Projects

A project is the organisational unit that groups your containers together and gates access to the shared resources they depend on.

What a project contains

• Containers — the applications you deploy
• Attached vault items, configs, registries, and secrets — created at the organisation level, attached to one or more projects, then wired into individual containers. See Project Attachments for the full model.

Project isolation

Each project gets its own isolated environment on every region it runs in. Containers in one project cannot communicate with containers in another project. This provides a clean boundary between different applications or environments.

Resource quotas

Each project has configurable resource quotas that cap the total CPU and memory that containers within the project can consume across all replicas. Quotas are set by Bahriya administrators and are visible on the project detail page.

Handles and immutability

A project's handle is set at creation time and cannot be changed. It appears in:

• DNS hostnames for containers in the project
• Internal deployment pipelines

Choose a handle that reflects the long-term purpose of the project — you cannot rename it later.

Deleting a project

Deleting a project terminates all containers running within it and removes all associated resources (secrets, registries, DNS records) from every region. This action is irreversible.

See also

• Project Attachments — how vault items, configs, registries, and secrets reach the containers in a project
• Project Quotas