Isolated sandboxes for AI agents
Create a sandbox through an API for code interpreters, coding agents, previews and CI. Each one is an isolated machine on your own infrastructure.
A few lines of code
Create a sandbox, run commands, write files and open a port as a URL with the TypeScript SDK.
npm install @pyodev/sandboxOr give your AI assistant sandbox tools through Pyo's MCP server.
claude mcp add --transport http pyo https://your-pyo/api/mcpimport { Sandbox } from "@pyodev/sandbox";const sbx = await Sandbox.create({ template: "node-22", ttl: "1h" });const out = await sbx.exec("node -v");await sbx.files.write("/app/index.js", "console.log('hi')");const url = await sbx.ports.open(3000);What you can run
One sandbox for each session or job. Make as many as you need and throw them away when you're done.
Code interpreter
Run the code a model writes and send back what it prints.
Coding agents
Give an agent its own machine to clone a repo, install packages and run tests.
Live previews
Open a port and share what an agent builds as a live URL.
Browser and computer use
Run a browser for an agent to drive, away from your own machines.
Evals
Start many sandboxes at once to test agents and models on real tasks.
Untrusted code in CI
Run pull requests and user code without putting your servers at risk.
How it runs
Strong isolation that starts fast, on servers you own.
- to start from a template
- < 50 ms
- to start from a template
- of memory per idle sandbox
- ~7 MB
- of memory per idle sandbox
A microVM for each sandbox
Each sandbox is its own Firecracker microVM. Servers without KVM use gVisor. Pyo picks one for you.
Dedicated sandbox servers
Sandboxes run on their own servers, outside your clusters. Your services never share a machine with them.
Starts from a template
A sandbox starts from a template in under 50 ms. Its root disk is shared and its memory is copy-on-write.
A safe network
Internet is on. Your own network and cloud metadata are always blocked.
Ports become URLs
Open a port and get a live HTTPS URL, public or private.
Pause and resume
Pause a sandbox to keep its memory and files, and pick up where it left off.
Why Pyo
Sandboxes that live next to your services and databases.
On your own infrastructure
Code and data never leave your servers, so sandboxes can work with private data.
One bill and one dashboard
Services, databases and sandboxes, all in one place.
- Coming later
Promote to a service
When an agent builds something good, deploy it as a Pyo service with a domain, HTTPS and autoscaling.
- Coming later
Scoped database access
Let a sandbox read one of your Pyo databases through a read-only connection. Off by default.
Get Pyo running on your server
Run Pyo on any machine, from your laptop or VPS to a dedicated server or homelab.
curl -fsSL https://pyo.dev/install.sh | bash