Introduction

Airframe is a reference implementation of a Google Cloud landing zone and a git-native control plane for product teams. Teams propose every change as a merge request, rules written as code decide it, and pipelines execute it. No one’s everyday account can change production infrastructure, and every coding agent contributes under the same checks as a person.

One person runs the platform today. Where a rule needs a second person, such as the approver of a time-boxed grant or the approval of a merge request by someone other than its author, that second person is the maintainer’s second account. The mechanisms are enforced, but the separation between two people is not yet real.

Where to start

• Airframe in ten minutes follows one product through its whole life, from the file that creates it to the file that retires it. Begin there.
• The glossary explains every term the documentation uses, in a sentence or two.
• The Concepts section explains the ideas the platform is built on, one page each, starting with the catalog.
• The repositories section maps the platform’s seven repositories, then gives each one a page: what it is for, what is in it, and who changes it.
• How it works follows a product from creation to removal, a change from a laptop to production, and what happens when the cloud drifts from the code.
• Adopting Airframe is for an organization that wants to run it: what it needs and costs, the bootstrap, the first domain and product, and what an existing system can bring today.
• Operating is for the day to day: temporary access and the break-glass, moving between releases, cost and billing, and dashboards, alerts and drift.
• Security model draws the platform’s trust boundaries, then lists every security claim with the mechanism behind it and whether it is enforced, a convention or designed.
• Reference is for looking things up: the catalog’s fields, the platform’s names and labels, the hostname of each environment, its pipeline components, and every rule of the policy pack, each row with its source.

The source is on GitLab.