Sandboxes for coding agents · Hosted in Germany

Give every agent a computer of its own.

pols.so runs full Ubuntu virtual machines for coding agents and the people who work with them: root, systemd, Docker, a desktop with Chrome, Claude Code and Codex preinstalled. Start one in seconds, fork it in under one, and keep it all on servers in Germany.

Install the CLI

curl -fsSL https://pols.so/install.sh | sh
# a fresh Ubuntu 24.04 VM
$ pols new --name review
# run anything, output streams back
$ pols exec review -- make test
# a second copy, cloned in under a second
$ pols fork review --name review-b
# an HTTPS address for port 3000
$ pols host review 3000
# its desktop, in your browser
$ pols desktop review
# done for today: snapshot and stop
$ pols stop review

A real machine, not a container.

Agents get further when they can install what they need, run the whole stack and look at the result. A pols sandbox is a KVM virtual machine with its own kernel, so apt install, docker compose up, systemd services and a browser all behave the way they do on a workstation, and nothing an agent does there reaches your laptop.

You drive sandboxes from the pols CLI, the REST API, the TypeScript client, or straight from your agent over MCP. Stopped sandboxes keep their disk; usage is metered per second while they run.

What you get

  • Forks and templates in under a second

    Forks and templates are copy-on-write ZFS clones: the copy takes less than a second, and the fork answers on SSH about nine seconds later. Prepare a machine once, save it as a template, start the next ones from it.

    How forks work
  • Desktop and computer use

    Every sandbox has a 1920×1080 desktop with Google Chrome. Open it in your browser, let an agent take screenshots, click and type, or drive Chrome over CDP with Playwright or Puppeteer.

    More on computer use
  • HTTPS for every port

    Publish any port at its own HTTPS address. Ports are private by default and open with a short-lived login link; make one public when you want to share it. SSH works too.

    More on ports and SSH
  • Full Ubuntu VMs

    Ubuntu 24.04 with root, systemd and Docker, on its own kernel. Git, build tools, Python, Node.js and Go are installed, and so are Claude Code and Codex.

  • MCP server and agent skill

    pols mcp puts sandboxes in reach of Claude Code, Cursor, Codex and any other MCP client. The installer can add the pols skill and register the server, so asking for a VM is enough.

  • Vault

    Keep API keys and passwords in your organization's vault, encrypted with AES-256-GCM, and hand them to a sandbox by name instead of pasting them into command lines.

  • Outbound network control

    Choose per sandbox: the open internet, only the addresses you allow, or no network at all. Untrusted code gets exactly the reach you give it.

  • Hosted only in Germany

    Sandboxes, their disks, snapshots and templates stay on dedicated servers in German data centres. No hyperscaler underneath and no CDN in front.

  • GDPR by default

    Run by PEWEO Sàrl, an EU company in Luxembourg. No trackers, no third-party scripts, no access logs for the website, and a privacy policy you can read in five minutes.

How it works

  1. Install the CLI

    One command on macOS or Linux. It puts pols in ~/.local/bin and, if you use Claude Code, offers to add the agent skill and the MCP server.

    curl -fsSL https://pols.so/install.sh | sh
  2. Sign up and log in

    Sign up on my.pols.so with your email address; there is no password to remember. During early access we approve new accounts by hand. Then create an API key and store it.

    pols login
  3. Create a sandbox

    A fresh VM takes commands about ten seconds later. Or let your agent do it: over MCP it creates, forks and uses sandboxes on its own.

    pols new --name review
  4. Stop, resume, fork

    Stop a sandbox and its disk is snapshotted; resume it where it left off. Fork it to try two approaches side by side, then keep the one that worked.

    pols fork review --name review-b

The documentation covers the CLI, the API, MCP, templates, the vault and published ports.

Hosted in Germany. Actually.

pols runs on dedicated servers in Hetzner data centres in Germany, set up and operated by us. Your sandboxes, their disks, snapshots and templates never leave them. There is no cloud provider underneath and no CDN in front: requests to pols.so and to your sandboxes go straight to our machines.

Behind pols is PEWEO Sàrl, a small company in Luxembourg, so your contract partner and the law that applies are European too. What we process and why is in the privacy policy.

Data centres
Falkenstein and Nuremberg, Germany
Operator
PEWEO Sàrl, Luxembourg
Login emails
Lettermint, processed in the EU, no tracking
DNS
Cloudflare, DNS only: traffic never passes through it
Trackers and cookies on this site
None
What is kept where

Sizes, limits and pricing

Sandbox sizes
SizevCPUMemoryDisk
small24 GiB20 GiB
default48 GiB50 GiB
large816 GiB100 GiB
xlarge1632 GiB200 GiB
Default limits per organization
Running sandboxes5
Sandboxes in total20
Sandbox hours per month500
Saved templates10
Active API keys25

Pricing is coming soon.

Usage is metered per second while a sandbox runs. During early access, accounts are approved by hand; if you need more than the limits above, write to team@peweo.com.

Start with one machine.

Install the CLI, sign up, and give your agent somewhere to work.

curl -fsSL https://pols.so/install.sh | sh