Skip to main content
Version: v5.0 Stable

What are Projects

A project is a policy boundary that groups clusters, spaces, and the users or teams who access them. Projects are where work happens, and they're the unit most users see day to day.

Projects divide a boundary rather than define the outermost one. On a platform that serves several organizations, a tenant is the outer boundary and a tenant admin divides it across projects. On a platform with no tenants, projects are the only boundary. Project permissions still scope project admins and members, but no tenant boundary constrains platform admins.

For internal platforms, projects map to teams, cost centers, or environments. For AI cloud operators serving several customers, give each customer a tenant and let them run their own projects inside it. A project on its own doesn't separate one customer's inventory, identities, or configuration from another's.

Which one do you need

Use projects alone when one group administers the whole platform. Add tenants when separate organizations share it and shouldn't see each other. See What are tenants.

Platform represents each project as a namespace in the management plane. That namespace holds cluster instances and project secrets, along with reconciled role bindings, access rules, quotas, integrations, and metadata. Project namespaces are internal to Platform and are distinct from namespaces that users create inside a cluster.

Members​

Every project has members: the users and teams authorized to access it. Only members (and global admins) can see or interact with resources inside a project. Each member is assigned a role that defines what they can do within the project.

Manage project members →

Allowed clusters​

Each project specifies which connected clusters its members can deploy clusters into. This lets you direct different teams to specific infrastructure, within what the tenant allows if you use one. For example, routing GPU workloads to a cluster with GPU nodes, or keeping a customer's resources in a specific region.

Configure allowed clusters →

Templates​

Projects define which templates members can use when creating clusters. Admins can set a default template, restrict members to an approved set, or allow all templates. This ensures clusters created within the project meet your configuration and security requirements.

Configure allowed templates →

Quotas​

Projects can define resource quotas that cap total compute and storage consumption across all clusters and spaces in the project. Quotas prevent any single project from consuming disproportionate infrastructure resources.

Configure project quotas →

Enforce storage limits inside a cluster →

Secrets​

Projects can store secrets that are shared across resources within the project. These are useful for distributing credentials, tokens, or configuration that multiple clusters need access to.

Manage project secrets →

Integrations​

Projects can integrate with HashiCorp Vault to sync Vault secrets into project secrets.

View the Vault integration →

Platform architecture →

View resources across all your projects →