Purgatory (p7y)
Official# <img src="ui/logo.svg" alt="" width="40" align="top"> Purgatorium (p9m)
[](https://csakaszamok.github.io/p9m/latest/) [](https://github.com/csakaszamok/p9m/actions/workflows/ci.yml) [](LICENSE)
> [!NOTE]
> **Early, before 1.0.** It works and is tested (CI on every change, releases with a changelog), but expect rough edges, and breaking changes between minor versions.
**Self-hosted sandboxes for your team and their AI agents: everyone gets their own Docker, every app gets a URL, idle sandboxes sleep.**
Think of it as a self-hosted Vercel for the apps your team and its agents spin up. Today you deploy with `docker compose`; [git-based builds](https://csakaszamok.github.io/p9m/latest/roadmap/) are on the roadmap.
**About 10 seconds** from *New sandbox* to your own Docker and a public URL for your app; a sleeping sandbox is back in under 10. (Measured with the images already pulled: the first sandbox on a new server also downloads them.)
<a href="docs/media/demo.gif"><img src="docs/media/demo-thumb.webp" alt="Creating a sandbox and opening its app, in real time: about 10 seconds" width="100%"></a>
- **Its own Docker daemon** for every sandbox (with a Portainer UI if you want one)
- **A public URL for every app**, and TLS addresses for Postgres, Redis and SSH
- **Sleeps when idle, wakes on the next request**; a delete archives, nothing is lost
- **Made for agents:** tokens limited to one sandbox, an [agent guide](docs/agent-guide.md), an MCP server and a [Claude Code plugin](https://csakaszamok.github.io/p9m/latest/claude-plugin/) (`/plugin marketplace add p9m-team/p9m`, then `/p9m:init <address>` gets each project a sandbox: users need no web UI, only the admin has one). `p9m-team/p9m` is the official marketplace: it points at this repository's `plugins/p9m`, so use that name, not this repository's
### Hide the complexity. Keep it simple. Focus on what matters.
Purgatorium abstracts away infrastructure complexity and operational overhead, providing an intuitive user experience that lets users focus on their work and business goals rather than managing the underlying technology.
**[Why Purgatorium, and how it compares](https://csakaszamok.github.io/p9m/latest/comparison/)** with a laptop, a cloud PaaS, a shared Docker host, Coolify and a VM for everyone · **[How it works](https://csakaszamok.github.io/p9m/latest/architecture.html)**: the components (Docker-in-Docker, frp, Traefik, Sablier), a sandbox's lifecycle and the path of a request
### The same from a script or an agent
All real runs, in real time; press one to watch it.
<table><tr>
<td width="33%"><a href="docs/media/api-curl.gif"><img src="docs/media/api-curl-thumb.webp" alt="Creating a sandbox with curl and calling its app, in real time: about 7 seconds" width="100%"></a></td>
<td width="33%"><a href="docs/media/mcp-agent.gif"><img src="docs/media/mcp-agent-thumb.webp" alt="Claude Code creates a sandbox through the MCP server and checks its app, in real time" width="100%"></a></td>
<td width="33%"><a href="docs/media/mcp-rpc.gif"><img src="docs/media/mcp-rpc-thumb.webp" alt="The MCP server called with curl: tools/list, then create_sandbox, in real time" width="100%"></a></td>
</tr></table>
With curl through the [API](https://csakaszamok.github.io/p9m/latest/api/), by an agent over the [MCP server](https://csakaszamok.github.io/p9m/latest/mcp/), and the MCP server by hand (JSON-RPC over HTTP, so even curl can call its tools).
## Try it on your laptop
With Docker Desktop, or Docker Engine and the compose plugin on Linux, and ports 80 and 443 free (on Windows, in Git Bash or WSL):
```bash
mkdir p9m && cd p9m
curl -fsSLO https://github.com/csakaszamok/p9m/releases/latest/download/docker-compose.yml
curl -fsSL https://github.com/csakaszamok/p9m/releases/latest/download/setup.sh | bash # prints the admin password
docker compose up -d
```
Open **http://p9m.lvh.me** (`lvh.me` and all its subdomains point to `127.0.0.1`, so no DNS to set up), sign in as administrator with the password `setup.sh` printed, and press **New sandbox**. The first one takes a minute or two while the images are pulled; after that about 10 seconds. Its app opens at its own `http://<name>-….lvh.me` address.
> **An app takes seconds to open the first time?** In Chrome, *Settings → Privacy and security → Security → Use secure DNS*: with "your current service provider" each new `*.lvh.me` name can wait for a slow or filtering resolver. Turn it off, or pick a provider such as Cloudflare (1.1.1.1).
To remove it: delete the sandboxes in the UI first (each is a compose project of its own, so the next step would leave them running), then `docker compose down -v` in the `p9m` directory, and delete the directory.
## Install
On a Linux host with Docker Engine, the compose plugin and [sysbox](https://github.com/nestybox/sysbox), no clone needed. First check the host; it changes nothing:
```bash
curl -fsSL https://github.com/csakaszamok/p9m/releases/latest/download/check-host.sh | bash -s -- dev.example.com
```
Then:
```bash
mkdir p9m && cd p9m
curl -fsSLO https://github.com/csakaszamok/p9m/releases/latest/download/docker-compose.yml
curl -fsSL https://github.com/csakaszamok/p9m/releases/latest/download/setup.sh | bash -s -- dev.example.com # .env with your domain and random secrets
docker compose up -d
curl -fsSL https://github.com/csakaszamok/p9m/releases/latest/download/check-host.sh | bash # again, in p9m: what is not secure yet
```
Then sign in at `http://p9m.<HOST_DOMAIN>` (by default `http://p9m.lvh.me`). Rather read the scripts before running them? Download them instead of piping them into `bash`: see [Install](https://csakaszamok.github.io/p9m/latest/install/).
## When to use something else
Purgatorium is for a team's apps and agents' deployments that should be up at a URL, cheaply, on your own server. For other jobs other tools fit better:
- **Production that must scale and stay up** → a cloud PaaS, or [Coolify](https://coolify.io) / [Dokploy](https://dokploy.com) on your own servers
- **Untrusted code from strangers** → a microVM sandbox such as [E2B](https://e2b.dev) or Docker Sandboxes (or Purgatorium's `kata` runtime on a host with KVM)
- **Writing code in a cloud IDE** → [Coder](https://coder.com) or GitHub Codespaces
- **An agent running short scripts from an SDK** → E2B or [Daytona](https://daytona.io)
More in [how it compares](https://csakaszamok.github.io/p9m/latest/comparison/).
## Documentation
**[csakaszamok.github.io/p9m](https://csakaszamok.github.io/p9m/latest/)**: [tutorials](https://csakaszamok.github.io/p9m/latest/tutorials/), [install](https://csakaszamok.github.io/p9m/latest/install/), [configuration](https://csakaszamok.github.io/p9m/latest/configuration/), [let your agent deploy](https://csakaszamok.github.io/p9m/latest/agents/), [MCP](https://csakaszamok.github.io/p9m/latest/mcp/), [API](https://csakaszamok.github.io/p9m/latest/api/), and [`llms-full.txt`](https://csakaszamok.github.io/p9m/latest/llms-full.txt) for agents.
> **Security:** sandboxes run under [sysbox](https://github.com/nestybox/sysbox), without a privileged container; install it on the server. For code you do not trust, the opt-in `kata` runtime runs each sandbox in its own VM (needs a host with KVM). The privileged `dind` runtime is for development only (Docker Desktop, a laptop) and is not allowed unless `ALLOWED_RUNTIMES` says so. Web apps in a sandbox open only for its owner unless labelled otherwise ([details](https://csakaszamok.github.io/p9m/latest/security/)).
[Contributing](CONTRIBUTING.md) · [Security issues](SECURITY.md) · [AGPL-3.0](LICENSE)
Free to use, also commercially, on your own servers or for your customers. Changed it and people use it over the network? Then they get your changed source too, under the same license ([AGPL-3.0](LICENSE)). Every product built on Purgatorium says so: *Based on Purgatorium (p9m)*, in its About page and its docs, is marked as changed, and does not take the names "Purgatorium" or "p9m" ([NOTICE](NOTICE)). Versions up to 0.10.3 were released under Apache-2.0.
TDQS
Scored across 38 tools
Tools are grouped cleanly by resource (sandboxes, files, mounts, SSH keys, tokens, registry, templates) and most actions are distinct. The only real overlap is the lifecycle family — sleep_sandbox/stop, wake_sandbox/start, deep_sleep_sandbox, keep_sandbox_awake, restart_sandbox, set_sleep_settings — where the descriptions carry the distinction rather than the names. An agent can resolve these, but it must read carefully.
The dominant pattern is verb_noun in snake_case (list_sandboxes, create_sandbox, delete_sandbox_file, add_sandbox_mount, generate_sandbox_ssh_key), applied consistently across resources. A few outliers break the pattern: sandbox_summary and project_dir_link are noun phrases, and who_am_i is an idiom rather than verb_noun. Minor deviations only.
38 tools is well past the comfortable 3-15 range and feels heavy; the surface area is genuinely broad (sandboxes, files, mounts, registry, keys, tokens, templates), so most tools do earn a place. Still, splitting into sub-surfaces or merging the many lifecycle verbs would reduce the cognitive load.
CRUD/lifecycle coverage is strong: sandboxes (create, get, list, restart, sleep/wake/deep-sleep, archive/delete, summary), files (list, read, write, mkdir, delete), mounts (list/add/remove), SSH keys, tokens, and registry images. Remaining gaps are small — no rename/move for files, no template create/update (arguably server-managed), and no sandbox duplication — all workaroundable.