Hangar · Where it runs

Two clusters, one source of truth

Hangar as it actually runs today: a dev cluster that builds and proves, a prod cluster that runs Tower and the apps, and GitHub between them as the only thing either one trusts.

Two clusters, one source of truth Two Kubernetes clusters, dev and prod, each built from the Apron template and each running ArgoCD and Airframe. The dev cluster runs Glidepath, an Autopilot agent sandbox and dev copies of the Skyport apps; the prod cluster runs Tower and the production Skyport apps. Developers use Tower, which opens pull requests on GitHub; GitHub triggers Glidepath, and each cluster's ArgoCD pulls merged changes. No cluster holds credentials for another. DEV CLUSTER · BUILT FROM APRON PROD CLUSTER · BUILT FROM APRON SELF-SERVICE PR WEBHOOK RELEASE PR DEPLOYS AGENT RUN DEPLOYS GitHubreviewed, merged commits Developersself-service Glidepathbuild · sign Autopilotagent sandbox Skyport appsdev · test TowerBackstage Skyport appsflight-api · baggage-api · canary ArgoCD + Airframepulls from git · composes XRs ArgoCD + Airframepulls from git · composes XRs No cluster holds credentials for another. Each one pulls. LEGENDPeopleHangar productProposed runtimeThe only crossingA changeWrite-back

A token follows one change from Tower to prod, on a quiet loop (CSS only, hidden for reduced motion). Click any box to open its page.

Hangar · OverviewClick any box to open its page