Daytona vs Islo

Daytona starts every sandbox as a container and sells Linux VM, Windows and GPU classes on top, in the US and the EU. Islo, from Incredibuild, gives every agent its own microVM on Islo's cloud or in your own cloud account, with a gateway that decides what each agent can reach.

The companies and products

Daytona

Daytona is a cloud for running AI-generated code: you create sandboxes from code through its API and SDKs.

By default a Daytona sandbox is a Linux container with its own namespaces and reserved vCPU, memory and disk. You can also pick a Linux VM class (pause, fork, memory snapshots, /dev/kvm), a Windows VM class, a GPU class with Nvidia and AMD cards, or macOS sandboxes in early access. It is built for teams that run agent code, code interpreters and evals through Python, TypeScript, Ruby, Go or Java SDKs.

Founded
2023

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. “19th cheapest of 365” means 18 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 workloadDaytona: price rankIslo: price rankboat: price rank
Software factory
100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month
Daytona fits on its Linux VM class and ranks 19th. Islo runs Docker but documents no /dev/kvm, and launch coverage reported 50 running sandboxes on Team, so it is a compromise (60th). boat ranks 5th with /dev/kvm and a desktop on every sandbox.
19th cheapest of 365
$4,111 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: boat ranks 6th, Daytona 31st and Islo 37th. Islo can pause an idle assistant with its memory and wake it on the next request. On boat you turn auto-stop off (default 1 hour).
31st cheapest of 361
$6,104 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
Daytona fits one-minute runs best here (31st): it creates 300 to 600 sandboxes a minute with no plan fee. Islo's reported Team limit of 50 running sandboxes (155th) and boat's start limits (189th) make big bursts a compromise.
31st cheapest of 336
$271 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 of 2 vCPU at once is more than Daytona's Tier 4 pool of 500 vCPU (153rd) and more than the 50 running sandboxes reported for Islo's Team plan (172nd), so both need higher limits. boat ranks 3rd.
153rd of 349, with limits
$2,000 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
134th of 349, with limits
$8,261 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
boat ranks 10th. Islo has a built-in Harbor integration and gateway rules that stop trials from looking up answers, but its reported 50-sandbox Team limit makes this a compromise (203rd); Daytona's vCPU pool is too small (192nd).
192nd of 359, with limits
$2,000 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
boat ranks 2nd and Islo 124th. Daytona caps one sandbox at 4 vCPU by default, so an 8 vCPU CI job needs a raised limit (309th, compromise).
309th of 374, with limits
$805 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
200th of 371, with limits
$245 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
Daytona has a VNC desktop and a computer-use API on Linux and Windows (29th). On Islo you install Xvfb and a VNC server with a setup script (63rd). boat ranks 7th with a 60 fps desktop you can embed.
29th cheapest of 367
$1,198 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
114th of 356, with limits
$598 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
42nd cheapest of 343
$404 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
203rd of 327, with limits
$8,073 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
18th cheapest of 351
$2,000 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
Only Daytona fits (19th): it rents Nvidia and AMD GPUs by the hour. Neither Islo nor boat has GPUs.
19th cheapest of 102
$1,190 a month
Not 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

