CodeSandbox SDK vs Islo

Both give each sandbox a microVM with its own kernel, and both keep memory across a pause. CodeSandbox SDK is built around VMs that hibernate and wake on the next HTTP request. Islo is built around coding agents whose outbound traffic can pass a gateway that allows, blocks, injects keys and logs.

The companies and products

CodeSandbox SDK

CodeSandbox SDK is an API from CodeSandbox, now a Together AI company, that starts sandboxed development VMs on the same infrastructure as the CodeSandbox editor.

Each sandbox is a Firecracker microVM built from a template or any Dockerfile. When it goes idle, it hibernates with a memory snapshot, and it resumes or forks from that snapshot in seconds. You drive it from a TypeScript SDK through terminals, commands, files and HTTPS hosts. Together's docs call it the deprecated offering and point new users to its successor, the together-sandbox SDK.

Islo

Islo is an agent sandbox and coding-agent factory from Incredibuild: each coding agent gets its own microVM, with network rules and credentials handled at a gateway.

An Islo sandbox is a Linux microVM with its own kernel, built from a container image, with Claude Code, Cursor CLI and Codex preinstalled. Outbound traffic can pass through a gateway that allows or blocks hosts, injects credentials and logs every request. Islo also runs factory lines: saved agents run steps on a schedule, on a webhook or on GitHub, Slack, Linear and Jira events. It runs on Islo's cloud or in your own cloud account.

Launched
May 4, 2026

Which use cases each one fits

For each use case, Battleships prices every sandbox provider on the same workload and sorts them from the cheapest monthly bill up. “32nd cheapest of 365” means 31 of the other 364 providers run that workload, with every feature it needs, for less. “With limits” means the provider runs it but misses something, so it is listed after every full match. Open a use case for its whole ranking and what each provider misses.

Use case and its workloadCodeSandbox SDK: price rankIslo: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Both run Docker inside their microVMs, but neither documents /dev/kvm, so Android emulators and nested VMs are not documented there. boat has /dev/kvm on every sandbox.
32nd cheapest of 365
$3,731 a month
60th of 365, with limits
$7,402 a month
5th cheapest of 365
$634 a month
Always-on AI employees
50 machines 24/7 · 2 vCPU / 4 GB
Both fit an assistant that lives on its machine. Islo installs the agents and pauses an idle sandbox with its memory. On CodeSandbox SDK you install the agent harness yourself. On boat, turn auto-stop off on a paid plan (default 1 hour).
50th cheapest of 361
$4,811 a month
37th cheapest of 361
$9,928 a month
6th cheapest of 361
$657 a month
Code interpreter bursts
100 at once · 1 vCPU / 2 GB · 200,000 sessions of 1 min a month
CodeSandbox SDK fits short code runs: VMs hibernate with memory and wake on the next request. Islo publishes no concurrency limit, so ask Islo before a large burst.
54th cheapest of 336
$642 a month
155th of 336, with limits
$503 a month
189th of 336, with limits
$2,000 a month
Sandboxes for your users
300 at once · 2 vCPU / 4 GB · 30,000 sessions of 23 min a month
300 user sandboxes at once is more than CodeSandbox SDK's 250 on Scale and the 50 reported for Islo's Team plan, so both need a higher limit. boat allows 300 at once on its $100 plan.
140th of 349, with limits
$1,707 a month
172nd of 349, with limits
$3,160 a month
3rd cheapest of 349
$209 a month
RL rollouts
1,000 at once · 2 vCPU / 4 GB · 1,000,000 sessions of 3 min a month
CodeSandbox SDK's memory forks let rollouts branch from one warm state. Islo snapshots files and starts new sandboxes from them. A boat fork copies the disk only.
341st of 349, with limits
$3,861 a month
174th of 349, with limits
$15,265 a month
39th of 349, with limits
$2,000 a month
Agent evals
250 at once · 4 vCPU / 8 GB · 15,000 sessions of 20 min a month
Both run evals. CodeSandbox SDK runs up to 250 VMs at once on Scale. Islo has a Harbor integration, its Harbor docs show 300 trials at once, and gateway rules can stop trials from looking up answers. boat runs up to 2,000 sandboxes at once on its $2,000 plan.
77th cheapest of 359
$1,335 a month
203rd of 359, with limits
$2,456 a month
10th cheapest of 359
$200 a month
CI runners
40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month
96th cheapest of 374
$860 a month
124th cheapest of 374
$1,507 a month
2nd cheapest of 374
$86 a month
24/7 dev boxes
1 machine 24/7 · 4 vCPU / 8 GB
Both keep a VM running with no session cap. Islo has SSH through its CLI; CodeSandbox SDK documents none. Neither has a built-in desktop or documents /dev/kvm; boat has both.
316th of 371, with limits
$240 a month
117th cheapest of 371
$402 a month
19th cheapest of 371
$26 a month
Computer-use agents
50 at once · 4 vCPU / 8 GB · 20,000 sessions of 15 min a month
Neither has a built-in desktop. On CodeSandbox SDK you add a VNC desktop to your Dockerfile; on Islo a setup script installs Xvfb and a VNC server. boat streams a 60 fps desktop with Chrome and a computer-use API.
54th cheapest of 367
$1,236 a month
63rd cheapest of 367
$2,210 a month
7th cheapest of 367
$200 a month
Browser-use agents
50 at once · 2 vCPU / 4 GB · 30,000 sessions of 10 min a month
125th of 356, with limits
$741 a month
151st of 356, with limits
$1,105 a month
7th cheapest of 356
$200 a month
Scraping & bots (startup scale)
50 at once · 1 vCPU / 2 GB · 100,000 sessions of 3 min a month
119th cheapest of 343
$871 a month
71st cheapest of 343
$748 a month
6th cheapest of 343
$90 a month
Mass scraping & bots (undetectable)
1,000 at once · 1 vCPU / 2 GB · 3,000,000 sessions of 2 min a month
194th of 327, with limits
$7,390 a month
266th of 327, with limits
$14,966 a month
73rd of 327, with limits
$1,800 a month
Parallel red teaming
200 at once · 2 vCPU / 4 GB · 5,000 sessions of 30 min a month
29th cheapest of 351
$505 a month
78th of 351, with limits
$746 a month
3rd cheapest of 351
$200 a month
GPU eval jobs
10 at once · 8 vCPU / 32 GB · 500 sessions of 30 min a month
Not ranked: misses a requirementNot ranked: misses a requirementNot ranked: misses a requirement
macOS agents
5 at once · 4 vCPU / 8 GB · 1,000 sessions of 20 min a month
Not ranked: misses a requirementNot ranked: misses a requirementNot ranked: misses a requirement

