Know what a release breaks before you ship it.
A green test suite tells you the code does what the tests expect. Release runs your critical journeys in a real browser against the build you are about to ship, and tells you whether a customer could still finish them.
| Journey | Reach | Result |
|---|---|---|
| Sign up and verify email | Not measured | Queued |
| Upgrade to Growth | Not measured | Queued |
| Invite a teammate | Not measured | Queued |
| Export a project to CSV | Not measured | Queued |
| Delete a workspace | Not measured | Queued |
“142 tests passed” is not the same as “nobody is worse off”.
What you can already see
- Unit tests
- 1,204 passing
- Integration tests
- 188 passing
- Staging smoke test
- Green
- Coverage
- 76%
What nothing tells you
- Whether a customer can still sign up, pay and export on this build.
- Which of those journeys only passed on a retry.
- Which failure nobody has measured the reach of.
Unit tests check functions. A journey checks the thing a customer came to do, end to end, in a browser, against the build you are about to promote.
Run the journeys that matter against the build.
- 01
Write
Critical journeys, as closed steps against a path.
- 02
Run
In a real browser against staging or preview.
- 03
Classify
Passed, failed, or flaky. A retry never turns red into green.
- 04
Weigh
Severity rises for a journey nobody has measured.
A regression is an engineering fact until you price it.
- ARR at stake
- —
- Customers
- —
- Margin
- —
- Contracts
- —
- Claims
- —
- Engineering
- —
- Risk
- High
Release answers the rows it can see. The blank ones are not missing data — they are outside what this system reads.
Running v4.12’s critical journeys against staging, the export journey fails at its fourth step, on both attempts. Nobody has measured how many accounts run it, so Release raises the severity rather than guessing low.
Release knows which journey broke. It does not know that an enterprise agreement names that workflow in an availability control, or what the subscriptions behind it are worth. Put the pull request through Preflight and Contract answers the same question, with the revenue attached, and the argument ends.
1 journey failing
$221K ARR exposed
Sources this product is designed to read
Staging, Preview deploys work without a connector. The rest are sources the model is built for and cannot be connected yet. The app never offers a provider whose consent flow it cannot complete.
Targets
- Staging (available today)
- Preview deploys (available today)
Delivery
- GitHub Actions
- Vercel
Release is in beta.
Built and running: journeys replay against staging in a real browser, a retry that rescues a failure is reported as flaky rather than green, and a journey nobody has measured raises severity instead of lowering it. What it does not have yet is analytics weighting, so reach reads not measured rather than a number nobody collected.