Technology
Many teams write code, but only a few people can release it
We automate the release flows your teams share, in the tools you already run. Then any engineer on the team can start a release and roll it back without waiting on another team.
- Built in your own repositories
Releases today
Each team starts its own
- web-app 4.12Started by the Web team at 09:12 Live
- billing-api 3.8Started by the Billing team at 09:40 Live
- search-service 1.22Rolled back by the Search team at 10:05 Rolled back
- accounts-api 2.6Started by the Accounts team at 10:31 In checks
- notifications 2.1Started by the Messaging team at 10:47 Deploying
Release bot#releases
search-service is back on 1.21. The Search team rolled it back, and the checks passed.
What slows releases
Where releases wait when many teams ship
Many services, one release path
Each team owns its services, but they all ship through one shared release process. Releases line up behind each other, and changes pile up while they wait.
One team every release waits for
A central platform or ops team runs the releases, or the one person who knows how. When they are busy or away, every team waits.
Deploys only a few can run
Production access and the know-how sit with a few people. Everyone else opens a ticket or asks in chat, and a rollback waits for the same people.
What changes
After a Build, each team releases on its own
Plan on 4 to 8 weeks. You pay the second half of the fee when the acceptance criteria you signed pass in your own environment.
-
TodayMany services share one release process, run by hand, with handoffs between teams.
After a BuildHand-run steps and handoffs become one pipeline per release flow, started by the team.
-
TodayEvery release waits for the central team, or for the one person who knows how.
After a BuildAny engineer on the team can start a release and roll it back without waiting on another team.
-
Today“Where is it now?” gets asked in chat, and the answer depends on who is online.
After a Build“Where is it now?” gets answered by status messages in chat or the ticket.
-
TodayOnly a few people can deploy to production, and how they do it isn't written down.
After a BuildWhat they know becomes a runbook, a trained team, and a pipeline your team has already changed on its own.
Results
The same work at Nike and ASML
Results from release work at Nike (retail) and ASML (semiconductors): hand-run release steps and handoffs, turned into self-service pipelines.
Nike · deploys to staging
A test build on staging devices, started by the developer
- Started by: release engineer → developer
- Handoffs per deployment: 1 → none
ASML · CI for multiple teams
Integration steps that ran by hand became one self-service CI pipeline, standardized across teams
300+engineering hours a year
Nike · engineering time
600+
engineering hours a year of operational toil removed with self-service tooling
Read the cases“Previously, moving CI workflows between Dev, Staging, and Prod required manual, uncommitted code changes. Mateusz implemented a solution that reduced this to a single line of code, streamlining the process and enabling faster iteration for both developers and our team.”
At Nike, the other release engineers were trained on the tooling, so the knowledge didn't sit with one person.
Reading
More on platform teams and safe rollbacks
- ArticlePlatform Engineering vs DevOps: What an Internal Developer Platform Actually Buys YouWhat an internal developer platform is, when a platform team pays off, and why one that still routes requests through a person is a help desk.Read the article
- ArticleProgressive Delivery in 2026: Canary vs Blue-Green vs Feature FlagsHow canary releases, blue-green deployments and feature flags differ, and how each one gives you a fast way back from a bad release.Read the article
- ArticleEmbracing Software Development for Rapid Evolution in Technology ServicesWhy AI, platform engineering, multi-cloud cost and security all reward the same thing: small, tested changes through a governed pipeline.Read the article
Where to start
Start with your last release
The free Release Check shows where your last release spent its time and what that costs a year, in under 5 minutes and without a call.
Contact
Talk to the engineer
Book 30 minutes and bring your last release, or send a message. You talk with Mateusz directly.
