Ship to production without holding your breath.
Relay is the progressive-delivery control plane. Promote every change through Build, Test, Canary and Production with adaptive analysis and one-second rollback.
- 31,000+
- deploys / day
- 1.1s
- median rollback
- 0.04%
- change-fail rate
Trusted by platform teams shipping at scale
Five stages. One safe path to production.
Every change rides the same rails — built, gated, canaried, promoted and guarded. Relay deals them out one at a time, and never advances a stage that isn't healthy.
Build
Every commit becomes an immutable, signed artifact. Relay fingerprints the build, captures provenance, and stages it the instant CI goes green.
- Signed provenance (SLSA-3)
- Reproducible artifacts
- Auto-stage on green
- [build]fetch source @ a91f2c4
- [build]compile 1,284 modules
- [ok]artifact signed · slsa-3
- [test]612 gates running
- [ok]gates green 612/612
- [canary]route 5% → candidate
Test
Quality gates run in parallel and report back as a single verdict. A failed gate never reaches a user — the artifact simply waits.
- Parallel gate execution
- Single roll-up verdict
- No flaky-test promotions
- Unit248 passed
- Types1 passed
- Lint1 passed
- Integration96 passed
- End-to-end34 passed
- Security scan1 passed
Canary
Relay routes a sliver of live traffic to the new version and watches latency, errors and saturation against the incumbent. Adaptive thresholds tune themselves to each service.
- Variance-aware scoring
- Live traffic shadowing
- Auto-abort on regression
Promote
A healthy canary promotes itself on a curve you control — 5%, 25%, 50%, 100% — pausing automatically the moment a signal drifts out of band.
- Progressive traffic shift
- Policy-gated promotion
- Pause on drift
Production
Once at 100%, Relay keeps watching. Post-deploy guardrails hold for the full bake window, and a single keystroke — or a single anomaly — reverts in about a second.
- Post-deploy guardrails
- One-second revert
- Always-on health
Below: zoom into the stage that does the watching — Adaptive Canary.
Deploys shouldn't require a hero.
Most teams ship by gathering the bravest engineer, watching dashboards by hand, and hoping the rollback runbook still works. It doesn't scale, it burns people out, and it makes Friday a no-deploy day.
Manual watching
Someone babysits Grafana for twenty minutes after every release, correlating spikes by eye.
Slow, scary rollbacks
By the time a human notices, redeploys the old version and waits for it to roll out, the incident is already minutes old.
Blast radius
A bad change hits 100% of traffic at once because there's no safe way to test it on a fraction of users.
Deploy anxiety
Fear of breaking prod slows everyone down — releases pile up, batch sizes grow, and risk compounds.
It scores the release so you don't have to.
Relay shadows a fraction of real traffic onto the new version and compares it to the incumbent across latency, error rate and saturation. Thresholds aren't static — they adapt to each service's own variance, so a noisy endpoint isn't held to the same bar as a quiet one.
- Compares candidate vs. baseline on live, mirrored traffic
- Variance-aware scoring tuned per service, automatically
- Aborts and reverts before a regression reaches the majority
- Every decision is explained, logged and replayable
Median time from regression detected to full revert: 1.1 seconds.
Live in an afternoon. Watching forever.
Relay sits beside the tools you already run. There's nothing to rip out — point it at your pipeline and describe a safe rollout.
Connect your pipeline
Point Relay at your existing CI and cluster. No rip-and-replace — it sits beside what you already run.
Describe a safe rollout
Declare promotion steps, bake windows and guardrail metrics in a few lines of policy. Version it like code.
Ship and let it watch
Merge. Relay builds, gates, canaries, promotes and guards — paging a human only when a decision genuinely needs one.
Sits beside everything you already run.
Relay consumes your artifacts and signals from the tools your team already uses. No rip-and-replace, no agent sprawl.
Production-grade by construction.
Relay runs in your account, touches the minimum, and proves what it did. Every promotion and revert is signed, attributed and exportable.
SOC 2 Type II
Independently audited controls, renewed annually.
Runs in your VPC
The control plane never holds your data or your secrets.
Signed provenance
SLSA-3 artifacts with a verifiable chain of custody.
Scoped access
Least-privilege by default, with full RBAC and SSO.
Immutable audit log
Every decision is recorded, attributed and exportable.
Private by design
No telemetry leaves your boundary without consent.
The difference is who's awake at 2am.
The graphs watch themselves now.
“We went from a no-deploy Friday culture to shipping forty times a day. Relay reverts faster than a human can read the alert.”
Start free. Scale when production does.
Every plan ships canary analysis and automatic rollback. Pay only when you outgrow a single service.
Solo
For a single service and a small team finding their footing.
- 1 service, 1 cluster
- Canary + automatic rollback
- 7-day audit retention
- Community support
Team
Most popularFor engineering orgs running real, frequent production traffic.
- Unlimited services
- Adaptive Canary scoring
- Policy-as-code promotions
- 90-day audit retention
- SSO + RBAC
- Priority support
Enterprise
For regulated fleets that need it in their own account.
- Runs in your VPC
- SOC 2 + SLSA-3 provenance
- Custom guardrail metrics
- Immutable, exportable audit
- Dedicated solutions engineer
- 99.99% SLA
Shipped, naturally, one stage at a time.
Relay ships itself through Relay. Here's the recent cascade of releases.
Adaptive Canary
Canary thresholds now tune to each service's own variance. Noisy endpoints stop crying wolf; quiet ones get held to a tighter bar.
Policy-as-code v2
Promotion policies gained reusable fragments, dry-run previews and a typed schema with editor completion.
One-second revert
Reworked the data plane so a revert is a traffic-table flip, not a redeploy. Median detect-to-revert is now 1.1s.
Run-in-your-VPC
The control plane can now run entirely inside your account, holding none of your data or secrets.
Questions, answered straight.
No. Relay sits beside your existing CI and cluster. It consumes your build artifacts and orchestrates the rollout — you keep the tools you already use.
Relay keeps the previous version warm and shifts traffic with a routing-table flip rather than a redeploy. Reverting is a state change, not a rebuild, so it lands in about a second.
Latency, error rate and saturation out of the box, plus any custom metric you expose through Prometheus, Datadog or OpenTelemetry. Scoring is variance-aware per service.
On Team it's hosted; on Enterprise the control plane runs inside your own VPC and never holds your data or secrets. Either way, every action is signed and logged.
Kubernetes today, with first-class support for Argo CD, AWS and Vercel edge. Anything that can split traffic by weight can be a Relay target.
Yes — Solo covers one service with canary and automatic rollback, free forever. Upgrade to Team when you outgrow a single service.
Make your next deploy a non-event.
Join the teams who let Relay watch production so their engineers can sleep. Request access and we'll have you shipping safely this week.
Runs in your VPC · SOC 2 Type II · 99.99% SLA