Sometimes, giving users
access to namespaces is just not enough.

No Permission To Modify RBAC
No Way To Install CRDs (required to install many Helm charts)
Conflicting Cluster-Wide Resources (e.g. CRDs, ingress controller etc.)
No Permission To Access Any Cluster-Wide Resources
No Permission To Even List Your Own Namespaces

Virtual Clusters

Cluster-Wide Access But Within A Single Namespace.

vCluster Users

Create and use vClusters
Start vClusters On-Demand
Full Admin Access (including RBAC + CRDs)
Sleep Mode For Inactive Clusters

Platform Admins

Manage the host clusters
Self-Service For Engineers
Better Tenant + Workload Isolation
Higher Platform Stability (Cluster Sharding)

Works with any Kubernetes cluster

You can even test virtual clusters with Minikube or Docker Desktop.
Interested?

Try Virtual Clusters Today

Get started

or

Request a Demo
Architecture

Virtual clusters run on top of any k8s cluster

Kubernetes Platform

Host Cluster

The host cluster is the Kubernetes cluster in which the host namespace exists and which is used to start the containers of the virtual cluster.

Host Namespace

Every virtual cluster is contained within a single namespace of the underlying host cluster. If you remove the namespace, the virtual cluster will also be gone.

Virtual Cluster

Virtual clusters are super lightweight and start within seconds. They are fully functional Kubernetes clusters that run with a certified Kubernetes distribution.

Ready?

Install loft in 5 minutes

Get started

or

Request a Demo

Product

 GitHub Repository Request Demo Pricing

Documentation

 Quickstart Getting Started Architecture

Company

About Blog Press Brand Contact

Legal

Terms of Service Privacy Policy

All product and company names shown on this website are trademarks or intellectual property of their respective holders. Using them on this website does not imply any affiliation with or endorsement by them.