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

Cut median promotion time from 34 minutes to 38 seconds across 41 services.

“We replaced four scripts, a spreadsheet and a Slack channel with one pipeline file.”

Dana Reyes Dana Reyes Staff Platform Engineer
thrayne.dev/pipelines/2411

Release 2411

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

Logistics

Headquarters

Rotterdam, NL

Size

1,400 employees

Relationship

Customer since 2024

38s
median promotion
41
services
0
rollback incidents since

The story

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

Connected tools

  • GitHub Actions
  • Kubernetes
  • Terraform
  • Datadog
All integrations →
01

The problem

Promotion was four bash scripts, run in an order that lived in one engineer's head. Which version sat in which environment was tracked in a shared spreadsheet, updated by hand and wrong often enough that nobody fully trusted it. Anything urgent went through a Slack channel where an approval was a thumbs-up emoji, and every November the team declared a peak-season code freeze because it was the only way to be confident nothing would move unexpectedly.

02

What changed

The 41 services were described once, as a single pipeline file per repository, with staging, canary and production inheriting shared configuration rather than redefining it. The scripts were deleted rather than wrapped. Approvals moved from the Slack channel into policy: a rule about who may promote to production, evaluated automatically, instead of a person remembering to ask.

03

Where they are now

Median promotion is 38 seconds, down from 34 minutes, and the spreadsheet is gone — the environment view is the record. There have been no rollback incidents since the migration, and the December freeze was not declared last year for the first time in six years.

“The freeze used to be the only way we could trust December. We did not declare one last year.”
Dana Reyes Dana Reyes · Staff Platform Engineer, Northwind

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