Pricing
The CLI, execution kernel, and adapters are free and source-available — they run entirely in your own infrastructure. The hosted dashboard adds run history and evidence on top, priced per project so it scales with how much of your release surface you actually prove.
What counts as a project
A project is one system under test: the thing one API token, one set of cases, and one release label sequence describe.
- One backend API = one project.
- A monorepo with three deployable services = three projects.
- Staging and production of the same service = one project with two release labels.
What's included
| Feature | Free | Team | Enterprise |
|---|---|---|---|
| CLI, execution kernel & adapters (run anywhere) | |||
| Uploaded run history | |||
| Projects | 1 | Unlimited | Unlimited |
| Evidence viewer | |||
| Evidence retention | 7 days | 12 months | Custom |
| Active share links per run | 1 per run | Unlimited | Unlimited |
| Custom redaction rules | |||
| Hosted project secrets | |||
| Trend analytics | |||
| Release roll-up | |||
| CI integration | |||
| Run notifications | |||
| Shareable evidence links | |||
| SSO | |||
| Audit log | |||
| Jira write-back | |||
| Linear write-back | |||
| Flag-proof merge gate | |||
| Flag blast-radius view | |||
| Hosted evidence runners | |||
| Verification-driven ticket transitions | |||
| GitHub write-back | |||
| Bitbucket write-back | |||
| Azure Boards write-back | |||
| Flag-rollout re-verification | |||
| Programmatic API access |
Every row is generated from the plan catalog the hosted API enforces — see the full list on the features page.
What if I put everything in one project?
You can — nothing stops you, and we don't check. What you give up is per-system answers: the release-readiness rollup (on every plan), the flag blast-radius view, and ticket-tracker mapping all operate on a project as a whole, so one project spanning four services reports “this release is proven” only when all four are green, and tells you nothing about which of them broke. Splitting by system is what makes those views answer a question.
Founding Setup
Testing a non-REST system, a feature-flag source that isn't Azure DevOps, or a gnarly multi-step release check often needs scoped setup work. Founding Setup wires one critical workflow into your CI and hands you a written readout of what it catches — fixed scope, fee refunded if it isn't running against your real system at the end. Included with Enterprise; a paid add-on otherwise.
If we disappear, you keep working
The CLI and execution kernel are open source (AGPL-3.0) and run entirely in your own infrastructure — a hosted outage never blocks a release. If we ever wind the company down, active hosted licenses convert to perpetual and the hosted source is published.
ReleaseTwin is independent and self-funded. Prices are early-access placeholders and may change before general availability.