exe.dev vs Islo

exe.dev and Islo both give each machine its own VM with root and Docker, and neither has a built-in desktop. exe.dev is a flat-priced pool of persistent dev boxes in nine regions. Islo is a metered agent sandbox whose gateway controls and logs every outbound call, on Islo's cloud or your own.

The companies and products

exe.dev

exe.dev, made by Bold Software, Inc., rents Linux VMs for developers and AI agents that you reach over SSH and HTTPS.

You reserve a pool of vCPUs and memory, and your VMs share it. You can also start standalone VMs billed by the second. Each VM is KVM-isolated with Cloud Hypervisor, boots from a container image in about two seconds, and has root, systemd and Docker. It comes with Claude Code, Codex, Pi and exe.dev's own Shelley agent. It suits developers who want a persistent dev box or a sandbox for their agents.

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. “20th cheapest of 361” means 19 of the other 360 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 workloadexe.dev: 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. exe.dev turns on nested virtualization on request, and Islo documents none, so Android emulators fit boat best. On both, a visible desktop is a VNC stack you install yourself.
267th of 365, with limits
$3,721 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
All three fit always-on assistants. exe.dev keeps the VM running in its pool. Islo can pause an idle one with its memory and wake it on the next request. boat keeps a sandbox running with auto-stop off (default 1 hour), billed at full rate while it runs.
20th cheapest of 361
$3,833 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
231st of 336, with limits
$175 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 sandboxes for your users at once: exe.dev Personal stops at 50 VMs, and Islo publishes no limit (launch coverage reported 50 on Team), so ask Islo first. boat fits on its $100 plan with token-protected URLs, within its daily start limits.
252nd of 349, with limits
$1,234 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
260th of 349, with limits
$5,250 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
Islo has a built-in Harbor integration, its Harbor docs show 300 trials at once, and gateway rules can stop trials from looking up answers. exe.dev runs evals as plain VMs. boat runs up to 2,000 sandboxes at once on its $2,000 plan.
280th of 359, with limits
$1,050 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
Islo bills only while a runner is up, which suits CI. exe.dev pools bill whether jobs run or not, but its standalone VMs bill per second. On boat each CI job counts as a start; the $20 plan includes 200 a day.
289th of 374, with limits
$504 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
For one box that stays on, exe.dev's flat pool comes to $35 a month against $420 on Islo's hourly meter. boat comes to $26 a month with auto-stop off on a paid plan.
24th cheapest of 371
$35 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 exe.dev nor Islo has a built-in desktop. On both you install Xvfb and a VNC server yourself, and your own tooling drives it. boat streams a built-in 60 fps desktop with Chrome that agents can see and click.
270th of 367, with limits
$1,055 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
Islo ships a browser-use capability inside the sandbox, and on exe.dev Shelley's tool drives a headless Chromium. boat adds a visible desktop and a computer-use API.
187th of 356, with limits
$530 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
187th of 343, with limits
$278 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
165th of 327, with limits
$5,490 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
51st of 351, with limits
$264 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

