Ship every release through one gate.
Thrayne is the release plane for platform teams — deploy pipelines, environment promotion, and rollback in a single control surface your whole org can read.
Free for one environment · No card required · SOC 2 Type II
Release 2411
rolling out started 4m 02s ago-
build
24s
-
test
1m 12s
-
staging
8s
-
canary
25%
-
production
—
| Service | Version | |||
|---|---|---|---|---|
| api-gateway | production | v2.14.0 | live | 1m 48s |
| checkout | canary | v2.14.0 | rolling | 4m 02s |
| search-index | staging | v2.14.1 | queued | — |
| billing | production | v2.13.2 | live | 2h ago |
Pipelines
Three pipeline files, 41 services, one promotion path each.
| Pipeline | Runs (30d) | Success | Last run |
|---|---|---|---|
| web-monorepo | 412 | 99.3% | 6m ago |
| platform-services | 1,284 | 98.8% | 12m ago |
| data-jobs | 96 | 100% | 1h ago |
Environments
Promotion order is fixed. Production requires two approvals.
- production 2 approvals
eu-west-1 · 38 services
- canary
eu-west-1 · 38 services
- staging
eu-west-1 · 41 services
- dev
local · 41 services
2,400+ engineering teams promote to production through Thrayne every day.
- Northwind
- Kestrel Bank
- Helio
- Ravensworth
- Tessellate
How it works
Four steps between a merge and production.
Each one is inspectable, each one leaves a record, and none of them require a person to remember a runbook.
- 01 Model
Describe the path to production once
A pipeline is a file in your repo, not a wizard someone clicked through in 2021. Thrayne reads it, renders it, and keeps every environment in step.
- Declarative pipeline spec
- Environment inheritance
- Drift detection
- 02 Gate
Every promotion carries its evidence
Checks, approvals, and the diff that triggered the release travel with the build. Nothing reaches production without a record of why it was allowed to.
- Required checks
- Policy-based approvals
- Immutable audit trail
- 03 Roll out
Move traffic in steps you can defend
Canary a percentage, watch the signals you already collect, and promote or roll back from the same screen. No separate dashboard, no second tool.
- Percentage rollout
- Automatic rollback
- Signal-based gating
- 04 Answer
Know what shipped, and when, and by whom
Every deploy is queryable. Ask what changed between two releases and get the commits, the approvals, and the config diff in one response.
- Release diffing
- Change attribution
- Exportable audit log
Thrayne at run rate.
Across all production tenants, last 30 days.
- 1.4M
- promotions per month
- 99.99%
- control-plane uptime
- 38s
- median promotion time
- 2,300
- environments managed
Integrations
It sits between the tools you already run.
Thrayne does not replace your CI, your runtime or your secret store. It reads from them, gates on them, and records what they said.
Browse all 40+ integrations →- GitHub Actions CI
- GitLab CI CI
- Kubernetes Runtime
- Terraform Infrastructure
- Datadog Signals
- Prometheus Signals
- Vault Secrets
- Slack Notifications
- PagerDuty On-call
- Okta Identity
Customers
Teams that stopped guessing what shipped.
- Northwind
We replaced four scripts, a spreadsheet and a Slack channel with one pipeline file. The first week we caught two config drifts that would have been outages.
34m → 38s
median promotion time
Dana Reyes Staff Platform Engineer - Kestrel Bank
The auditors asked who approved a change in March. It took eleven seconds to answer, and I did it from my phone.
11s
to answer an audit query
Marta Ilves Head of Platform - Helio
The release train was a coordination tax nobody wanted to pay. It just stopped being necessary — we went from weekly to twelve a day.
12/day
promotions, up from 1/week
Sam Okonkwo Engineering Manager
Trusted by platform teams at
- Northwind
- Kestrel Bank
- Helio
- Ravensworth
- Tessellate
- Blue Harbour
- Northwind
- Kestrel Bank
- Helio
- Ravensworth
- Tessellate
- Blue Harbour
Changelog
Shipping every week, in public.
- Added v2.14.0
Signal-based gating for canary steps
Hold a canary step until your own latency and error-rate signals clear a threshold you declare in the pipeline file.
- Fixed v2.13.2
Faster environment diffing on large monorepos
Environment diffing on repositories above 400 services is roughly nine times faster and no longer times out.
- Added v2.13.0
Segregation-of-duties approval policies
Declare that the author of a change may not approve it. Enforced in the pipeline, not by convention.
Questions we get asked
Does Thrayne replace my CI?
No. Thrayne starts where CI ends. Your CI builds and tests an artefact; Thrayne decides where that artefact goes, under what conditions, and keeps the record.
What happens if a rollout goes wrong?
Rollback is a first-class operation, not a re-deploy of an older commit. The previous release is kept warm, so reverting is a traffic change rather than a rebuild.
Can we run it in our own infrastructure?
Yes. The control plane is available as a managed service or self-hosted on your own Kubernetes cluster. The pipeline spec is identical either way.
How does approval work for regulated environments?
Approvals are policies, not people. You declare who must approve which environments, and Thrayne enforces it — including segregation-of-duties rules where the person who authored a change cannot approve it.
Do you support monorepos?
Yes. A single pipeline file can describe many services, and Thrayne only promotes the ones whose inputs actually changed.
Get started
Put every release behind one gate.
Start with a single environment for free. Add the rest when your team is ready — no migration, no rebuild, no second dashboard.
- Free for one environment
- SOC 2 Type II
- Self-host or managed
- No card required