FeatureDaytonaIsloboat
IsolationContainer with its own namespaces by default; Linux VM and Windows VM classes with a hardware virtualization boundaryEvery sandbox is a microVM with its own kernelEvery sandbox is a full VM with its own kernel; vCPUs are shared
CPU speed (V8 Web Tooling Benchmark, 4 vCPU / 8 GB, StarSling run of 3 October 2026)21.52 runs/s on the Linux VM class (shared rank 2); the default container class has no resultNot in the public benchmarks we use28.06 runs/s, second of 15 (shared rank 2), on an AMD Ryzen 9 9950X host
Docker and nested virtualizationDocker in all classes; /dev/kvm only on Linux VMs, with KVM turned on for your organizationDocker inside and sudo; /dev/kvm and nested virtualization are not documentedDocker, root, systemd and /dev/kvm on every sandbox
Desktop and computer useVNC desktop (xfce4) and a computer-use API on Linux and WindowsBrowser-use capability built in; no built-in desktop or computer-use API; a setup script can install Xvfb and a VNC server1920x1080, 60 fps desktop and Chrome, computer tools for agents, embeddable stream
Pause and wakeLinux VM and Windows classes pause and resume with memory keptPause keeps files, processes and memory; can pause after idle time and wake on the next exec, file access or webhookStop and resume; resume reboots from disk (no memory snapshots)
ForkLinux VM and Windows classes fork with memory kept; containers start new sandboxes from filesystem snapshotsSnapshot a running sandbox's files, then start new sandboxes from itFork a running sandbox from its last 1-minute snapshot
Files after a stopWhole disk kept and billed while stopped; containers auto-archive after 7 days stopped (free)Files kept; a paused or stopped sandbox has no compute chargeDisk saved every minute and at each stop; no compute charge while stopped; kept at least 14 days, longer with a saved snapshot
Reaching the sandboxHTTPS preview URLs on any port, token-protected or public; SSH; no public IPHTTPS 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, token-gated by default; SSH; raw ports over IPv6, and over IPv4 only on sandboxes with their own IPv4
Outbound internet rulesTier 1 and 2 reach only package registries, git hosts and AI APIs; Tier 3 and up get open internet plus per-sandbox domain or CIDR allowlistsOpen by default; optional gateway profiles allow or deny by host, path and HTTP method, with default deny, rate limits and per-request logsOpen internet on every plan; no provider-side allowlist (firewall rules inside the VM)
Keeping keys out of the sandboxSecrets proxy swaps placeholders in HTTPS request headers for allowed hostsGateway injects stored credentials into outbound requests for any hostOptional AI credentials proxy ($1 a day plus $1 per 1,000 requests) for model providers and HTTPS APIs you register
Coding agentsYou set it up: guides install agents and run them through process execClaude Code, Cursor CLI and Codex preinstalled; factory lines run agent steps with events, steer and follow-upsSeven harnesses preinstalled, with a prompt, steer and events API
GPUs and WindowsNvidia and AMD GPUs on-demand or preemptible; Windows VM sandboxesNo GPUs; Linux onlyNo GPUs; Linux VMs, with Wine for Windows apps
Sandboxes at onceAn org-wide pool of 10, 100, 250 or 500 vCPU from Tier 1 to Tier 4, not a sandbox countNo 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
Where it runsUS and EU, plus dedicated regions or your own machinesIslo's cloud (regions not published, set per account), or your own cloud account with BYOCGermany, Finland and France; no US or Asia region, no region choice
Every feature Battleships tracks (43)
FeatureDaytonaIsloboat
Full VM (own kernel)No documented wayYesYes
Docker insideYesYesYes
Nested virtualizationYesNo documented wayYes
RootYesYesYes
SystemdNot publishedNot publishedYes
Desktop GUIYesWith your own setupYes
BrowserYesYesYes
Computer-use APIYesNo documented wayYes
SSHYesYesYes
Persistent diskYesYesYes
Pause/resumeYesYesYes
Automatic snapshotsYesYesYes
Fork/cloneYesYesYes
Live fork (no pause)No documented wayYesYes
Memory forkYesNo documented wayNo documented way
Custom image (Docker or snapshot)YesYesYes
≥24 h sessionsYesYesYes
Idle auto-stopYesYesNo 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 allowlistYesYesNo documented way
Secret proxyYesYesYes
Secret proxy for any APIYesYesYes
Preinstalled agentsYesYesYes
Agent harness APINo documented wayYesYes
MCP serverYesNo documented wayNo documented way
GPUYesNo documented wayNo documented way
WindowsYesNo 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 logsYesYesNo documented way
SSOYesYesNo documented way
SOC 2YesNot publishedNo documented way
HIPAAYesNot publishedNo documented way
EU data residencyYesNo documented wayNo documented way
Zero data retentionNot publishedNot publishedYes

