Skip to content
New Signal-based gating for canary steps is live in v2.14 Read the changelog →
← All customer stories
Helio

Moved from weekly release trains to twelve promotions a day without adding headcount.

“The release train was a coordination tax. It just stopped being necessary.”

Sam Okonkwo Sam Okonkwo Engineering Manager
thrayne.dev/environments/2402

Release 2402

rolling out started 4m 02s ago
  1. build

    24s

  2. test

    1m 12s

  3. staging

    8s

  4. canary

    25%

  5. production

$ thrayne promote api-gateway staging to prod
Service Version
api-gateway v2.14.0 live
checkout v2.14.0 rolling
search-index v2.14.1 queued
billing v2.13.2 live

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

Industry

Energy

Headquarters

Porto, PT

Size

260 employees

Relationship

Customer since 2025

12/day
promotions
-84%
lead time
3
engineers on platform

The story

How Helio moved from where they were to where they are, in their platform team's words.

Connected tools

  • Buildkite
  • Amazon ECS
  • Prometheus
  • PagerDuty
All integrations →
01

The problem

Everything shipped on Thursday. Around thirty changes from six teams were batched into a weekly release train, preceded by a coordination meeting nobody enjoyed. When the train broke, the batch made it genuinely hard to say which change was responsible, so the response was to roll back all of it and rebuild the batch for the following week. A one-line fix waited six days for the next departure.

02

What changed

Rollout became progressive and per-change: each promotion goes to a canary slice first and advances only while the Prometheus error-rate and latency queries stay inside their thresholds, rolling back on its own and paging through PagerDuty when they do not. Because a bad change reverts itself in minutes, batching stopped being the safety mechanism and the train had nothing left to do.

03

Where they are now

Helio promotes about twelve times a day, lead time from merge to production fell 84%, and the Thursday meeting no longer exists. The platform team is still three engineers — the cadence changed without headcount following it.

“Nobody argues about what broke any more, because one promotion contains one change.”
Sam Okonkwo Sam Okonkwo · Engineering Manager, Helio

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