Key features

FeatureCodeSandbox SDKIsloboat
IsolationFirecracker microVM with its own kernelMicroVM with its own kernel, built from a container imageFull VM with its own kernel, on hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Docker and nested virtualizationDocker and root, built from any Dockerfile; /dev/kvm not documentedDocker inside and sudo; /dev/kvm and nested virtualization not documentedDocker, root, systemd and /dev/kvm on every sandbox
Pause and resumeHibernates with a memory snapshot; an HTTP request to a host wakes it with processes still runningPause keeps files, processes and memory; resumes on the next exec, file access or webhookDisk saved every minute and at each stop, kept at least 14 days; memory is not saved, so a resume is like a reboot
ForkFork a hibernated sandbox from its memory snapshot, or a running one that shares memory with its parentSnapshot a running sandbox's files, then start new sandboxes from itFork a running sandbox from its last 1-minute disk snapshot; memory is not copied
Shell accessTerminals, commands and files through the SDK; SSH is not documentedSSH and port-forward through the Islo CLISSH, plus exec and files over the API
Inbound accessHTTPS host per port, public by default, signed tokens for private sandboxes; raw TCP is not documentedHTTPS share links anyone with the URL can open, expiring after a TTL (24 hours by default)Up to 50 HTTPS URLs, token-gated by default; raw ports on the public IPv6 address (some sandboxes also have IPv4)
Desktop and browserNo built-in desktop; a headless Chromium template, and you can install a VNC desktop in your own DockerfileBrowser-use capability built in; no built-in desktop, and a setup script can install Xvfb and a VNC serverBuilt-in desktop and Chrome streamed at 1920x1080, 60 fps, with a computer-use API; no GPU
Coding agentsYou install your own agent in the template and run it through the commands APIClaude Code, Cursor CLI and Codex installed; factory lines run agent steps on a schedule, webhook or GitHub, Slack, Linear and Jira eventsSeven harnesses installed, including Claude Code and Codex, with a prompt, steer and events API
Outbound internet rulesOpen; no egress allowlist documentedOpen by default; optional gateway profiles allow or deny by host, path and HTTP method, with default deny, rate limits and content filtersOpen internet on every plan; no provider-side allowlist
Keeping API keys out of the sandboxSecrets passed in as environment variables; no credentials proxy documentedGateway injects stored credentials into outbound requests for any host; credentials never reach the sandboxOptional credentials proxy ($1 a day while on, plus $1 per 1,000 requests) for model providers and HTTPS APIs you register; other secrets still enter the sandbox
Request logsNo per-request outbound log documentedPer-request gateway logs of what each agent called and what was blocked, streamed to your SIEMUsage API; no per-request log of outbound calls
Sandboxes at once250 on Scale, more on EnterpriseNot on the pricing page; launch coverage (May 2026) reported 5 on Free and 50 on Team; paused ones do not count100 on $20 up to 2,000 on $2,000, plus start limits per minute, hour and day
Where it runsA country hint steers scheduling, but placement is not guaranteedIslo's cloud (regions not published, set per account), or your own cloud account with BYOCGermany, Finland and France; you cannot pick a region; no US or Asia region
Every feature Battleships tracks (43)
FeatureCodeSandbox SDKIsloboat
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationNo documented wayNo documented wayYes
RootYesYesYes
SystemdNot publishedNot publishedYes
Desktop GUIWith your own setupWith your own setupYes
BrowserWith your own setupYesYes
Computer-use APINo documented wayNo documented wayYes
SSHNo documented wayYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesYesYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo documented way
Wake on requestYesYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistNo documented wayYesNo documented way
Secret proxyNo documented wayYesYes
Secret proxy for any APINo documented wayYesYes
Preinstalled agentsNo documented wayYesYes
Agent harness APINo documented wayYesYes
MCP serverNo documented wayNo documented wayNo documented way
GPUNo documented wayNo documented wayNo documented way
WindowsNo documented wayNo documented wayNo documented way
Arm64No documented wayNo documented wayNo documented way
Self-hostingNo documented wayNo documented wayNo documented way
BYOCNo documented wayYesNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysNot publishedNot publishedYes
Spend limitsNot publishedYesYes
Usage per sandbox (API)No documented wayYesYes
Audit logsNot publishedYesNo documented way
SSOYesYesNo documented way
SOC 2YesNot publishedNo documented way
HIPAANo documented wayNot publishedNo documented way
EU data residencyNo documented wayNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

