Compartment
Open-source runtime for internal team software
Start new thread

Compartment Enterprise - Securely share and scale custom internal apps and workflows

by
•
Compartment gives teams a self-hosted path from AI-built source code to a protected app URL. Developers deploy through the CLI or Git. With the new Kubernetes runtime, teams get isolated project namespaces, NetworkPolicies, gVisor-sandboxed builds and workloads, rolling deployments, durable recovery, and promotion without rebuilding. Operators can install it on a clean Ubuntu VM or an existing Kubernetes cluster while keeping infrastructure and data under their control.

Add a comment

Replies

Best
Maker
📌
Hi Product Hunt 👋 I’m one of the makers of Compartment. We started Compartment because coding agents made it easy for our team to build internal apps, scripts, and workers. Sharing those tools still required deployment, secrets, access control, isolation, and ownership. We wanted a self-hosted platform that handled this work for the team. Our first Product Hunt release ran workloads with Docker Compose on a single server. Beta use exposed limits in recovery and isolation, and adding another node would have meant writing our own orchestrator. We chose to replace the runtime. Compartment v0.10 now runs on Kubernetes. Operators can let the CLI provision k3s on a clean Ubuntu VM or install Compartment into an existing Kubernetes 1.30+ cluster. Developers don’t need to manage Kubernetes. Add a compartment.yml file and run compartment deploy, or connect a Git repository. Compartment builds the source, creates an immutable release, deploys it to an environment, and gives the app a protected URL. Teams can promote the same release or roll it back without rebuilding. Each project gets its own namespace and NetworkPolicies. Rootless BuildKit jobs build the source, while gVisor isolates builds and app workloads. SSO, scoped RBAC, encrypted variables, and audit logs live in the platform, so each internal tool doesn’t need to implement them. Compartment is open source under Apache 2.0 and runs on infrastructure you control. Thanks for taking a look. We'd love feedback from teams shipping internal software built with coding agents.