Hangar · How a change moves

One road from intent to production

Everything in Hangar meets at one place: a reviewed, merged commit. People ask Tower, agents ask Autopilot, and from there the same pipeline builds, proves and releases to every cluster.

One road from intent to production A developer asks Tower for a change, which becomes a pull request on GitHub. A reviewed, merged commit is the only thing that crosses into the clusters: Glidepath builds and signs it, each cluster's ArgoCD pulls it, and Airframe composes what the Skyport apps need. Events flow back to Tower. AI agents follow the same road through Autopilot's Clearance gateway, with less authority. CLUSTERS · DEV AND PROD · BUILT FROM APRON PR SCOPED PR WEBHOOK RELEASE PR PULL XR COMPOSES Developersself-serviceEXPERIENCETowerBackstage portal1 BOUNDARYGitHubreviewed commitsONLY A MERGEDCOMMIT CROSSES2 DELIVERYGlidepathbuild · sign3 ArgoCDone per cluster · pulls4 CONTROL PLANEAirframeCrossplane5 Skyport appsflight-api · baggage-api EVENTS · TRACES · SLOS6 AI agentsany agent workloadAI WORKLOADSAutopilotClearance gateway7 LEGENDPeople and agentsHangar productThird-party toolThe only crossingA changeWrite-backEvents back

Plays once on load. Click any box to open its page; numbered badges give the reading order.

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

Hangar · OverviewClick any box to open its page