Hangar · The lifecycle

Every pass leaves the platform better

The software lifecycle as Hangar runs it: seven stages in a loop, each owned by part of the platform, and every pass written back to one shared record.

Every pass leaves the platform better A loop of seven lifecycle stages: plan and design, onboard and code, build and test, secure and govern, release and deploy, operate and observe, and measure and improve, which feeds back into planning. Release and deploy is the boundary where only a merged commit crosses. Four stages write back to the hub, Hangar's single record of git history, decisions and release records. GIT · RELEASESHangarone record of every passPlan and designADRs · contracts1 Onboard and codeTower · one cicd.yaml2 Build and testGlidepath · Tekton3 Secure and governSigstore · Kyverno4 Release and deployArgoCD · Rollouts5 Operate and observeTower · OTel · SLOs6 Measure and improveDORA · scorecard7 LEGENDStageThe boundaryThe recordWrites back

The whole SDLC

Seven stages, clockwise from the top, and every pass leaves something in the record at the centre. Point at a stage for the short version; click it for the full page.

The centre · Hangar

Git history, ADRs, release records and DORA numbers: the platform remembers every pass, so the next one starts better informed.

Stage 1 · Plan and design

Contracts first, decisions in writing.

Every decision that shapes the platform is written down as an ADR, and every service starts as a contract (an Airframe XR) before it is code.

Stage 2 · Onboard and code

One file, scaffolded for you.

A new service is one form in Tower. It becomes a pull request with a single cicd.yaml; nobody hand-writes pipelines.

Stage 3 · Build and test

Rootless builds, pinned catalogs, real tests.

Glidepath builds on Tekton with rootless BuildKit, pinned task catalogs, and real tests through Testkube.

Stage 4 · Secure and govern

Honest gates, workload identity, no stored keys.

Keyless signing, provenance that says what the build really did, and policy that checks both before release.

Stage 5 · Release and deploy

Only a merged commit crosses a boundary.

Promotion is a pull request. Each cluster's ArgoCD pulls what merged, and Argo Rollouts runs the canary.

Stage 6 · Operate and observe

One trace per change, one pane of glass.

One OpenTelemetry trace per change from commit to canary, with SLOs and release records side by side in Tower.

Stage 7 · Measure and improve

Scorecards, evals and written-down gaps.

DORA metrics, the Airframe scorecard and agent evals turn every pass into the next round of work.

Press Play or use ←/→ to walk the stages. Point at a stage to preview it; click to open its SDLC page.

←/→ step · Space play/pause · R replay · Home/End jump

Hangar · OverviewClick any box to open its page