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

Compartment - Open-source runtime for internal team software

by
UI Bakery
•
Compartment is a self-hosted open-source runtime for AI-built internal apps. It gives teams one place to run and share the apps, scripts, workers, and automations created with AI coding agents, on infrastructure they own. Use Cursor, Claude, Codex, or any stack your team already works with. Compartment turns the code into team-ready software with isolation, RBAC, SSO, and audit logs built in.

Add a comment

Replies

Best
Vladimir Lugovsky
Maker
📌
Hey Product Hunt, AI coding agents have made it much easier to create useful internal software: small admin apps, scripts, workers, dashboards, automations, and one-off tools that solve real team problems. But sharing those tools is still messy. They often stay on someone’s laptop, get deployed behind random links, run without clear ownership, or become hard to access, audit, and maintain once more people start depending on them. We built Compartment as an open-source, self-hosted runtime for this new wave of internal software. The idea is simple: your team can build with any AI coding agent or technology stack, then run and share the result from one place, on infrastructure you own. Compartment supports internal apps, scripts, workers, services, and automations, with isolation, RBAC, SSO, and audit logs built in. We’re launching today because we think AI-built internal tools need a proper home, not more ad hoc sharing. Would love to hear how your team is currently handling apps and automations built with AI agents.
Dmitry Nehaychik
Maker

I keep coming back to this: internal tools don't always start as "projects" anymore. They often start as a quick fix from the person closest to the pain, not as something planned by a central team weeks later.

That seems like a huge unlock, but also brings a new kind of chaos. For teams already seeing this happen: what do you actually do with these tools once they start being useful - where do they live, how do people discover/use them, and who ends up maintaining them?

kostya danovsky
Maker

The weirdest thing about AI-built tools is that many of them take less time to create than to make trustworthy.

Getting a prototype is easy now. Making it something another person on your team can safely use, maintain, and build on is still the real work.

That gap is a big part of why we built Compartment. We kept seeing useful internal apps appear very quickly, then get stuck in a limbo between “cool demo” and “something the team can actually depend on.”

Would love to hear if others here are running into the same problem.