# Capsule

Capsule is a multi-tenancy and access-control tool for Kubernetes that provides tenant-based namespace isolation and policy-based resource sharing. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4838/capsule

## Description

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: Helm.

## Health score

75/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 1 day ago)
- Popular: 67 (2,222 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 85 (no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 8.1/10)

## Links

- GitHub: https://github.com/projectcapsule/capsule
- Kubernetes (Helm): https://artifacthub.io/packages/helm/projectcapsule/capsule
- Official website: https://projectcapsule.dev/

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/4838/capsule), the self-hosted and open-source app directory.
