Hangar Brand System
Hangar / Brand System / Draft
Platform naming, philosophy & visual system — proposal v1

HANGAR.

A home base for building, releasing, and watching every service you run — one platform, one look, no snowflakes.

Platform — Hangar
CI/CD engine — Glidepath (standalone-installable)
Release command center — Tower (Backstage plugin)
01 — Naming architecture

Three names, one hangar door

Everything stays inside a single aviation vocabulary, so the names teach the product instead of decorating it. Each piece is real and separately installable — but they were clearly poured from the same mold.

The Platform

Hangar

Home base. Where a service is scaffolded, given a golden-path template, and provisioned onto whichever cluster it belongs on — no cluster is a snowflake.

"Every aircraft needs a hangar before it needs a runway."

The CI/CD Engine

Glidepath

The guarded descent from a merged commit to a verified release — build, scan, sign, attest, promote. Installs on its own if a team just wants the pipeline.

"The angle of descent is fixed. Every release flies it the same way."

The Command Center

Tower

One Backstage plugin, not a shelf of them. Topology, pull requests, image provenance, releases, and SLOs in a single console.

"Pilots don't check five instruments for one answer. They look at the tower."

Hangar provisions the airframe → Glidepath flies every release down the same path → Tower is the window into all of it, live, from the ground. Tower isn't the last stop in a pipeline — it's the view that never closes.

02 — Platform philosophy

Preflight checklist

Five things Hangar is opinionated about. Not marketing copy — the actual rules the product is built to enforce.

1

Golden paths, not gatekeeping

Scaffolding gets a compliant service running in minutes. Guardrails validate — they don't block by default.

2

One tower, full visibility

Releases, PRs, images, and topology live in a single console, not a dozen disconnected tabs bolted onto a catalog.

3

Provenance you can prove

Every artifact is signed, attested, and independently verifiable. Security is structural, not a checkbox at the end.

4

No cluster is a snowflake

The same platform installs the same way everywhere — dev, staging, prod, someone else's laptop.

5

Calm cockpit, not a light show

Amber means attention. Blue means information. Gray means at rest. Nothing blinks that doesn't need to.

03 — Visual system

Amber for attention, sky for information

Dark is the primary surface — instrument-panel dark, not gamer-RGB dark. Light is a full first-class second theme, not an inverted afterthought. Toggle the switch above to compare both.

Ground
--bg
Panel
--panel
Amber / primary
--amber
Sky / secondary
--sky
Good
--good
Critical
--bad
Display
Plex Sans Condensed
Body
IBM Plex Sans — running text, labels, descriptions.
Data / mono
IBM Plex Mono — SHAs, tags, digests, status codes.
04 — Tower, in the flesh

One card, everything you'd otherwise open five tabs for

A release card from Tower's Releases tab. Linked PRs are buttons, not links buried in a description. Image provenance lives in a panel you open when you need it, not a wall of text you scroll past when you don't.

Overview
Releases
Topology
Pull Requests
Images
SLOs
checkout-api production
Approaching — 4 of 5 gates clear
BuildSAST/SBOMSign+AttestStagingProduction
PR #482 outcome-relay hostAliases fix → main
✓ PR #479 merged
▸ Image & provenance ›
Imageghcr.io/hangar/checkout-api
Digestsha256:7f3a…c19e
Cosignverified ✓
Rekor entry24601998
SBOMavailable ✓
Base imagedistroless/nodejs20
cluster: kind-prod deployed 12m ago commit a1c4e9f