Analysis updated 2026-05-18
Deploy an internal team tool to your own servers using a compartment.yml config file.
Connect a Git repository so pushes to a branch automatically trigger a new deployment.
Set up single sign-on and role-based access for who can view or manage deployments.
Run a self-hosted alternative to managed cloud platforms for sensitive internal applications.
| compartmentdev/compartment | denissergeevitch/pole-chudes-2 | xuanyuanzhifeng/ai-video-agent | |
|---|---|---|---|
| Stars | 77 | 77 | 77 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | easy | hard |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | ops devops | developer | vibe coder |
Figures from each repo's GitHub metadata at analysis time.
Requires running the system on your own server infrastructure and packaging apps as containers.
Compartment is a self-hosted deployment system for software teams who want to run their own web apps and internal tools on their own servers, without paying for a managed cloud platform or building a custom deployment setup from scratch. It sits between your code repository and your running application, handling the steps that normally require custom plumbing: building the app, giving it a stable URL, managing who can access it, and keeping a history of each deployment. The core workflow is file-first. You add a small configuration file called compartment.yml to a project, then run a command to deploy it. If the app can be packaged as a container using Docker or a compatible build tool, Compartment can usually deploy it. You can also connect a Git repository so that pushing to a branch automatically triggers a new deployment without running commands manually. Access control is a first-class part of the system. Teams can use single sign-on, define roles and permissions for different team members, and keep an audit log of who deployed what and when. This is aimed at teams that have sensitive internal tools or data, where informal permission sharing through links or credentials is not acceptable. The project is organized as a set of packages: a command-line tool, a browser-based control panel for viewing and managing deployments, a background worker that carries out the deployment work, and an edge layer that handles incoming traffic and enforces access rules. The whole system runs on infrastructure you control, so you are not sending application traffic or data through a third-party service. Compartment is open source under the Apache 2.0 license.
A self-hosted deployment system that lets teams build, host, and manage web apps on their own servers, handling access control and deployment history without a managed cloud platform.
Mainly TypeScript. The stack also includes TypeScript, Docker, SSO.
Apache 2.0 lets you use, modify, and distribute the software, including commercially, as long as you keep attribution and license notices.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.