Capsule

Capsule is a multi-tenancy and access-control tool for Kubernetes that provides tenant-based namespace isolation and policy-based resource sharing.

  • Infrastructure
  • Tools & Utilities
Capsule is a multi-tenancy and access-control tool for Kubernetes that provides tenant-based namespace isolation and policy-based resource sharing.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 1 day ago
Popular
672,222 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
85no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 8.1/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
2,222
Open issues
55
Last commit
2026-11-20
Latest release
v0.15.2
License
Apache-2.0
Activity
declining

Checked today - source: GitHub (projectcapsule/capsule)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Run make up in the playground folder From the playground directory, run make up to start a two-node Kind cluster (a small Kubernetes cluster in Docker) and install Capsule, Capsule Proxy, Dex login, Headlamp dashboard, and ingress-nginx. If you skip this, none of the web apps or APIs are running, so the installation looks broken or unreachable. source
  • Wait before applying permit requests In the playground, install the GlobalResourcePermitTemplate examples, then wait until solar-system appears in each template's status.namespaces before submitting the sample permit requests as alice. If you submit too early, the allowed namespace is not ready and the request can fail or leave you without the expected access. source
  • Set LAPTOP_HOST_IP before dev setup When using the dev setup, replace <YOUR_LAPTOP_IP> with your computer's local IP, for example LAPTOP_HOST_IP=192.168.1.10, before running make dev-setup. Capsule sends admission webhooks (checks that can allow or block changes) to that address, so a wrong IP makes webhooks fail and normal cluster actions can stop working. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where should I start if a Capsule command or app does not behave as expected?

Start with the troubleshooting documentation, which covers common setup, serve, deploy, auth, secret, and runtime issues.

Are tenant-level policies applied to every namespace in the tenant?

Yes. Network and Security Policies, Resource Quota, Limit Ranges, RBAC, and other policies defined at the tenant level are inherited by all namespaces in the tenant.

Can Capsule be managed in a declarative GitOps workflow?

Yes. Capsule is completely declarative and GitOps ready.

Does Capsule require additional management layers, plugins, or customized binaries?

No. It provides multi-tenancy with a native Kubernetes experience without introducing additional management layers, plugins, or customized binaries.

Answers sourced from docs.capsule.new, github.com, projectcapsule.dev

Community

Collected 48 days ago - public community threads