Projects & stages

A project is where your code and its environments live. Stages are the environments you deploy into.

Projects

A project pairs a name with a git URL and owns everything derived from that repo — its builds, its reusable configs, and its stages. Create one to get started; there's nothing to configure up front.

Stages

A stage is one environment — typically dev, qa, and prod. Each stage is independent: it carries its own placement (which outposts it runs on), its own resolved config, and its own current release. A stage stays empty until you bring a release up on it.

Promoting between stages

There is no separate "promote" action to learn. Because a release is just build × config × stage, promoting a known-good build from qa to prod is deploying it onto prod — the same build, resolved against prod's config. What changes between environments (replica counts, limits, domains) lives in each stage's config, not in the build, so the exact bytes you tested move forward unchanged.