Fair, Transparent, and Built for Your Infrastructure—Not Ours.
Our pricing is different because our architecture is different. We don't have to charge you for our massive cloud bills, because our tools run on your compute. You get enterprise-grade governance at a fraction of the cost, without ever sending your code to a third-party cloud.
| Tool | Included In Suites | Committers | CI/CD License / Committer / Year | Annual Tool Cost |
|---|
A Model That Puts Engineers First
Pay for Who Builds, Not Who Watches
Traditional tools charge "per-seat," forcing you to pay for managers, architects, and junior developers who may only need occasional access. Our model is simple: you're licensed based on the number of developers actively committing code. This fairly scales with the team benefiting from automated governance, saving you an average of 70-80% over per-seat models.
Run Your Pipelines, Not a Tab
Your CI/CD system is dynamic. Why should your licensing be rigid? We use a per-tool concurrent licensing model. If you buy a 2-run license, you can run up to two instances of *each licensed tool* in parallel across your organization. We don't charge per-repo or per-scan. Run your pipelines as often as you need.
Handle Spikes Without Failing Builds
We're engineers. We know CI workloads are unpredictable. That's why your license includes a two-stage safety net to provide flexibility and guarantee your pipeline never breaks.
1. Automatic Bursting: Twice per quarter, for each tool, you can automatically burst up to double your licensed concurrency for a 30-minute window. This handles the common "everyone pushed code at once" scenario without any configuration changes.
2. Graceful No-Op: If you exceed even your burst capacity (or you have used your allocated burst capacities), our tools don't just fail. They will wait for a configurable timeout (e.g., 5 minutes) for a license to become free. If one doesn't, the tool performs a "no-op" run: it prints a summary of its findings to the console, exits with a success code (0), and never blocks your build.
The result: You get the flexibility to handle spikes, and the peace of mind that a licensing issue will never be the reason your deployment fails.
It's simple: We respect your infrastructure, and we respect the source.
The result isn't a "cheap" tool—it's an architecturally efficient one. You get deeper, more accurate analysis because our tools run where your code and infrastructure live, without forcing you to pay for our cloud bill on top of your own.