Islo vs Instabox
Islo and Instabox both give each agent its own microVM with root and Docker, and both pause a machine with its memory kept. Islo is a metered service with egress rules, request logs and coding agents built in. Instabox has a free plan for one machine, paid plans from $20 a month as usage credit, a VNC desktop on most templates and machines up to 32 vCPU.
The companies and products
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
Instabox
Instabox gives each AI agent its own Linux machine in the cloud. It has a free plan with one machine and paid plans from $20 a month plus usage.
Each Instabox machine is a Firecracker microVM with its own kernel, root and Docker. It starts from a template (agent-browser by default, universal, t3, herdr, orca, android, omarchy or ci), from your own snapshot, or from a Docker image that you import as a snapshot. The default size is 4 vCPU / 8 GiB, and paid plans go up to 32 vCPU / 64 GiB. You drive it from a CLI, a TypeScript SDK, an HTTP API or an MCP server, with SSH, mosh, HTTPS port URLs and a desktop for computer use.
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. “37th cheapest of 361” means 36 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 workload | Islo: price rank | Instabox: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month Instabox ranks 2nd and boat 8th for a software factory; Islo (48th) is a compromise because launch coverage reported 50 running sandboxes on Team. Neither Islo nor Instabox documents /dev/kvm, so Android emulators and VMs inside the sandbox need boat. Instabox has an android template that runs Android natively. | 60th of 365, with limits $7,402 a month | Cheapest of 365 $410 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB All three can keep a machine running all month. Islo and Instabox can pause an idle one with its memory kept: Islo wakes it on the next exec, file access or webhook, and Instabox on a port visit. boat keeps a sandbox running with auto-stop off (default 1 hour), billed at full rate while it runs. Instabox ranks 4th, boat 5th and Islo 40th. | 37th cheapest of 361 $9,928 a month | 4th cheapest of 361 $534 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 | 155th of 336, with limits $503 a month | 4th cheapest of 336 $56 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 boat ranks 2nd and Instabox 8th for sandboxes for your users. Instabox runs 100 machines at once on Pro, 200 on Builder and 500 on Team, so 300 at once needs Team. Islo publishes no limit, and launch coverage reported 50 on Team, so ask Islo first. | 172nd of 349, with limits $3,160 a month | 10th cheapest of 349 $500 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 | 174th of 349, with limits $15,265 a month | 16th of 349, with limits $845 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 Harbor integration and gateway rules that stop trials from looking up answers. Instabox runs 100 to 500 machines at once by plan. boat ranks 8th, Instabox 22nd and Islo 129th, where its reported 50-sandbox limit is the blocker. | 203rd of 359, with limits $2,456 a month | 34th cheapest of 359 $500 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 Instabox 3rd for CI, at $86 and $89 a month; Islo ranks 91st at $1,507. Instabox has a ci template and an android template; boat adds /dev/kvm for emulators. Each boat CI job counts as a start. | 124th cheapest of 374 $1,507 a month | 3rd cheapest of 374 $89 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB All three work as a cloud dev box over SSH. Instabox adds mosh, paste-anywhere SSH tokens and pause with memory, and ranks 8th at $24 a month. boat ranks 13th at $26 and Islo 80th at $402 on its hourly meter. | 117th cheapest of 371 $402 a month | 14th cheapest of 371 $24 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 Instabox has a VNC desktop with a browser on most templates, with a screenshot and click API; you bring the model. Islo has no built-in desktop, and you can install Xvfb and VNC yourself. boat streams a 60fps desktop with computer tools. Instabox ranks 4th, boat 8th and Islo 46th. | 63rd cheapest of 367 $2,210 a month | 4th cheapest of 367 $122 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 Instabox's default template is agent-browser. boat adds a visible Chrome on a 60fps desktop and a computer-use API. | 151st of 356, with limits $1,105 a month | 49th of 356, with limits $61 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 | 71st cheapest of 343 $748 a month | 5th cheapest of 343 $83 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 | 266th of 327, with limits $14,966 a month | 31st of 327, with limits $1,658 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 | 78th of 351, with limits $746 a month | 2nd cheapest of 351 $100 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 requirement | Not ranked: misses a requirement | Not 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 requirement | Not ranked: misses a requirement | Not ranked: misses a requirement |
Key features
| Feature | Islo | Instabox | boat |
|---|---|---|---|
| Isolation | A microVM with its own kernel for each sandbox | A Firecracker microVM with its own kernel and root | A full VM with its own kernel, on a physical host dedicated to boat (AMD Ryzen 7 9700X or Ryzen 9 9950X; vCPUs are shared) |
| Machine sizes | You choose CPU cores, memory and disk per sandbox | 4 vCPU / 8 GiB on Free; up to 8 / 16 on Pro, 16 / 32 on Builder, 32 / 64 on Team; disk up to 1 TiB | 2 to 8 vCPU on the $20 plan; up to 16 vCPU / 32 GB on $100 and above |
| Docker | Docker inside, with sudo | Docker and Docker Compose inside, with root | Docker and Compose inside, with root and systemd |
| Nested virtualization | Not documented | /dev/kvm not documented; an android template runs Android natively, with no emulator | Yes, /dev/kvm for Android emulators and VMs on every sandbox |
| Desktop and computer use | No built-in desktop; a browser-use capability; you can install Xvfb and VNC with a setup script | VNC desktop with a browser on most templates, screenshot and click API, shareable view or control links; you bring the model | 60fps Linux desktop with Chromium, computer tools for every built-in agent and an embeddable stream |
| Pause and resume | Pause keeps files, processes and memory; can pause after idle time and wake on the next exec, file access or webhook | Pause keeps memory and running programs; the docs say resume usually takes about a second; pauses after 30 idle minutes by default, and a port visit wakes it | Stop keeps the disk for at least 14 days with no compute charge; a resume is like a reboot |
| Fork and snapshots | Snapshot a running sandbox's files, then start new sandboxes from it | Fork a running or stopped machine, disk only, up to 5 copies per call; snapshots saved by hand while it runs, 5 on Free and unlimited on paid plans, at no charge | Fork a running sandbox from its last 1-minute snapshot; the disk is saved every minute and at each stop with no action |
| Port URLs | HTTPS share links anyone with the URL can open, expiring after 24 hours by default | HTTPS on up to 16 ports, public by default, token-protected with --private | HTTPS on up to 50 ports, token-protected by default; raw ports over public IPv6; no dedicated IPv4 |
| SSH | SSH and port-forward through the CLI | SSH through a gateway with short-lived certificates, paste-anywhere SSH tokens and mosh | SSH into every sandbox |
| Outbound internet rules | Gateway allows or denies by host, path and HTTP method, with default deny, rate limits and a log of every request | Not documented | Open internet; no provider-side allowlist |
| Keeping API keys out of the sandbox | Gateway injects stored credentials into outbound requests for any host; keys never reach the sandbox | Secrets proxy swaps a placeholder for the real key in outbound HTTPS headers to allowed hosts | Optional paid AI credentials proxy ($1 a day while on, plus $1 per 1,000 requests); other secrets still enter the sandbox |
| Coding agents | Claude Code, Cursor CLI and Codex preinstalled; factory lines run agent steps on a schedule, webhook or GitHub, Slack, Linear and Jira events | CLI, skills and MCP for Claude Code, Codex, Cursor, OpenCode and Antigravity; you run the agent yourself | Seven agents preinstalled, with a prompt, steer and events API |
| Machines at once | No limit on the pricing page; launch coverage reported 5 on Free and 50 on Team; paused ones do not count | 1 on Free; 100 running on Pro, 200 on Builder, 500 on Team | 100 to 2,000 running sandboxes by plan, plus start limits per minute, hour and day |
| Regions | Islo's cloud (regions not published, set per account), or your own cloud account with BYOC | Not published; you cannot choose where a machine runs | Germany, Finland and France; you cannot pick one; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Islo | Instabox | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | No documented way | Not published | Yes |
| Root | Yes | Yes | Yes |
| Systemd | Not published | Yes | Yes |
| Desktop GUI | With your own setup | Yes | Yes |
| Browser | Yes | Yes | Yes |
| Computer-use API | No documented way | Yes | Yes |
| SSH | Yes | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Yes | Yes |
| Memory fork | No documented way | No documented way | No documented way |
| Custom image (Docker or snapshot) | Yes | Yes | Yes |
| ≥24 h sessions | Yes | Yes | Yes |
| Idle auto-stop | Yes | Yes | No documented way |
| Wake on request | Yes | Yes | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | No documented way | Yes | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Not published | No documented way |
| Secret proxy | Yes | Yes | Yes |
| Secret proxy for any API | Yes | Yes | Yes |
| Preinstalled agents | Yes | Yes | Yes |
| Agent harness API | Yes | Not published | Yes |
| MCP server | No documented way | Yes | No documented way |
| GPU | No documented way | Not published | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | No documented way | Not published | No documented way |
| Self-hosting | No documented way | Not published | No documented way |
| BYOC | Yes | Yes | No documented way |
| Open source | No documented way | No documented way | No documented way |
| Scoped API keys | Not published | Yes | Yes |
| Spend limits | Yes | Yes | Yes |
| Usage per sandbox (API) | Yes | Yes | Yes |
| Audit logs | Yes | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Not published | Not published | No documented way |
| HIPAA | Not published | Yes | No documented way |
| EU data residency | No documented way | Not published | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
Islo and Instabox are not in the public benchmarks we use, so we cannot say which is faster. Instabox says a new machine's shell is ready in under a second; we have not measured it. 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.
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. Islo and Instabox 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.
| Scenario | Islo, a month | Instabox, a month | boat, 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 | $101 · Free | $0 · Free | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $420 · Free | $25 · Pro | $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 | $4,863 · Team | $269 · Pro | $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 | $1,382 · Team · with limits | $500 · Team | $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 | $3,053 · Team · with limits | $500 · Team · with limits | $8,800 · $2000/mo · with limits |
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, and you can set a cost limit per task. Egress has no published price, so Islo totals here leave it out.
Instabox: Free costs $0 for one 4 vCPU / 8 GiB machine. Pro ($20), Builder ($100) and Team ($500) a month each include usage credit equal to the fee. Usage costs $0.004 per vCPU-hour and $0.00225 per GiB-hour, per second while a machine runs. Disk above the included pool costs $0.08 per GiB-month, and egress above the allowance $0.02 per GiB. Snapshots are free.
Instabox: 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. Egress is not billed. A stopped sandbox has no compute charge, and boat keeps its disk for at least 14 days; extra saved snapshots and the optional AI credentials proxy still charge. The $20 plan includes 200 starts a day; extra starts cost $0.03 to $0.07 each.
Limits in those scenarios
Instabox Free allows 1 machine, 3 starts a minute and a pause after 8 hours of running. Pro runs 100 machines at once, Builder 200 and Team 500, so 300 user sandboxes need Team, and 1,000 short jobs at once do not fit. Islo publishes no concurrency limit, and launch coverage reported 50 running on Team, so 300 user sandboxes and 1,000 short jobs at once need a higher limit there. boat allows 100 to 2,000 sandboxes at once by plan. The $2,000 plan includes 90 starts a minute, charges $0.03 to $0.07 per extra start, and refuses starts above 270 a minute, so the 1,000-job burst does not fit boat either.
| Scenario | Islo | Instabox | boat |
|---|---|---|---|
| One coding agent, workdays |
| None for this scenario | None for this scenario |
| One agent that never stops |
| None for this scenario | None for this scenario |
| 50 agents in parallel |
| None for this scenario | None for this scenario |
| Sandboxes for your users |
| None for this scenario | None for this scenario |
| 1,000 short jobs at once |
|
|
|
Which one should you use?
Use Islo when
you need per-host egress rules with a log of every call, coding agents that run from schedules, webhooks and team-tool events, or sandboxes inside 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.
- Coding agents that run on their own. For background agent work: Islo preinstalls Claude Code, Cursor CLI and Codex and starts runs from schedules, webhooks or GitHub, Slack, Linear and Jira events.
- Your own cloud account. For data that must stay in your account: Islo can run its sandboxes inside your own cloud account with BYOC.
Use Instabox when
you want a free machine to start with, a low hourly rate, a VNC desktop on most templates, pause with memory, machines above 16 vCPU, or an SSH gateway with mosh.
- A free plan and a low hourly rate. One 4 vCPU / 8 GiB machine is free, and paid use costs $0.034 an hour at that size, from a $20 plan that is usage credit.
- A desktop agents can click. For computer-use tests: most templates have a VNC desktop with a browser, a screenshot and click API and shareable view links.
- Bigger machines and an SSH gateway with mosh. Machines go up to 32 vCPU / 64 GiB on Team, and its SSH gateway relays mosh and gives paste-anywhere SSH tokens.
Where boat fits
Look at boat if your agents need more than a shell in a microVM: a VM that can start its own VMs, ports that are private by default, the disk saved every minute with no action, and one API to prompt and steer agents. boat's limits: start caps per plan, no pause with memory, a 16 vCPU maximum, and no US or Asia region.
/dev/kvm for emulators and VMs
Neither Islo nor Instabox documents /dev/kvm, so Android emulators, Firecracker or a VM inside the sandbox have no documented path. Instabox's android template runs Android natively instead. boat gives every sandbox /dev/kvm, systemd and root.
Ports private by default
Islo share links open for anyone with the URL and expire after 24 hours by default. Instabox port URLs are public unless you add --private. boat URLs carry a token by default, on up to 50 ports, plus raw ports over IPv6.
Disk saved every minute, agents driven from outside
Islo and Instabox save snapshots when you ask. boat saves the disk every minute while a sandbox runs; if a machine fails, you lose what was written after the last good snapshot. boat also has one API to prompt, steer and stream seven agents.
Use boat when your agents need /dev/kvm, token-gated port URLs by default, a 60fps desktop with computer tools, the disk saved every minute, and one API to drive agents from your app. Compare it one to one: boat vs Islo and boat vs Instabox.
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 Islo cheaper than Instabox?
No. Instabox costs less in every scenario on this page that both fit. A 24/7 dev box comes to $24 a month on Instabox against $402 on Islo, and CI runners to $89 against $1,507. Islo totals leave out egress, which has no published price. boat comes to $26 and $86 for the same two.
Which is faster, Islo or Instabox?
Neither is in the public benchmarks we use, so we make no speed claim. Instabox says a new machine's shell is ready in under a second, and its docs say a paused machine usually resumes in about a second; we have not measured either.
Can Islo and Instabox run Docker?
Yes, both run Docker inside their microVMs, and Instabox also documents Docker Compose. Neither documents /dev/kvm, so emulators and nested VMs have no documented path; Instabox's android template runs Android natively. boat has Docker, systemd and /dev/kvm on every sandbox.
Does Islo or Instabox have a desktop for computer use?
Instabox does: most templates have a VNC desktop with a browser and a screenshot and click API; you bring the model. Islo has no built-in desktop, but has a browser-use capability, and you can install a VNC desktop yourself. boat streams a 60fps desktop with computer tools.
Does Instabox have a free plan?
Yes. Free gives one 4 vCPU / 8 GiB machine with a 20 GiB disk; it pauses after 30 idle minutes, stops after 8 hours of running and allows 3 starts a minute. Paid plans start at $20 a month as usage credit. Sign-up is self-service. boat has no free plan; its 7-day trial needs a card.
Are port URLs private on Islo and Instabox?
Not by default. Islo share links open for anyone with the URL and expire after 24 hours by default. Instabox ports are public by default, and one flag (--private) puts a token on them. boat's port URLs carry a token by default.
Try boat
Install the CLI, then run boat new.
7-day free trial