Your on-call rotation gets quieter, and nobody has to be heroic about it.
Odonat sits in three places in your delivery path: in front of the merge button, in front of the rollout, and in front of the pager. Each one catches a class of fault earlier than the last, and the earliest catch costs nothing at all.
Nothing about the change is different. Everything about the evening is.
- A config change merges on Friday because the reviewer was in a meeting.
- p99 climbs at 02:14. PagerDuty wakes one person.
- Forty minutes go to working out which of the day’s eleven deploys did it.
- The fix is a one-line revert. Finding it was the job.
- The same change is replayed against real traffic before it merges. It fails, and it never lands.
- What does land ships to 1% of traffic first, watched for six minutes.
- If it degrades, the rollout halts before the other 99% see it.
- If something still reaches production, the revert PR is written, explained and waiting.
Three interception points, in the order a change meets them.
The bad pull request never becomes your problem
Every PR is replayed against a copy of your real production traffic before it can merge. Latency regressions, malformed config and hardcoded secrets surface while the author still has the diff in their head, not after a reviewer finds a spare hour.
The reliability gate stops being a person.
What gets through is contained to 1% of traffic
Anything that survives the gate ships into a Sentinel Cell, our name for a canary: 1% of production traffic, observed for six minutes. Capacity and correctness faults that only appear under real load appear here, in front of a hundredth of your users.
A regression becomes a rollback, not an incident channel.
The revert is written before anyone reads the page
When an alert fires, Datadog metrics, PagerDuty events and recent commits normalise into one shape, and the causal engine ranks what changed against what broke. Above 85% confidence it opens the revert. Below it, you get a written analysis and a button.
On-call gets a decision instead of an investigation.
The same system, four different reliefs.
Break something on purpose and watch it get caught.
The sandbox runs the full interception path against a sample service. Inject a connection-pool regression, a malformed feature flag or an unindexed query, and follow it through the pre-merge gate, the Sentinel Cell and the causal engine, including the case where confidence lands below the threshold and Odonat refuses to act.
Nothing you do here touches a real environment, and there is nothing to install.
Open the sandboxRequires a sign-in. You will land straight in the sandbox afterwards.