Performance

Daytona21.52 runs/s
IsloNot measured
boat28.06 runs/s

Islo is not in the public benchmarks we use, so we cannot say how it compares. In StarSling's run of 3 October 2026 (run 37073680030), the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, boat did 28.06 runs/s (second of 15) and Daytona's Linux VM class 21.52. Both share rank 2, so the run cannot separate them. Daytona's default container class has no result. 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.

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. Daytona measured on: Linux VM sandbox (same rates; KVM / nested virt per-org feature). 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. Islo is 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.

ScenarioDaytona, 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
$56 · Tier 3 ($500 top-up)$101 · Free$20 · $20/mo
One agent that never stops
4 vCPU / 8 GB, 50 GB disk, running 24/7 all month
$245 · Tier 3 ($500 top-up)$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,682 · Tier 3 ($500 top-up)$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
$2,000 · Tier 4 ($2,000 top-up every 30 days) · 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
$2,000 · Tier 4 ($2,000 top-up every 30 days) · with limits$3,053 · Team · with limits$8,800 · $2000/mo · with limits

Daytona: Daytona bills per second for the vCPU, memory and disk you reserve, including while a sandbox starts or stops, and keeps billing the disk while it is stopped. You pay from a prepaid wallet with no plan fee and $200 of free compute: open internet needs a $500 top-up (Tier 3), and the biggest pool needs $2,000 every 30 days (Tier 4).

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 running idle sandbox bills until a pause-after-idle timer fires, and that timer can only be set when the sandbox is created. 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. A stopped sandbox has no compute charge, but saved snapshots above the included count and the AI credentials proxy still charge. The $20 plan includes 200 starts a day; extra starts cost $0.03 to $0.07.

Limits in those scenarios

Daytona limits the total vCPU, memory and disk running at once (500 vCPU at Tier 4), and Islo's Team plan is reported at 50 running sandboxes. So 300 sandboxes for your users and 1,000 short jobs at once fit neither without higher limits. Daytona also caps one sandbox at 4 vCPU / 8 GB by default and opens the internet only from Tier 3. Neither publishes an egress price, so their totals here leave egress out. On boat the $2,000 plan includes 90 starts a minute and 2,400 a day and refuses starts above 270 a minute, so the 1,000-job burst does not fit boat either.

ScenarioDaytonaIsloboat
One coding agent, workdays
  • egress price not published
  • Tier 1 (email verified), Tier 2 (card + $25 top-up) reach only an allowlist (package registries, git, AI APIs)
  • egress price not published
None for this scenario
One agent that never stops
  • egress price not published
  • Tier 1 (email verified), Tier 2 (card + $25 top-up) reach only an allowlist (package registries, git, AI APIs)
  • egress price not published
None for this scenario
50 agents in parallel
  • egress price not published
  • Tier 1 (email verified), Tier 2 (card + $25 top-up) reach only an allowlist (package registries, git, AI APIs)
  • egress price not published
None for this scenario
Sandboxes for your users
  • max 500 vCPU running at once (needs 600)
  • max 1,000 GiB running at once (needs 1,200)
  • egress price not published
  • Tier 1 (email verified), Tier 2 (card + $25 top-up) reach only an allowlist (package registries, git, AI APIs)
  • Team: max 50 concurrent
  • egress price not published
None for this scenario
1,000 short jobs at once
  • max 500 vCPU running at once (needs 2,000)
  • max 1,000 GiB running at once (needs 4,000)
  • egress price not published
  • Tier 1 (email verified), Tier 2 (card + $25 top-up) reach only an allowlist (package registries, git, AI APIs)
  • 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 Daytona when

