AI Platform
Every sandbox is its own microVM with a terminal, files, HTTPS previews and an optional desktop. Coding agents come preinstalled. Your agent creates one over MCP, the CLI or the REST API, gets the job done and deletes it.
Use cases
Agents install packages, start servers and run code nobody has reviewed yet. A sandbox gives them a machine for that, away from your laptop and your production apps.
Start Claude Code, Codex or another preinstalled agent in the web terminal and hand over the repo, away from your laptop.
Let the agent run what it wrote in a disposable microVM instead of on your machine or next to production.
Clone the repo, install, build and run the tests on a clean machine, then read the output and the exit code.
Turn any port into an HTTPS URL. Token-gated by default, public when you want to share it with your team.
The desktop images run XFCE and Firefox, streamed to your browser over noVNC, for agents that need a screen.
Give your own AI features a place to run code. Create, run and delete sandboxes over the REST API.
Images
All based on Ubuntu 26.04, with git, curl, Python and the Nodion CLI. Pick one when you create the sandbox.
Base
The default image. Bring the rest with your setup script.
Agents
Base plus Node.js 22 and eight coding CLIs. Sign in with your own account.
Desktop
XFCE with Firefox and a terminal, behind a token-gated noVNC preview.
Desktop Agents
The desktop plus all eight coding CLIs, for agents that need a browser and a shell.
On every sandbox
A full shell in the dashboard, one click from the sandbox page.
Run any command over the API and get its output and exit code, up to 15 minutes per call.
Read, write, edit, list, rename and delete files in the workspace without opening a shell.
Share a running dev server under its own HTTPS hostname, with a token or in public.
Environment variables and API keys, sealed at rest and injected when the sandbox boots.
Install what your project needs with a script that runs once on first boot.
Control
The dashboard, MCP, the CLI and the REST API all use the same sandbox endpoints.
Connect the hosted Nodion MCP server with a personal API key and your agent gets tools to create sandboxes, run commands, edit files and open previews.
# in Claude Code, with Nodion connected over MCP > create a sandbox, clone acme/shop and run the tests sandboxes.create checkout-fix, GP-G2-4GB, agents image sandboxes.exec git clone https://github.com/acme/shop sandboxes.exec npm ci && npm test 42 passed > start the app and give me a link sandboxes.exec nohup npm run dev -- --port 3000 & sandboxes.previews.create port 3000 https://3000-8f2c41d07b.euc.nodionsandbox.net
Setup for Claude Code and Cursor is on the coding agents page.
The nodion CLI covers the whole lifecycle, from create to delete.
# create a sandbox with the coding agents image and your Anthropic key nodion sandboxes create --name checkout-fix --region REGION \ --package-sku compute.session.gp-g2-4gb --image agents \ --secret-env ANTHROPIC_API_KEY=sk-ant-… # run a command nodion sandboxes exec SANDBOX_ID --cmd "cd /workspace && git clone https://github.com/acme/shop" # write a file into the workspace nodion sandboxes fs SANDBOX_ID --action write --path notes.md --content "hello" # share port 3000 as an HTTPS URL nodion sandboxes previews create SANDBOX_ID --port 3000
Install and sign in as described in the CLI docs.
Every sandbox endpoint lives under https://api.nodion.com/v2/sandboxes and takes a bearer token.
# create a sandbox curl -X POST https://api.nodion.com/v2/sandboxes \ -H "Authorization: Bearer $NODION_TOKEN" \ -H "X-Nodion-Project: $NODION_PROJECT" \ -H "Content-Type: application/json" \ -d '{"name": "checkout-fix", "region_id": "REGION", "package_sku": "compute.session.gp-g2-4gb", "image": "agents"}' # run a command, up to 15 minutes curl -X POST https://api.nodion.com/v2/sandboxes/$SANDBOX_ID/exec \ -H "Authorization: Bearer $NODION_TOKEN" \ -H "Content-Type: application/json" \ -d '{"cmd": ["npm", "test"], "dir": "/workspace/shop", "timeout_sec": 300}'
Files, logs, power, previews and environment variables have their own endpoints next to exec.
Built for untrusted code
Isolation
Each sandbox boots its own kernel on Cloud Hypervisor. The VMM runs jailed, with seccomp.
Network
Outbound internet over NAT, no access to your project's private network. Overlay mode opts in when the code should reach your databases.
Location
Sandboxes run in Frankfurt. Nodion is run by Nodion GmbH, a German company based in Stuttgart.
Project
Same project, team and invoice as your apps and databases. Personal API keys can be limited to sandbox read, write or exec.
Lifecycle
No servers to keep alive. A sandbox runs while someone works with it and waits on disk in between.
A sandbox lives up to 24 hours. Then it is deleted with its workspace, so nothing is left running.
Packages
Billed per second while running, never more than the monthly price. Sleeping sandboxes only pay for their workspace disk.
GP-G2-2GB
0,0139 € / hour
For scripts, tests and a single coding agent.
10,00 € per month of running time at most.
1 vCPU, 2 GB RAM, 16 GB workspace
GP-G2-4GB
0,0278 € / hour
For coding agents, builds and the desktop.
20,00 € per month of running time at most.
2 vCPU, 4 GB RAM, 32 GB workspace
GP-G2-8GB
0,0556 € / hour
For larger builds and test suites.
40,00 € per month of running time at most.
4 vCPU, 8 GB RAM, 64 GB workspace
GP-G2-16GB
0,1111 € / hour
For heavy builds and several services at once.
80,00 € per month of running time at most.
8 vCPU, 16 GB RAM, 128 GB workspace
Net prices, excl. VAT.
FAQ
A microVM with its own kernel, a workspace disk, a terminal, a files API, HTTPS previews and an optional desktop. You or your agent create it from the dashboard, over MCP, the CLI or the REST API, and running time is billed per second.
Every sandbox boots its own kernel on Cloud Hypervisor. The VMM runs jailed, with seccomp. In the default isolated mode a sandbox reaches the internet over NAT, but not your project's private network.
The Agents and Desktop Agents images ship Claude Code, Codex, OpenCode, Gemini CLI, Copilot CLI, Muse, Grok and Cursor CLI, plus Node.js 22. Sign in with your own account, or store your API keys as secret environment variables on the sandbox.
Yes, in overlay mode. The sandbox joins your project's private network and reaches databases at <slug>.internal and apps at <app>.app.internal. HTTPS previews and the browser desktop are available in isolated mode only.
Up to 24 hours from creation. Then it is deleted together with its workspace, so nothing is left running. After 5 idle minutes it goes to sleep and only its disk is billed. Commands, file calls, an open terminal and preview traffic count as activity, and the keepalive call keeps it awake. The next command or file call wakes it.
Pick one of four images based on Ubuntu 26.04: Base, Agents, Desktop or Desktop Agents. Install everything else with a setup script of up to 64 KiB that runs once on first boot.
In Frankfurt, Germany. Nodion is run by Nodion GmbH, a German company based in Stuttgart.
Running time is billed per second and never costs more than the package's monthly price. A sleeping sandbox only pays for its workspace disk. Delete it and billing stops.
No. Personal API keys can be limited to sandbox read, write and exec, so the agent can work with sandboxes and nothing else.
Earn up to 15 € in credit when signing up.
or with email
Product news, no spam. Unsubscribe anytime.
Successfully subscribed.