vcluster

loft-sh/vcluster

vCluster creates tenant clusters: fully isolated environments delivered as managed Kubernetes, or as the foundation for Slurm, Ray, Run:ai and inference clusters. Each gets its own API server, CRDs and RBAC, and runs on an existing cluster or standalone on bare metal. CNCF Certified Kubernetes.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 1, 2026
1 day ago
Ship score
99/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 11,260 → 11,321 (Aug 18 – Sep 29, 2026)
+38 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
11.3K
Forks
611
Open issues
170
Watchers
55
Primary language
Go
Created
Apr 8, 2021
Owner
loft-sh · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#cloud-native#helm#k3s#k8s#kubectl#kubernetes#multi-tenancy#platform-engineering#vcluster#virtual-clusters

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 73%, hosted offering 77%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-01This is the badge for loft-sh/vcluster, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/loft-sh/vcluster.svg)](https://ossean.com/loft-sh/vcluster)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.