CodeSandbox SDKNot measured
IsloNot measured
boat28.06 runs/s

Neither CodeSandbox SDK nor Islo is in the public CPU benchmarks we use, so we cannot say which is faster. In StarSling's run of 3 October 2026 (run 37073680030), boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, second of 15. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. For start time, ComputeSDK measured CodeSandbox SDK at its default size: 11.76 s median with 100 starts at once (6 November 2026) and 2.33 s one at a time in its latest published run. Islo and boat are not in ComputeSDK.

V8 Web Tooling Benchmark at a 4 vCPU / 8 GB target, runs per second, higher is better. Source: StarSling's run of 3 October 2026 (run 37073680030), median of 5 sandboxes. Providers ran on different hardware in different regions. StarSling gives a shared rank when the run cannot separate two providers. Every boat sandbox in this run ran on an AMD Ryzen 9 9950X host. boat also places some sandboxes on AMD Ryzen 7 9700X hosts, which this run did not measure. CodeSandbox SDK and Islo are not in the public benchmarks we use, so we cannot say which is faster.

Pricing in five scenarios

Each bill is priced from the providers' public price lists by the open Battleships engine, with the cheapest plan that runs the scenario. Start limits, per-start fees and plan minimums are in the price, boat's included.

ScenarioCodeSandbox SDK, a monthIslo, a monthboat, a month
One coding agent, workdays
4 vCPU / 8 GB, 50 GB disk, 8 hours a day, 22 days a month, files kept between days
$193 · Scale$101 · Free$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$341 · Scale$420 · Free$26 · $20/mo
50 agents in parallel
50 machines of 4 vCPU / 8 GB at once, 8-hour sessions, 1,100 sessions a month, Docker inside
$2,500 · Scale$4,863 · Team$317 · $20/mo × 3 seats
Sandboxes for your users
2 vCPU / 4 GB, 30,000 sessions of 10 minutes a month, up to 300 at once
$815 · Scale · with limits$1,382 · Team · with limits$200 · $100/mo × 2 seats
1,000 short jobs at once
2 vCPU / 4 GB, 1,000 at once, 3 minutes each, 200,000 jobs a month
$1,632 · Scale · with limits$3,053 · Team · with limits$8,800 · $2000/mo · with limits

