Product · Promotion
Move the build, not the source.
The artefact your CI produced is the artefact that reaches production. Promotion changes where it runs and what configuration it reads — never what it contains.
01 · Inheritance
Set a value once, not once per environment
Environments form a chain. Each inherits from the one before and overrides only what genuinely differs, so a shared value lives in exactly one place.
- Chained inheritance
- Per-environment overrides
- Secret references, not secrets
02 · Drift
Know when an environment stops matching its file
Anything changed outside Thrayne is reported as drift against the declared state, with the diff and who made it. No more discovering a manual hotfix six months later.
- Continuous drift detection
- Diff against declared state
- Attribution and timestamps
Release 2409
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
Promotion questions
Does promotion rebuild the artefact?
No. The artefact built by your CI is the artefact that reaches production. Promotion moves it between environments and swaps configuration — it never rebuilds, so what you tested is what ships.
How is environment configuration inherited?
Environments form a chain. Each one inherits from the previous and overrides only what differs, so a value set once in staging does not have to be repeated three times.
Can promotion be triggered from CI?
Yes — the CLI and the API both accept a promotion request. Most teams promote to staging automatically on merge and gate production behind approvals.
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