sandboxes

Most powerful & affordable cloud VMs for long-running agents

Spawn thousands of cloud computers with a browser, persistent files, for your agents, without having to manage the entire infra yourself.

$curl -fsSL https://neev.ai/sandbox/install | sh
$sandbox new
# sandbox created
{
"desktop_stream": "https://neev.ai/s/fire3e5cc756",
"hosted_url": "https://dsmv.hosting.neev.ai",
"machine_ip": "203.0.113.42"
}
# ssh user@203.0.113.42 to get inside

Full VMs in the cloud

Run Docker, systemd, databases, and cron inside. Feels like a true dev machine.

ubuntu14:02
$ uname -a
Linux vm 6.8.0-generic x86_64
$ lsb_release -d
Ubuntu 24.04 LTS
$ nproc && free -h | head -2
8
Mem: 32Gi 2.1Gi 29Gi
$ systemctl is-system-running
running
$

Integrated desktop & browser

To open your web apps, games, 3D scenes, IDE, and more, on a crisp 60fps virtual desktop.

Treasure Hunt ×+
‹ ›neev.ai/treasure···
TREASURE HUNT
Clue 3 of 5 — follow the dotted trail
DIG HERE

Run agents inside, from outside

Prompt, observe and wrap any harness running in the sandbox, from the outside, with our CLI, API or SDKs.

agent — ~/project
›→
✳
working..
✶
working..
◼
working..
Pre-installed in every sandbox
DockerVS CodeChromeGhosttyGitHub CLIRustNode.jsBun
•Lowest price•

Plan required, from $20/mo

  • •$20 plan = $20 of sandbox time.
  • •Billed per second, only while running.
  • •100 to 2,000 sandboxes at once, by plan.
  • •Out of time? $20 packs, auto-refilled.
1
at once
$0.036/ hour

4 vCPU · 8 GB RAM · 50 GB for your files

Neev$0.036/h1x
Novita$0.233/h6x
Freestyle$0.264/h7x
exe.dev$0.280/h8x
E2B$0.331/h9x
Daytona$0.331/h9x
Blaxel$0.331/h9x
Codespaces$0.360/h10x
Cloudflare$0.360/h10x
Modal$0.476/h13x
Islo$0.600/h17x
Runloop$0.634/h18x
Vercel Sandbox$0.682/h19x
Learn more →
•Highest performance•

The same Node.js build & test loop, 1,000 runs, 4 vCPU / 8 GB everywhere. Time it takes:

Neev36 s1x
Daytona54 s1.5x
Modal66 s1.8x
E2B89 s2.5x
Learn more →
•Simple API•
$ sandbox newSpin up a sandbox
$ sandbox ssh / scpShell in, copy files
$ sandbox execRun a command, no SSH
$ sandbox promptRun Claude Code or Codex
$ sandbox eventsPoll agent messages & tool calls
$ sandbox hostPublic HTTPS URL for a port
$ sandbox desktopDesktop & browser at 60 fps
$ sandbox stop / resumeSnapshot, pause billing

…and many more useful features: fork, named snapshots, port forwarding, webhooks, API keys, secrets, teams, auto-stop.

For programmatic use, see the API and SDKs.

Enterprise

Dedicated, private DGX Spark deployments.

Talk to sales →

Run the whole fleet on hardware that is yours alone — a private NVIDIA DGX Spark cluster, isolated from every other tenant. Your models, your data, your network. Nothing leaves the box.

Private execution

Every sandbox runs inside your dedicated DGX Spark cluster — single-tenant, air-gappable, no shared infrastructure.

Customer-owned models

Bring your own weights and serve them in-house. Your models never leave your hardware or touch a third-party API.

Controlled environment

Lock down egress, images, and secrets to match your compliance posture — SOC 2, HIPAA, or fully air-gapped.

Agent testing before deployment

Rehearse full agent runs in an isolated replica of production, so you validate behaviour before anything ships.

•GPU-enabled sandboxes•

Enterprise sandboxes run on GPU — the same DGX Spark silicon, exposed straight to your agents for inference, fine-tuning, and GPU-bound test suites.

Chip
NVIDIA GB10 Grace Blackwell
Memory
128 GB unified
Compute
1,000 AI TOPS (FP4)
Networking
200 GbE, cluster-ready

On the roadmap

Built for fleets of agents.

Unified MCP server

In design

One MCP endpoint that brokers every tool and data source your agents reach — managed, versioned, and audited in one place.

Secret management & credential isolation

In design

Per-sandbox credential scoping, so an agent only ever sees the secrets it needs and never another tenant's.

Per-agent spend caps & access control

In design

Hard budget ceilings and role-based access per agent, so a runaway loop can't burn the account.

Auto-resume

Shipping

Stopped sandboxes wake themselves the moment a request or scheduled agent run arrives — no manual resume.

Set sail.

Spin up your first sandboxes in minutes.

Questions

Am I billed when a sandbox is stopped?+

No. Stopping snapshots the sandbox and pauses billing. Resume any time in a few seconds.

Is the $20/mo a per-sandbox minimum?+

No. It is the account total, and it converts into 555 hours of machine time to spend across any number of sandboxes.

Where do sandboxes run?+

In secure, single-tenant VMs across US and EU regions. Your data and snapshots stay in-region.

What survives stop and resume?+

Your files, installed packages, and enabled systemd services. Hand-run processes need a restart.

Can I give sandboxes to my own users?+

Yes. Create them no-env so they receive none of your account's secrets and stay confined to themselves.