Support
Frequently asked questions
Quick answers to the questions we get most. Searchable below.
General
4 questions Crash Override embeds provenance into every artifact at build time — irrefutable evidence of what was built, shipped, and running. It traces every artifact from a developer's desktop to production, whether the code was written by a human or an AI agent. That powers three things: AI code traceability, software compliance (real evidence from real builds — SLSA Level 3 natively), and incident response.
No — and we're deliberate about that distinction. Crash Override is a developer tools company that solves security use cases. Security outcomes are the goal; developer experience is the path to get there.
Crash Override supports Python, JavaScript, TypeScript, Go, Rust, Java, Ruby, PHP, C, C++, C#, Kotlin, Swift, and Scala.
Book a demo and we'll have you up and running straight after. Or start right now, for free, with our open-source tool Chalk.
Product
1 questions Crash Override works with GitHub Actions, GitLab CI, Jenkins, CircleCI, Buildkite, and ArgoCD. Each integration is a single YAML step.
Security & Compliance
1 questions We operate a responsible disclosure programme. Report via our Responsible Disclosure page or email [email protected].
Open Source
2 questions Two. Chalk — an open-source tool for binary marking, provenance tracking, and software supply-chain security. Ocular — an open-source tool for infrastructure visibility and security observability. Both are free and open source.
Chalk and Ocular are GPL licensed.
Still have questions?
We know FAQ pages can't cover everything. If you didn't find what you were looking for, a real engineer will answer — no chatbot, no ticket queue.