Learn: Onboarding a Product

How a whole new application gets onto the platform — its registry, CI push role, supply-chain policies, and delivery — from one file in git, with nothing hand-wired per app. This is the day-one paved road, and the single-source-of-truth model behind it.

Audience: platform engineers and team leads onboarding a new app. It builds on the domain model (Team / Product / Service / Environment), and it’s the sibling of the Environment API: that provisions an environment, this registers the Product.

Before you start: read the domain model. Skimming Delivery, Policy, and Supply chain helps too — this is where their per-product pieces come from.

Read in this order

1. Orientation — the one idea (one registry entry, everything derives from it), the real alpha-shop record, the derivations (github-oidc / policy / argocd-apps, plus github-teams), and the paved road (scaffolder → gate → reconcile-on-merge).
2. Reference — the Product schema, the derivations table, the paved road, and gotchas.

Onboard one yourself: How-to: onboard a new Product — a newcomer-followable playbook covering both the Backstage scaffolder path and a direct registry PR.

Then, to go deeper

• The pieces that derive from the registry: Delivery · Policy · Supply chain · Environment API.