Release clearance for Rails
Know when every release is safe to stop watching.
CI tells you your code passed its tests. DeployAngel tells you it passed production: after each deploy it compares real traffic against your last healthy release, then clears it, fails it, or says exactly what it's still waiting to see.
One gem. No dashboards or thresholds to configure.
v381 cleared for normal traffic
12 min after rollout · promoted from staging v57, which was cleared
- Confidence
- High
- Routes exercised
- 31 / 33
- Requests
- 18,204
- HTTP 5xx rate0.12% → 0.10%
- Background jobsall normal
- Checkpoint
order.created412 expected · 405 seen - Still watchingNightlyInvoiceJob by 03:00 EDT
You ship more often than ever.
Coding agents write a lot of the code now. Releases go out daily, and nobody has time to stare at dashboards after each one.
Monitoring tells you something is wrong.
Error trackers and APM are great at alerts. None of them tell you a specific release is done, safe, and no longer worth watching.
DeployAngel gives every release a verdict.
Cleared, failed, or not cleared yet, with the evidence behind it: what ran, what didn't, and what it's still watching for you.
How it works
From deploy to verdict, without setup
-
1
Add the gem
The agent aggregates requests, jobs, and exceptions in memory and sends one small payload a minute. No code changes.
# Gemfile gem "deployangel"
-
2
Deploy as usual
DeployAngel notices each new release on Heroku, Kamal, Render, Fly.io, or your own servers. Registering from CI adds a link to the run.
# Optional, after deploying deployangel release -
3
Get a verdict
DeployAngel compares the release with your last healthy one and clears it once enough normal behavior has run. Failures alert immediately.
✓ Cleared ✕ Failed ! Not cleared yet
What it checks
Catches what error trackers miss
Regressions, per route and job
Error rates and latency for every route, failure rates and durations for every job class, each compared with the last healthy release.
Work that silently stops
Add DeployAngel.checkpoint("order.created") and a release fails if orders stop, even when every request still returns 200.
Recurring jobs that skip a run
It learns your schedules and keeps watching after clearance. A missed nightly job revokes the release's clearance.
Rare paths, watched after release
Password resets and sign-ups that changed but haven't run yet are flagged, and you're alerted if they fail the first time they do.
Points at the cause
Failures show the affected routes and jobs, new exceptions, and the changed files most likely responsible, with optional AI investigation.
Honest about low traffic
Quiet apps and after-hours deploys wait for normal activity instead of guessing, and the clearance report says what couldn't be observed.
Built for coding agents
Your agent ships the release. Now it can check it too.
The deployangel CLI and MCP server let Claude Code, Cursor, or CI wait for a release's verdict and read the evidence when it fails. Stable exit codes mean a pipeline can stop on a bad release without anyone watching.
- ✓ Read-only tokens for agents and developer machines
- ✓ "No problems so far" is never reported as cleared
- ✓ Works with any agent that supports MCP
$ bundle exec deployangel verify --wait Waiting for v381… observing, 6 min of traffic Waiting for v381… initial check: no problems so far v381 cleared for normal traffic at 14:12 UTC (12 min after rollout) State: closed · Verdict: verified · Confidence: high · Coverage: 94% Still watching: NightlyInvoiceJob (expected by 03:00) Changed but not yet exercised: POST /password_resets $ echo $? 0
Safe to install
Never in your request path
No network calls in requestsEverything is aggregated in memory and sent from a background thread once a minute.
No user dataRoute patterns, counts, and sanitized exceptions. Never request bodies, parameters, or source code.
Fails openIf DeployAngel is unreachable, your app is unaffected and telemetry is simply dropped.
Stop watching dashboards after every deploy.
Free while in beta. Ruby on Rails 7.1+ on Heroku, Kamal, Render, Fly.io, or anywhere Rails runs.