Featureexe.devIsloboat
IsolationKVM VM with Cloud Hypervisor on rented bare metal; you cannot choose the kernelA microVM with its own kernel for every sandboxFull VM with its own kernel, on physical hosts dedicated to boat (AMD Ryzen 7 9700X and Ryzen 9 9950X); vCPUs are shared
Docker and nested virtualizationRoot, systemd and Docker; nested virtualization off by default, on request from supportDocker inside and sudo; no /dev/kvm or nested virtualization documentedDocker, root, systemd and /dev/kvm on every sandbox
Desktop and computer useNot built in; you can install a desktop and VNC yourself, and Shelley's browser tool drives a headless ChromiumBrowser-use capability built in; no desktop or computer-use API; you can install Xvfb and VNC with a setup scriptBuilt-in 60 fps desktop and Chrome, computer use and browser control, embeddable stream
Snapshots and backupsDisk replicated in the region; on-demand disk backups to your own S3 bucket, with restore (preview)Snapshot a running sandbox's files and start new sandboxes from itDisk saved every minute while running and at each stop; saved snapshots as templates
Pause and wakeA stopped standalone VM pays nothing for CPU and memory and keeps its disk; pools bill either wayPause keeps files, processes and memory; can pause after idle time and resume on the next exec, file access or webhookNo compute charge while stopped; disk kept at least 14 days; a resume is like a reboot (memory and processes are not kept)
Forkcp copies a VM's disk and config into a new VMStart new sandboxes from a snapshot of a running oneFork a running sandbox from its last 1-minute snapshot
Custom imagesBoots from your own Docker image in about two secondsBuilt from a container imageStart from boat's image or a saved snapshot; you cannot boot your own Docker or OCI image
Coding agentsClaude Code, Codex, Pi and Shelley; Shelley takes prompts through the API, others run through the HTTPS exec APIClaude Code, Cursor CLI and Codex; factory lines run agent steps with events, steer and follow-ups, on a schedule, webhook or GitHub, Slack, Linear and Jira eventsSeven harnesses including Claude Code, Codex and OpenCode, with a prompt, steer and events API and TypeScript and Python SDKs
MCP serverYes, at exe.dev/mcpNot documentedNo
Inbound trafficHTTPS proxy for ports 3000 to 9999, one of them public; SSH; no public IP or raw TCPHTTPS share links anyone with the URL can open, expiring after 24 hours by default; SSH and port-forward through the CLIUp to 50 HTTPS URLs per sandbox, token-protected by default; SSH; raw ports over IPv6; no dedicated IPv4
Outbound rules and logsOpen by default; an egress policy can block everything but attached integrationsGateway allows or denies by host, path and HTTP method, can deny by default, and logs every request to your SIEMOpen internet; no provider-side allowlist; usage API and spend limits
Keeping keys out of the sandboxIntegrations inject secrets at the network edge for any HTTP host, S3, GitHub and a large catalogGateway injects stored credentials into outbound requests for any host; credentials never reach the sandboxOptional paid AI credentials proxy ($1 a day plus $1 per 1,000 requests) for model providers and HTTPS APIs you register
Sandboxes at oncePersonal: 50 VMs in total, standalone VMs included; a Work pool holds up to 1,000 VMs, and pools above 32 vCPU need approvalNo limit on the pricing page; launch coverage reported 5 on Free and 50 on Team; paused ones do not count100 to 2,000 running sandboxes by plan, plus start limits per minute, hour and day
Regions9 regions in the US, Europe, Asia and AustraliaIslo's cloud (regions not published, set per account), or your own cloud account with BYOCGermany, Finland and France; no US or Asia region; you cannot pick one
Every feature Battleships tracks (43)
Featureexe.devIsloboat
Full VM (own kernel)YesYesYes
Docker insideYesYesYes
Nested virtualizationWith your own setupNo documented wayYes
RootYesYesYes
SystemdYesNot publishedYes
Desktop GUINo documented wayWith your own setupYes
BrowserYesYesYes
Computer-use APINo documented wayNo documented wayYes
SSHYesYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsNo documented wayYesYes
Fork/cloneYesYesYes
Live fork (no pause)YesYesYes
Memory forkNo documented wayNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopNo documented wayYesNo documented way
Wake on requestNo documented wayYesNo documented way
HTTPS preview URLsYesYesYes
Raw TCP inboundNo documented wayNo documented wayYes
Public IPv4No documented wayNo documented wayNo documented way
Egress allowlistWith your own setupYesNo documented way
Secret proxyYesYesYes
Secret proxy for any APIYesYesYes
Preinstalled agentsYesYesYes
Agent harness APIYesYesYes
MCP serverYesNo 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
BYOCYesYesNo documented way
Open sourceNo documented wayNo documented wayNo documented way
Scoped API keysYesNot publishedYes
Spend limitsNot publishedYesYes
Usage per sandbox (API)YesYesYes
Audit logsNot publishedYesNo documented way
SSOYesYesNo documented way
SOC 2No documented wayNot publishedNo documented way
HIPAANo documented wayNot publishedNo documented way
EU data residencyYesNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

exe.devNot measured
IsloNot measured
boat28.06 runs/s

exe.dev and Islo are not in the public 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 does not promise a CPU model.

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. exe.dev 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.

Scenarioexe.dev, 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
$35 · Personal$101 · Free$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$35 · Personal$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
$1,848 · Personal$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
$530 · Personal · 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,050 · Personal · with limits$3,053 · Team · with limits$8,800 · $2000/mo · with limits

exe.dev: exe.dev sells reserved pools that your VMs share, from $15 a month on Personal, and a pool bills the same whether its VMs are busy or idle. Standalone VMs bill per second at $0.105 per 2 vCPU / 4 GiB per hour.

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. Egress has no published price.

Islo: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. Sandboxes bill per second while they run, busy or idle. A stopped sandbox has no compute charge; extra saved snapshots and the AI credentials proxy still charge while it is stopped.

Limits in those scenarios

exe.dev Personal stops at 50 VMs in total. Islo publishes no concurrency limit, and launch coverage reported 50 running on Team. So 300 sandboxes for your users and 1,000 short jobs at once need a higher limit on both. exe.dev's flat pool is billed whether used or not, and Islo publishes no egress price, so every Islo total here leaves egress out. boat allows 100 to 2,000 sandboxes at once by plan. The $20 plan includes 200 starts a day; extra starts cost $0.03 to $0.07 each, and above 6 times the included number a start fails with 429. So boat does not fit 1,000 short jobs at once either.

