Namespaces

Namespaces provide isolated environments for grouping related apps—useful when you want to segment resources by project, customer, or environment without creating a separate team for each. They’re managed separately from apps and pipelines, and can be scoped to a specific region and zone.

Creating a namespace

$ bld namespaces:create my-namespace -t my-team -r us-east-1

Options:

• -t, --team — the team the namespace belongs to (defaults to your personal team).
• -r, --region — the region for the namespace (defaults to us-east-1; see Regions).
• -z, --zone — a specific zone ID within the region, for finer-grained placement.

Listing namespaces

$ bld namespaces -j | jq -r '.[].name'

Namespace details

$ bld namespaces:info my-namespace -j

Deleting a namespace

$ bld namespaces:delete my-namespace

Deleting a namespace does not automatically delete the apps inside it—remove or move those first.

When to use namespaces

Namespaces sit alongside teams and pipelines as another way to organize your infrastructure:

• Teams control who has access to a set of apps.
• Pipelines group the different deployment stages (review, staging, production) of a single app.
• Namespaces group apps by an arbitrary boundary you define—for example, all apps belonging to a single customer in a multi-tenant setup, or all infrastructure for a specific internal project.

If you don’t have a specific need to segment apps this way, you likely don’t need to create namespaces—most apps run fine at the team/pipeline level covered in Deploying Applications and CI/CD & Pipelines.