your agents need GPUs, Windows or forks that keep memory, or must run in the US or the EU, and a container by default works for you.

  • GPUs by the hour. Useful if your agents train or test models: Daytona rents Nvidia and AMD GPUs by the hour, from RTX 4090 to B300.
  • Windows and memory forks. Useful if you need Windows desktops or forks that keep memory: Daytona's VM classes do both.
  • Published regions and many fast starts. Daytona runs in the US and the EU, can run sandboxes on machines you bring, and creates 300 to 600 sandboxes a minute by tier.

Use Islo when

every agent must get its own VM by default, with per-host egress rules, a log of every outbound call, and sandboxes that pause with memory and wake on request.

  • A VM for every agent by default. Useful if you want kernel isolation without picking a class: every Islo sandbox is a microVM with its own kernel.
  • 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.

Where boat fits

If your agents do long, real work like installs, builds, tests, Docker and emulators, and running in Germany, Finland or France works for you, look at boat. Every boat sandbox is a full VM with /dev/kvm, a built-in desktop and ports you can host on, at $0.036 an hour for 4 vCPU / 8 GB.

A full VM with /dev/kvm on every sandbox

Daytona's default sandbox is a container with its own namespaces, and /dev/kvm needs its VM class plus KVM turned on for your organization. Islo has VMs but does not document /dev/kvm, so plan Android emulators elsewhere.

Ports you can host on

Daytona gives HTTPS previews but no public IP, and Islo share links are open to anyone with the URL and expire after 24 hours by default. boat serves up to 50 token-gated HTTPS URLs for as long as the sandbox lives.

Room for a fleet with open internet

Daytona opens the internet only from Tier 3, a $500 top-up, and its biggest pool is 500 vCPU. Islo's Team plan is reported at 50 running sandboxes. boat has open internet on every plan and 100 to 2,000 sandboxes by plan, with start limits per plan.

Use boat when your agents do real work for hours: installs, builds, tests, Docker and emulators on a full VM with a built-in desktop, ports you can host on and coding agents you drive through one API. Compare it one to one: boat vs Daytona 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 Daytona cheaper than Islo?

In the scenarios we priced, yes. One coding agent on workdays comes to $56 a month on Daytona and $101 on Islo, and one agent running all month to $245 against $420. 50 agents in parallel come to $2,682 against $4,863. On boat the same three come to $20, $26 and $317. Islo totals leave out egress, which Islo does not price publicly.

Which is faster, Daytona or Islo?

Islo is not in the public benchmarks we use, so we cannot say. In StarSling's run of 3 October 2026 at 4 vCPU / 8 GB, Daytona's Linux VM class did 21.52 runs/s and boat 28.06; the run cannot separate them. Daytona's default containers have no result.

Are Daytona and Islo sandboxes containers or VMs?

Daytona's default sandbox is a Linux container with its own namespaces, with Linux VM and Windows VM classes you can choose. Every Islo sandbox is a microVM with its own kernel, built from a container image. boat gives every sandbox a full VM.

Can Daytona and Islo run Docker?

Yes, both run Docker inside a sandbox. Daytona gives /dev/kvm only on its Linux VM class with KVM turned on for your organization; Islo does not document /dev/kvm. boat has Docker, systemd and /dev/kvm on every sandbox.

Can I limit what an agent reaches on the internet?

On both. Daytona from Tier 3 lets you limit each sandbox to chosen domains or IP ranges. Islo's gateway allows or denies by host, path and HTTP method and logs each request. boat has open internet with no provider-side allowlist; with its optional paid credentials proxy on, the real keys of supported model providers stay out of the sandbox.

Where do Daytona and Islo run?

Daytona runs in the US and the EU, plus dedicated regions and your own machines. Islo runs on its own cloud, with regions set per account and not published, or inside your own cloud account with BYOC. boat runs in Germany, Finland and France; you cannot pick a region, and snapshot copies can be stored outside the EU.

Try boat

Install the CLI, then run boat new.

7-day free trial

More comparisons