Scenarioexe.devIsloboat
One coding agent, workdays
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
One agent that never stops
  • flat pool: the tier is billed whether used or not
  • egress price not published
None for this scenario
50 agents in parallelNone for this scenario
  • egress price not published
None for this scenario
Sandboxes for your users
  • Personal: max 50 concurrent
  • Team: max 50 concurrent
  • egress price not published
None for this scenario
1,000 short jobs at once
  • Personal: max 50 concurrent
  • 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 exe.dev when

you want a flat-priced dev box or VM pool that stays on, in a region near your users, booted from your own Docker image.

  • A flat price for a box that stays on. For one machine running all month, exe.dev's flat 4 vCPU pool is $35 a month, where Islo's hourly meter comes to $420.
  • Regions around the world. Useful if you need a known region: exe.dev runs in nine regions across the US, Europe, Asia and Australia.
  • Your own Docker image and an MCP server. exe.dev boots each VM straight from your own Docker image, and its MCP server lets tools like Claude Code control VMs.

Use Islo when

you need per-host egress rules with a log of every outbound call, agents that pause with memory and wake on a request or event, or your own cloud account.

  • Egress rules and request logs. Useful if you must control what agents reach: Islo allows or blocks each host, path and method, and logs every call.
  • Pause with memory, wake on request. Useful for agents that sit idle between tasks: Islo pauses them with memory kept and resumes on the next request.
  • Agent runs started by events. Islo's factory lines start agent steps on a schedule, a webhook, or GitHub, Slack, Linear and Jira events.

Where boat fits

If your agents need more than a shell, look at boat. exe.dev and Islo both give you a VM with no built-in screen. boat adds a built-in desktop, /dev/kvm on every sandbox, up to 50 token-protected URLs, a disk snapshot every minute and up to 2,000 sandboxes at once, on full VMs in Germany, Finland and France.

A screen agents can see and use

Neither exe.dev nor Islo has a built-in desktop. On either you install a VNC stack and a control layer yourself before an agent can check a UI. boat streams a 60 fps desktop with Chrome and a computer-use API.

Nested virtualization on every sandbox

Android emulators and tools that start their own VMs need /dev/kvm. exe.dev turns it on when you ask support, and Islo's docs do not mention it. boat exposes /dev/kvm on every sandbox.

Ports you can host on

exe.dev makes one port public through its HTTPS proxy, and Islo share links are open to anyone with the URL and expire after 24 hours by default. boat serves up to 50 token-protected URLs per sandbox, plus raw ports over IPv6.

Use boat when your agents need a built-in desktop, /dev/kvm, ports you can host on and the disk saved every minute, on up to 2,000 full VMs at once. Compare it one to one: boat vs exe.dev 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 exe.dev cheaper than Islo?

In the three scenarios that fit both, yes. One coding agent on workdays comes to $35 vs $101 a month, one agent running all month to $35 vs $420, and 50 agents in parallel to $1,848 vs $4,863. Islo totals leave out egress, which has no published price. boat comes to $20, $26 and $317 for the same three.

Which is faster, exe.dev or Islo?

We cannot say: neither is in the public benchmarks we use. In StarSling's run of 3 October 2026, boat did 28.06 V8 Web Tooling runs/s at 4 vCPU / 8 GB, on a Ryzen 9 9950X host.

Can exe.dev and Islo run Docker?

Yes. exe.dev VMs have root, systemd and Docker, and Islo runs Docker inside its microVMs with sudo. exe.dev turns on nested virtualization on request from support; Islo documents none. boat has /dev/kvm on every sandbox.

Do exe.dev or Islo have a desktop for computer use?

Not built in. On both you can install Xvfb and a VNC server yourself. Islo has a browser-use capability, and exe.dev's Shelley agent drives a headless Chromium. boat streams a built-in 60 fps desktop with Chrome and has a computer-use API.

Can I limit what an agent reaches on the internet?

Yes on both. Islo's gateway allows or denies traffic by host, path and HTTP method and logs each request. An exe.dev egress policy can block everything except attached integrations. boat sandboxes have open internet with no provider-side allowlist.

Where do exe.dev and Islo run?

exe.dev has nine regions in the US, Europe, Asia and Australia. Islo runs on its own cloud, with regions set per account and not published, or inside your own cloud account with BYOC. boat runs on machines in Germany, Finland and France, and snapshot copies can be stored outside the EU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons