RELEASE ENGINEERING / CONTROL PLANE

SHIP SOFTWARE.
NOT SURPRISES.

Build, verify and promote every release through a deterministic delivery chain. One control plane for runners, artifacts, approvals and rollback.

Inspect the pipeline ↓
18,402builds / day
6m 12smedian lead time
99.97%runner availability
Developer working at a computer
BUILD STATION / 04
MAIN / HEAD
7f3a2c1 release: harden deploy gates signed · verified · ready
RUNNER eu-07 ONLINE ARTIFACT registry/edge-api:4.18.2 VERIFIED CANARY ring-1 100% SBOM SIGNED ROLLBACK WINDOW 14m RUNNER eu-07 ONLINE ARTIFACT registry/edge-api:4.18.2 VERIFIED
01

One release lane.
No hidden steps.

Every change moves through the same observable chain. Policy is code, approvals are explicit, and every artifact keeps its provenance.

PIPELINE / EDGE-API ready
branch: main · commit: 7f3a2c1
01Checkoutsource + policy
02Testunit + integration
03BuildOCI image
04VerifySBOM + signature
05Canary5% traffic
06Promoteproduction
$ forgeflow pipeline status edge-api
ready — waiting for a build
Server racks used as build runners
RUNNER FLEET

Ephemeral by default.

Every job gets a clean worker. No snowflake agents, no state leakage, no mystery caches.

RUNNERS / LIVE
248
workers available now
linux/amd64
182
linux/arm64
52
gpu-build
14
Network equipment
ARTIFACT FABRIC

Replicated close to compute.

02

Promote with evidence.

Every release keeps its tests, signatures, artifact digest and deployment history. Roll forward or roll back from the same immutable record.

RELEASERINGSTATUSAGECHANGE
edge-api 4.18.2sha256:7e4d…a91fglobal healthy12m+14 files
console 2.41.0sha256:119a…03ccring-2 canary31m+8 files
agent 9.7.6sha256:cd02…61beglobal healthy2h-3 files
CONTROL THE RELEASE / KEEP THE SPEED

Every deploy should be
boringly predictable.