CodeSandbox SDK: You buy VM credits at $0.01486 each, and each size burns a fixed number per hour: 20 for a 4 vCPU / 8 GB VM, about $0.30. Billing is per started minute while the VM runs, including idle time before it hibernates. A hibernated VM has no VM charge. Larger teams pay a $170 monthly Scale platform fee, which is not usage credit. Prices as checked on 28 September 2026; CodeSandbox's pricing pages blocked our automated check on 8 November 2026.

Islo: Islo has no plan fee. It bills $0.07 per CPU-hour, $0.04 per GB-hour of memory and $0.0007 per GB-hour of disk while a sandbox runs. A paused or stopped sandbox has no compute charge. A running idle sandbox bills at full rate until a pause-after-idle timer fires, and that timer can only be set at creation. Billing granularity and egress prices are not published.

Islo: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs, busy or idle. The $20 plan includes 200 starts a day; each extra start costs $0.03 to $0.07. A stopped sandbox has no compute charge and keeps its disk for at least 14 days. Saved snapshots above the included count and the credentials proxy, while it is on, still charge.

Limits in those scenarios

CodeSandbox SDK's Scale plan caps at 250 VMs at once, and Islo's Team plan was reported at 50, so 300 user sandboxes and 1,000 short jobs at once need a higher limit on both. CodeSandbox SDK VMs have a 20 GB disk with no published price for more, and neither publishes an egress price, so their totals leave egress out. boat fits the 300 user sandboxes. It does not fit the 1,000-job burst: the $2,000 plan includes 90 starts a minute and 2,400 a day, extra starts are paid, and starts above 270 a minute fail with 429. boat never queues a start. Below about $20 of use a month, Islo costs less than boat's smallest plan.

ScenarioCodeSandbox SDKIsloboat
One coding agent, workdays
  • disk beyond 20 GiB: price unknown
  • egress price not published
  • egress price not published
None for this scenario
One agent that never stops
  • disk beyond 20 GiB: price unknown
  • egress price not published
  • egress price not published
None for this scenario
50 agents in parallel
  • egress price not published
  • egress price not published
None for this scenario
Sandboxes for your users
  • Scale: max 250 concurrent
  • egress price not published
  • Team: max 50 concurrent
  • egress price not published
None for this scenario
1,000 short jobs at once
  • Scale: max 250 concurrent
  • egress price not published
  • Team: max 50 concurrent
  • egress price not published
  • 2,400 starts/day included, paid above that (needs ~6,667)
  • 600 starts/hour included, paid above that (needs ~1,000)
  • starts above 90/min are paid, and starts above 270/min fail with 429

Which one should you use?

Use CodeSandbox SDK when

your sandboxes sleep between visits and wake on the next HTTP request with memory intact, or you fork many runs from one warm state, and you accept that Together calls this SDK deprecated.

  • Wake on the next request. For previews and code runs used in bursts: a hibernated VM wakes on an HTTP request with its memory and processes intact.
  • Forks that share memory. For branching many runs from one warm state, such as rollouts or test variants, without booting and setting up again.
  • Your own Dockerfile and published limits. Templates build from any Dockerfile, and Scale publishes its limit of 250 VMs at once.

Use Islo when

you run background coding agents and need per-host egress rules, keys injected at a gateway, a log of every outbound call, or sandboxes in your own cloud account.

  • Egress rules and request logs. For teams that must control what agents reach: Islo allows or blocks each host, path and method, and logs every call.
  • Keys stay at the gateway. For agents that call outside APIs: Islo injects stored credentials on the way out, so keys never sit inside the sandbox.
  • Coding agents installed. For teams running background agents: Claude Code, Cursor CLI and Codex come installed, with triggers from schedules, webhooks, GitHub, Slack and Linear.

Where boat fits

