mcpField
P
Purgatorium (p9m)

Purgatorium (p9m)

Remote
csakaszamok.github.ioCloud & Infra6Updated today

About Purgatorium (p9m)

Purgatorium (p9m) is a self-hosted platform for teams to create Docker sandboxes and deploy apps with Docker Compose. It gives each sandbox its own Docker daemon and app URLs, with idle sleep and wake-on-request behavior.

Key features

  1. 01Create isolated Docker sandboxes
  2. 02Deploy apps with Docker Compose
  3. 03Provide public app URLs and TLS addresses
  4. 04Sleep idle sandboxes and wake on requests
  5. 05Use sandbox-scoped agent tokens

Use cases

  1. 01Give an agent a sandbox for app deployment
  2. 02Host team apps on a self-managed server
  3. 03Expose deployed apps through individual URLs

MCP support

Purgatorium includes an MCP server through which agents can operate sandboxes. Its tools can be called through the MCP server or directly using JSON-RPC over HTTP.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://{purgatorium_host}/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://{purgatorium_host}/mcpAuth required

Tools

Details

From the project README

README image Purgatorium (p9m)

Docs CI 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 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.)

Creating a sandbox and opening its app, in real time: about 10 seconds

  • 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, an MCP server and a Claude Code plugin (/plugin marketplace add csakaszamok/p9m, then /p9m:init connects each project: Purgatorium shows the line under Let your agent deploy…)
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 with a laptop, a cloud PaaS, a shared Docker host, Coolify and a VM for everyone · How it works: 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.

Creating a sandbox with curl and calling its app, in real time: about 7 secondsClaude Code creates a sandbox through the MCP server and checks its app, in real timeThe MCP server called with curl: tools/list, then create_sandbox, in real time

With curl through the API, by an agent over the MCP server, 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):

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 and the compose plugin, no clone needed (check the host first):

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

Then sign in at http://p9m.<HOST_DOMAIN> (by default http://p9m.lvh.me).

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 / Dokploy on your own servers
  • Untrusted code from strangers → a microVM sandbox such as E2B or Docker Sandboxes (until Purgatorium has a Kata runtime)
  • Writing code in a cloud IDE → Coder or GitHub Codespaces
  • An agent running short scripts from an SDK → E2B or Daytona

More in how it compares.

Documentation

csakaszamok.github.io/p9m: tutorials, install, configuration, let your agent deploy, MCP, API, and llms-full.txt for agents.

Security: where sysbox is installed, sandboxes run without a privileged container; without it they fall back to the privileged dind, which suits a team that trusts each other, not hostile code. On a shared server install sysbox and set ALLOWED_RUNTIMES=sysbox (details).

Contributing · Security issues · AGPL-3.0

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). 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). Versions up to 0.10.3 were released under Apache-2.0.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.