Release trains
A release train coordinates a set of releases that ship together on a cadence — ideal for teams that batch multiple services into a scheduled delivery.
Create a train
Section titled “Create a train”Delivery → Release trains → New:
POST /api/v1/release-trains{ "projectId": "proj_…", "name": "Q3 Delivery Train", "description": "Bi-weekly train across storefront services.", "targetDate": "2026-09-15T00:00:00+00:00" }Board releases
Section titled “Board releases”Add releases to the train from the train board (or the release’s train field). Each boarded release keeps its own reconciliation, confidence and governance — the train is the coordination layer over them.
- A departed or cancelled train refuses new boarding.
- Leaving a train clears the release’s
trainId.
Why use a train
Section titled “Why use a train”- One place to see the readiness of every service in a coordinated release.
- A shared target date and status across teams.
- Governance still applies per release — the train doesn’t bypass policy or approvals.