If your agents do real work for hours, with builds, emulators, a browser on a screen and servers other people reach, look at boat. Each sandbox is a full VM with SSH, /dev/kvm, a 60 fps desktop and hosting on up to 50 ports, with coding agents installed. boat runs up to 2,000 sandboxes at once on its $2,000 plan. It has no egress rules and keeps no memory across a stop.

Emulators and nested VMs

Neither CodeSandbox SDK nor Islo documents /dev/kvm, so Android emulators and tools that start their own VMs are not documented there. boat exposes /dev/kvm on every sandbox.

A screen agents can use

Neither has a built-in desktop or a computer-use API. On both, you install a VNC stack and a control layer in the image. boat streams a 60 fps desktop with Chrome and computer-use tools.

Ports that stay reachable

CodeSandbox SDK hosts are HTTPS only and public by default. Islo share links are public to anyone with the URL and expire after 24 hours by default. boat serves up to 50 token-gated HTTPS URLs and raw ports on the sandbox's IPv6 address; the IP changes at each resume.

Use boat when your agents need a whole machine: SSH, Docker with /dev/kvm, a 60 fps desktop for computer use, and ports others can reach, with up to 2,000 sandboxes at once on the $2,000 plan. Compare it one to one: boat vs CodeSandbox SDK and boat vs Islo.

boat's own limits
  • Plans start at $20 a month. The plan price comes back as VM time for that month. Unused time does not carry over. Source
  • Starts (create, fork, resume): the $20 plan includes 12 a minute, 60 an hour and 200 a day. The $2,000 plan includes 90 a minute, 600 an hour and 2,400 a day. Extra starts cost $0.03 to $0.07. A start fails with 429 above 3 times the included starts per minute, or 6 times per hour or per day. Source
  • A stopped sandbox has no compute charge. boat keeps its disk for at least 14 days. A saved snapshot keeps it longer; extra saved snapshots and the AI credentials proxy are paid. Source
  • Auto-stop defaults to 1 hour. You can turn it off on a paid plan. The trial allows 2 hours at most. Source
  • boat saves the disk every minute and at each stop. Memory, running programs and /tmp are not saved: a resume is like a reboot. A machine failure loses writes after the last good snapshot. Source
  • Machines run in Germany, Finland and France only. Snapshot copies can be stored outside the EU. Source
  • Public IPv6 and outbound IPv4. No dedicated IPv4. The IP changes at each resume. Source
  • Hosts are AMD Ryzen 7 9700X and Ryzen 9 9950X. vCPUs are shared. No GPU. You cannot boot your own Docker image. Source

Questions people ask

Is CodeSandbox SDK cheaper than Islo?

It depends on the shape. One coding agent on workdays comes to $193 a month on CodeSandbox SDK and $101 on Islo. One agent running all month is $341 against $420, and 50 agents in parallel are $2,500 against $4,863. boat comes to $20, $26 and $317 for the same three. Neither CodeSandbox SDK nor Islo publishes an egress price, so their totals leave it out.

Which is faster, CodeSandbox SDK or Islo?

Neither is in the public CPU benchmarks we use, so we cannot say. In StarSling's run of 3 October 2026, boat did 28.06 runs/s on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, on an AMD Ryzen 9 9950X host. boat also places some sandboxes on slower hosts.

Can CodeSandbox SDK and Islo run Docker?

Yes, both run Docker inside their microVMs with root or sudo. Neither documents /dev/kvm, so Android emulators and nested VMs are not documented there. boat has Docker, systemd and /dev/kvm on every sandbox.

Can I SSH into CodeSandbox SDK or Islo?

Islo gives SSH and port-forwarding through its CLI. CodeSandbox SDK connects through its SDK, Node and browser clients with terminals, commands and files; SSH is not documented. Every boat sandbox has SSH as well as an exec and files API.

Is CodeSandbox SDK still maintained?

CodeSandbox is now part of Together AI. Together's docs call this SDK deprecated and name together-sandbox as its successor. The last SDK release was 2.4.2 in December 2025. Self-serve sign-up still runs through CodeSandbox.

How many sandboxes can run at once?

CodeSandbox SDK allows 250 VMs at once on Scale. Islo's pricing page names no limit; launch coverage reported 50 running sandboxes on Team, with paused ones not counted. boat allows 100 on the $20 plan up to 2,000 on the $2,000 plan.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons