vCluster

What it is

vCluster creates virtual Kubernetes clusters that run inside a namespace of a host cluster. Each vCluster gets its own API server, control plane, and (mostly) its own view of resources — CRDs, RBAC, admission controllers — while actual pods still get scheduled onto the underlying host cluster's nodes. This gets you cluster-level isolation without the cost and operational overhead of provisioning a real cluster per team, tenant, or environment. It sits between "give everyone a namespace" (cheap but leaky) and "give everyone a cluster" (isolated but expensive and slow to provision).

Who builds it and why

vCluster is built by Loft Labs, a company that sells commercial tooling on top of the open-source project (multi-cluster management, vCluster Platform, policy/governance layers). The open-source core is Apache-2.0 licensed and is the actual engineering product — Loft's business model is support, a management plane, and enterprise features (SSO, audit, sleep mode automation, etc.) layered on top. This is a fairly standard open-core model, and the core project has stayed genuinely useful without commercial features being required for basic use.

Production readiness signal

11,198 GitHub stars and 184 contributors indicate real adoption and a healthy contributor base, not a single-vendor side project. Latest release v0.35.1 suggests active, iterative versioning rather than a 1.0 that's been coasting. Commit activity is current. CNCF maturity level is not publicly available — vCluster is not (as of this writing) a CNCF project, so you don't get that governance signal; you're relying on Loft Labs' continued commercial interest as the primary sustainability guarantee. Founding date is not publicly available, but the project has been in the CNCF ecosystem conversation long enough to have multiple major version lines and a mature feature set (k3s/k8s backing stores, HA control planes, pluggable sync). Treat it as production-viable for teams that have validated their specific sync/scheduling edge cases, not as a drop-in with zero surprises.

Who should use this

• Platform teams running internal developer platforms who need per-team or per-tenant cluster isolation without the cost of real clusters per tenant
• SaaS vendors offering "your own cluster" experiences to customers, where spinning up real clusters per customer isn't economically viable
• Teams doing ephemeral environments (PR previews, CI test clusters) where fast create/destroy matters more than full physical isolation
• Organizations hitting namespace-based multi-tenancy limits (CRD conflicts, cluster-scoped resource fights, RBAC sprawl) but not ready to operate dozens of real clusters

Who should NOT use this

• Teams needing hard security isolation between tenants — vCluster tenants still share the host cluster's kernel, node pool, and networking layer unless you pair it with additional sandboxing (gVisor, Kata, dedicated node pools). It is not a security boundary by itself.
• Shops running workloads with heavy dependency on cluster-scoped resources or custom schedulers that don't sync cleanly — sync edge cases with certain CRDs and admission webhooks are a known source of friction
• Teams with only a handful of tenants where namespaces + solid RBAC + resource quotas already solve the problem — added control-plane overhead isn't worth it at small scale
• Anyone expecting vCluster to reduce actual compute cost — it reduces cluster management overhead, not node/pod resource consumption

Alternatives

• Kamaji – runs Kubernetes control planes as pods for true multi-cluster management, more focused on hosted control-plane-as-a-service than in-namespace virtualization.
• Capsule – namespace-based multi-tenancy without virtual control planes; lighter weight but less isolation than vCluster.
• Real separate clusters (via cluster-api or managed cloud offerings) – maximum isolation, highest cost and operational burden, no sync edge cases to debug.

Pricing

The core vCluster project is fully open source under Apache-2.0 — no license cost, no feature gating on basic virtual cluster functionality. Loft Labs sells vCluster Platform (management UI, SSO, policy enforcement, sleep mode, air-gapped support) as a paid add-on for teams that need centralized control across many vClusters. You can run vCluster entirely free and self-managed indefinitely.