Release observabilitySee what every
See what every
release actually did.
Every chart knows which flag changed and when. Spot the regression, click the marker, dial it back.
Error rate0.02%↓ 0.11 since 14:02
p95 latency212 ms↓ 700 ms after rollback
Releases today386 in progress
Auto-rollbacks3all within 90 s
p95 latency · checkout
Last 6 hv4.2 → 25%Auto rollback
12:0013:0014:0015:0016:0017:00
Live releases
- new-checkoutrolled back25%
- search-ranker-v3healthy50%
- agent-prompt-v15healthy5%
- pricing-page-bcomplete100%
- onboarding-tourwatching10%
Three questions every
release review asks.
Which flag caused it?
Every metric is sliced by flag and variant. The answer is one click away, not one meeting away.
errors / 1k requests · by variant
new-checkout · on4.1
new-checkout · off0.6
search-ranker · on0.9
exposure at detection
1%
5%
25%
50%
100%
caught at 5% · 412 users affected · rolled back in 38 s
Did we catch it early?
Regressions show up at 5% of traffic, when a few hundred people see them — not a few million.
What should we do now?
Alerts arrive with the fix attached. Dial back, pause the experiment or page the owner — from Slack or the dashboard.
p95 latency > 800 msSev 2
Started 14:02 · new-checkout moved to 25% at 14:01
Rheostat vs. the flags
you built in-house.
| Capability | Rheostat | In-house |
|---|---|---|
| Metrics sliced by flag and variant | ✓Yes | —No |
| Automatic rollback on a rule | ✓Yes | —No |
| Percentage rollouts with schedules | ✓Yes | ✓Yes |
| Agent traces linked to releases | ✓Yes | —No |
| Audit log of every change | ✓Yes | ✓Yes |
| Evaluation in under 20 ms at the edge | ✓Yes | —No |
Stop reading dashboards
after the incident.
- −61%
- median time to recover across 1,900 teams in 2026