AI Platform

Let AI agents work in isolated microVMs.

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.

  • 8 coding agents preinstalled
  • Desktop in the browser
  • Billed per second
  • Hosted in Germany

Use cases

Run the agent, the code it writes, or code for your users.

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.

Coding agents in the cloud

Start Claude Code, Codex or another preinstalled agent in the web terminal and hand over the repo, away from your laptop.

Run AI-generated code

Let the agent run what it wrote in a disposable microVM instead of on your machine or next to production.

Check a branch

Clone the repo, install, build and run the tests on a clean machine, then read the output and the exit code.

Preview what was built

Turn any port into an HTTPS URL. Token-gated by default, public when you want to share it with your team.

Computer use

The desktop images run XFCE and Firefox, streamed to your browser over noVNC, for agents that need a screen.

Code execution in your product

Give your own AI features a place to run code. Create, run and delete sandboxes over the REST API.

Images

Four images, ready on create.

All based on Ubuntu 26.04, with git, curl, Python and the Nodion CLI. Pick one when you create the sandbox.

Base

A clean Ubuntu.

The default image. Bring the rest with your setup script.

Agents

Coding agents installed.

Base plus Node.js 22 and eight coding CLIs. Sign in with your own account.

  • Claude Code
  • Codex
  • OpenCode
  • Gemini CLI
  • Copilot CLI
  • Muse
  • Grok
  • Cursor CLI

Desktop

A desktop in the browser.

XFCE with Firefox and a terminal, behind a token-gated noVNC preview.

Desktop Agents

Screen and agents.

The desktop plus all eight coding CLIs, for agents that need a browser and a shell.

On every sandbox

Everything an agent needs on one machine.

Web terminal

A full shell in the dashboard, one click from the sandbox page.

Commands

Run any command over the API and get its output and exit code, up to 15 minutes per call.

Files

Read, write, edit, list, rename and delete files in the workspace without opening a shell.

HTTPS previews

Share a running dev server under its own HTTPS hostname, with a token or in public.

Secrets

Environment variables and API keys, sealed at rest and injected when the sandbox boots.

Setup script

Install what your project needs with a script that runs once on first boot.

Control

Drive it from your agent or your code.

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.

Built for untrusted code

Isolation you do not have to configure.

Isolation

A microVM per sandbox.

Each sandbox boots its own kernel on Cloud Hypervisor. The VMM runs jailed, with seccomp.

Network

Isolated by default.

Outbound internet over NAT, no access to your project's private network. Overlay mode opts in when the code should reach your databases.

Location

Hosted in Germany.

Sandboxes run in Frankfurt. Nodion is run by Nodion GmbH, a German company based in Stuttgart.

Project

Next to your apps.

Same project, team and invoice as your apps and databases. Personal API keys can be limited to sandbox read, write or exec.

Lifecycle

Sleeps when idle, wakes on the next command.

No servers to keep alive. A sandbox runs while someone works with it and waits on disk in between.

  1. CreatePick a package, an image and a network mode. Billing starts once it runs.
  2. WorkRun commands, read and write files, open the terminal or a preview.
  3. SleepAfter 5 idle minutes the sandbox goes to sleep. Only its disk is billed.
  4. WakeThe next command or file call wakes it up again.

A sandbox lives up to 24 hours. Then it is deleted with its workspace, so nothing is left running.

Packages

Pay for the seconds it runs.

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

Questions and answers.

What is a Nodion sandbox?

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.

How are sandboxes isolated?

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.

Which coding agents are preinstalled?

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.

Can a sandbox reach my databases and apps?

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.

How long does a sandbox live?

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.

Can I use my own image?

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.

Where do sandboxes run?

In Frankfurt, Germany. Nodion is run by Nodion GmbH, a German company based in Stuttgart.

How is it billed?

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.

Does my agent need full access to my account?

No. Personal API keys can be limited to sandbox read, write and exec, so the agent can work with sandboxes and nothing else.

Give your agent a cloud.

Earn up to 15 € in credit when signing up.

Continue with GitHub

or with email

Stay in the loop.

Product news, no spam. Unsubscribe anytime.