# projectcapsule/capsule

Multi-tenancy and policy-based framework for Kubernetes.

Repository: https://github.com/projectcapsule/capsule
Canonical: https://ross.abutalabs.com/products/capsule
Homepage: https://projectcapsule.dev/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, multi-tenancy, operator, tenant, namespaces, kubernetes-namespaces, multi-tenant-operator, kubernetes-operator
Last push: 2026-08-26T19:59:57+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 99, longevity 100
- inputs: {"age_days": 2256, "days_push": 7, "days_rel": 8, "gap_med": 7.0, "n_releases_24m": 37}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2162, forks 217 (observed 2026-08-28T04:06:21.048983+00:00)

## What it is
Capsule is a Kubernetes Operator that turns a single cluster into a shared multi-tenant platform by grouping namespaces into Tenant abstractions with inherited RBAC, quotas, and admission policies. It is a CNCF Sandbox project written in Go that enforces governance via Kubernetes admission controllers without custom binaries or extra tooling.

## Use cases
- run multiple teams on a single kubernetes cluster with strong isolation
- prevent cluster sprawl by sharing one cluster across departments
- let developers self-provision namespaces within assigned boundaries
- enforce image registries and security contexts via admission policies
- propagate rbac roles and network policies across tenant namespaces
- manage cpu memory and storage budgets per tenant

## When to choose
- you need hierarchical multi-tenancy on a single kubernetes cluster
- you want policy enforcement using only native kubernetes primitives
- you prefer a declarative GitOps-ready operator over custom tooling
- you want to give teams self-service while admins keep control

## When to avoid
- you need hard isolation between tenants with separate control planes
- you run a single-tenant cluster with no namespace governance needs
- you require multi-cluster tenant management rather than in-cluster tenancy

## Facets
- artifact type: framework
- maturity: active
- function: middleware, security, configuration-management, deployment
- domain: cloud-computing, self-hosted
- platform: cloud, self-hosted, go
- tags: kubernetes-operator, multi-tenancy, policy-enforcement, tenant-management, namespace-governance, rbac, resource-quotas, gitops, cncf-sandbox, containers, devops, kubernetes, docker

## Member repositories
- projectcapsule/capsule (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:21.048983+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:50:14.544431+00:00, confidence not recorded.
  - readme: https://github.com/projectcapsule/capsule (fetched 2026-08-28T04:06:21.048983+00:00, sha 0c82e29f79c7)
  - homepage: https://projectcapsule.dev/ (fetched 2026-08-29T10:30:01.444555+00:00, sha 0c324acc4325)
  - site_page: https://projectcapsule.dev/docs (fetched 2026-08-29T10:30:01.453536+00:00, sha d9e5bca60706)
  - site_page: https://projectcapsule.dev/docs/overview (fetched 2026-08-29T10:30:01.455298+00:00, sha fcf2e8fbf19b)
- Data as of 2026-08-30T08:39:29.467469+00:00.