Skip to main content
Version: main 🚧

Tenants overview

Enterprise
Available in these plansFreeDevProdScale
Multi-Tenancy

Free, Dev, Prod, and Scale are vCluster Platform license plans. Open source does not need a license or a Platform connection. See Compare open source and free tiers.

A tenant is a customer organization inside vCluster Platform. It sits above projects, and it's the boundary a platform admin uses to decide what one customer can see and provision.

Understand the tenant model →

When to use tenants​

Reach for tenants when more than one organization shares your platform and those organizations shouldn't see each other.

  • AI cloud operators selling capacity. Each customer becomes a tenant, and the boundary decides which node types, images, and clusters they can reach.
  • Enterprises running a platform for separate business units or subsidiaries, where each unit administers itself.
  • Anyone delegating administration. A tenant admin manages their own users, projects, and quotas without seeing the rest of the platform.

Tenants are optional. A platform with none behaves exactly as it did before, so a single internal platform with one trusted admin group doesn't need them.

Requirements​

Tenants require the Multi-Tenancy feature in your vCluster Platform license. Check Platform > Platform Config > License and Billing to confirm it's active.

Two license limits apply when a platform admin creates a tenant.

  • The Tenants limit caps how many tenants the platform can hold. The Free, Dev, and Prod plans allow three tenants, and the Scale plan has no limit.
  • The Users limit is checked as well, because creating a tenant always creates its admin user.

Both are checked on create only. Reaching either limit still leaves existing tenants editable.

What's in this section​

The create and configure page carries the full platform admin workflow, from creating the tenant through granting inventory and handing it to the tenant admin.

The branding page covers how a tenant's users get their own logo and colors, and which platform UI settings reach them.

The GitOps page covers which identity a GitOps tool should use for a tenant's resources, and the labels and names its manifests need.

The boundary reference covers how each platform resource behaves inside a tenant boundary, plus the naming and ownership rules.

Current limitations​

The following aren't supported yet. Plan around them rather than working around them.

Not supportedWhat to do instead
Tenants registering their own control plane clustersA platform admin registers the cluster and grants it to the tenant
Tenants authoring their own templatesA platform admin creates templates and grants them by label
Tenants authoring their own stack templatesA platform admin creates stack templates and grants them
Tenants creating their own connectorsA platform admin creates connectors and grants them
Tenants creating their own network environmentsA platform admin creates network environments and assigns them to the tenant
Per-tenant SSOTenant users sign in through the platform's identity provider
A branded sign-in page per tenantUse tenant branding, which applies after sign-in
Tenant admins setting their own brandingA platform admin sets the tenant's branding
Tenant quotas on anything but node typesCap the rest at project level, which the tenant admin controls