smol machines vs Islo
Both give each agent a microVM with its own kernel, and both keep API keys out of the guest. smol machines is an open-source engine you can run anywhere, with live branches that keep memory. Islo wraps its sandboxes in a gateway that sets outbound rules by host, path and method and logs every call.
The companies and products
smol machines
smol machines makes isolated Linux microVMs that run the same way on your laptop, in their hosted cloud, or on your own servers.
The core is smolvm, an open-source microVM engine built on libkrun. Each machine has its own guest kernel. smol cloud is the paid hosted service. It runs machines behind a REST API, Node, Python and Rust SDKs, and a managed agents API. It is for developers who want one VM model from local development to production, with live branching of running machines.
- Uptime SLA
- 99.95% on Pro, Startup and Enterprise
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. “41st cheapest of 361” means 40 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 | smol machines: price rank | Islo: price rank | boat: 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. smol cloud exposes nested virtualization on its Startup and Enterprise plans; Islo documents no /dev/kvm. boat exposes /dev/kvm on every plan and has a built-in desktop. | 105th of 365, with limits $604 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 Islo can pause an idle assistant with its memory and wake it on the next request. smol machines keeps the files across a stop and starts the machine on the next command. boat keeps a sandbox running with auto-stop off (default 1 hour), billed at full rate while it runs. | 41st cheapest of 361 $1,038 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 smol machines fits short code runs well, with a one-minute minimum and branches of a warm machine that pay the minimum once. Islo publishes no concurrency limit; launch coverage reported 50 running on Team. | 16th cheapest of 336 $140 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 fits smol machines on Startup. Islo publishes no concurrency limit, and launch coverage reported 50 on Team, so ask Islo first. | 12th cheapest of 349 $531 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 smol machines can branch a running machine with its memory and processes, so many rollouts start from one prepared state. Islo starts new sandboxes from a snapshot of files. A boat fork boots fresh from the last 1-minute disk snapshot. | 119th of 349, with limits $6,978 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 Harbor integration, its Harbor docs show 300 trials at once, and gateway rules can stop trials from looking up answers. smol machines ships registry images with the Harbor eval harness. | 49th cheapest of 359 $670 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 All three run Docker for CI jobs. For jobs that build Android apps or boot VMs, boat has /dev/kvm on every plan and smol cloud on Startup and Enterprise; Islo does not document it. | 69th cheapest of 374 $514 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 | 230th of 371, with limits $29 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 or computer-use API. You set it up: on Islo a setup script installs Xvfb and a VNC server, and on smol you build it into your own image. boat streams a 60fps desktop with Chrome and computer tools. | 135th of 367, with limits $156 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 | 58th of 356, with limits $136 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 | 97th cheapest of 343 $242 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 | 145th of 327, with limits $4,344 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 | 59th of 351, with limits $377 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 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 | smol machines | Islo | boat |
|---|---|---|---|
| Isolation | libkrun microVM with its own guest kernel | A microVM with its own kernel for each sandbox | Full VM with its own kernel, on AMD Ryzen 7 9700X and Ryzen 9 9950X hosts dedicated to boat; vCPUs are shared |
| Docker and nested virtualization | Docker inside the VM; nested virtualization on Startup ($150 a month plus usage) and Enterprise | Docker inside and sudo; no /dev/kvm or nested virtualization documented | Docker, root, systemd and /dev/kvm on every plan |
| Desktop and computer use | You set it up: run Chromium from an OCI image (official guide); no hosted desktop or computer-use route | Browser-use capability built in; no desktop or computer-use API. You set it up: install Xvfb and a VNC server with a setup script | Linux desktop and Chrome streamed at 1920x1080, 60fps, with computer-use tools |
| Stop and resume | Files in /workspace survive a stop; stopped disk bills at $0.0001/GB-hour; the next command starts a stopped machine; checkpoints save RAM | Pause keeps files, processes and memory; can pause after idle time and resume on the next exec, file access or webhook | Disk saved every minute and at stop; memory and processes are not saved. A stopped sandbox has no compute charge and its disk is kept at least 14 days |
| Fork | Branch a running machine with its memory and processes; checkpoints capture RAM to durable storage | Snapshot a running sandbox's files, then start new sandboxes from it | Fork a running sandbox from its last 1-minute disk snapshot; the fork boots fresh |
| Shell access | Command API, sessions and a WebSocket terminal capped at one hour per connection; no SSH route documented | SSH and port-forward through the CLI | SSH, plus a command API and terminal |
| Inbound access | Up to 16 published ports via token URLs or an authenticated connect route, plus a TCP tunnel route; no dedicated IP | HTTPS share links that anyone with the URL can open, expiring after a TTL (24 hours by default); port-forward through the CLI | Up to 50 HTTPS URLs, token-gated by default; a public IPv6 address per sandbox; the IP changes at each resume |
| Outbound rules | Blocked, open, or an allowlist of hosts and CIDR ranges | Gateway profiles allow or deny by host, path and HTTP method, with default deny, rate limits, content filters and a log of every request | Open internet, no provider-side allowlist |
| Keeping API keys out of the sandbox | Stored credentials: the guest sees a placeholder, swapped for the real value on HTTPS to allowed hosts | Gateway injects stored credentials into outbound requests for any host; they never reach the sandbox | Optional AI credentials proxy, $1 per UTC day plus $1 per 1,000 requests; covers supported AI providers only |
| Coding agents | Managed agents API: Claude Code, Codex, OpenCode or any command, with turns, cancel, event stream, rewind and branch | Claude Code, Cursor CLI and Codex preinstalled; factory lines run agent steps with events, steer and follow-ups, on a schedule, webhook or GitHub, Slack, Linear and Jira events | Seven harnesses installed, including Claude Code and Codex, with a prompt, steer and events API |
| Sandboxes at once | 20 on Standard, 100 on Pro, 1,000 on Startup; a stopped machine holds a slot | No limit on the pricing page; launch coverage (May 2026) reported 5 on Free and 50 on Team; paused ones do not count | 100 on the $20 plan up to 2,000 on the $2,000 plan; starts per minute, hour and day are capped by plan |
| Open source and self-hosting | Open-source smolvm runs on your laptop or your own servers with the same .smolmachine artifact | Not open source; BYOC runs Islo in your own cloud account | Hosted service only |
| Where it runs | No region choice in the cloud API | Islo's cloud (regions not published, set per account), or your own cloud account with BYOC | Germany, Finland and France; you cannot pick a region; snapshot copies can be stored outside the EU |
| Billing | $0.04 base per running hour plus active CPU and memory, one-minute minimum; plan fees on top of usage | $0.07 per CPU-hour, $0.04 per GB-hour of memory and $0.0007 per GB-hour of disk while running; no plan fee; egress price not published | $0.036 an hour at 4 vCPU / 8 GB while running, busy or idle; plans from $20 a month come back as VM time for that month |
Every feature Battleships tracks (43)
| Feature | smol machines | Islo | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Yes | Yes | Yes |
| Nested virtualization | Yes | No documented way | Yes |
| Root | Not published | Yes | Yes |
| Systemd | Not published | Not published | Yes |
| Desktop GUI | No documented way | With your own setup | Yes |
| Browser | With your own setup | Yes | Yes |
| Computer-use API | No documented way | No documented way | Yes |
| SSH | No documented way | Yes | Yes |
| Persistent disk | Yes | Yes | Yes |
| Pause/resume | Yes | Yes | Yes |
| Automatic snapshots | No documented way | Yes | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | Yes | Yes | Yes |
| Memory fork | Yes | 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 | Not published | No documented way | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | Yes | Yes | 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 | Yes | Yes |
| MCP server | Yes | No documented way | No documented way |
| GPU | No documented way | No documented way | No documented way |
| Windows | No documented way | No documented way | No documented way |
| Arm64 | Yes | No documented way | No documented way |
| Self-hosting | Yes | No documented way | No documented way |
| BYOC | Yes | Yes | No documented way |
| Open source | Yes | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | Yes | Yes | Yes |
| Usage per sandbox (API) | Yes | Yes | Yes |
| Audit logs | Not published | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | No documented way | Not published | No documented way |
| HIPAA | No documented way | Not published | No documented way |
| EU data residency | No documented way | No documented way | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
smol machines 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 also places sandboxes on Ryzen 7 9700X hosts, which this run did not measure. smol machines publishes a boot time under 200 ms for smolvm. That is a start time, not CPU speed.
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. smol machines 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.
| Scenario | smol machines, a month | Islo, 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 | $25 · Standard | $101 · Free | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $93 · Standard | $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,139 · Pro | $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 | $465 · Startup | $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,389 · Startup | $3,053 · Team · with limits | $8,800 · $2000/mo · with limits |
smol machines: smol cloud charges $0.04 for every hour a machine runs, plus $0.05 per active vCPU-hour and $0.0162 per active GB-hour of memory, with a one-minute minimum. Disk bills at $0.0001 per GB-hour, also while stopped, and egress at $0.05 per GB. Standard is $0. Pro ($20 a month) and Startup ($150 a month) are fees on top of usage, not credit.
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 for what you give a sandbox while it 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 is set when the sandbox is created. Egress prices are not published.
Limits in those scenarios
smol machines caps machines by plan: 20 on Standard, 100 on Pro and 1,000 on Startup, and a stopped machine still holds a slot. So 50 agents need Pro, and 1,000 short jobs at once need Startup. Islo's pricing page names no concurrency limit. Launch coverage in May 2026 reported 50 running sandboxes on Team, so the table treats 300 user sandboxes and 1,000 jobs at once as needing a higher limit from Islo. Islo publishes no egress price, so its totals leave egress out. boat runs 100 sandboxes at once on the $20 plan and 2,000 on the $2,000 plan. The $2,000 plan includes 90 starts a minute; extra starts cost $0.03 to $0.07, and starts above 270 a minute fail with 429. boat never queues a start, so the 1,000-job burst does not fit boat as listed.
| Scenario | smol machines | Islo | 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 | None for this scenario |
|
|
Which one should you use?
Use smol machines when
you want one open-source VM engine from your laptop to your own servers, branch running machines with their memory, or start very large bursts of short jobs.
- Open source, from laptop to your own servers. Teams that want one VM engine locally, in a hosted cloud and on their own servers can use open-source smolvm.
- Live branches with memory. Useful for RL and test fan-out: branch a running machine with its memory and processes, paying the one-minute minimum once.
- Large bursts on one plan. Teams that start 1,000 short jobs at once can run them all on the Startup plan, which holds 1,000 machines.
Use Islo when
you need per-host egress rules with a log of every outbound call, credentials injected at a gateway, sandboxes that pause with memory, 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.
- Your own cloud account. Useful if your data must stay in your own cloud account: Islo can run under BYOC.
Where boat fits
Look at boat if your agents need a whole machine on every plan: a built-in desktop, /dev/kvm, SSH and up to 50 token-gated HTTPS URLs. boat costs less in the three agent scenarios on this page. It has no outbound allowlist, it does not keep memory across a stop, and it caps starts per plan.
A desktop and /dev/kvm on every plan
boat ships a 60fps desktop, Chrome and /dev/kvm on every sandbox. On Islo and smol cloud you build the desktop into the image yourself. smol cloud has nested virtualization on Startup and Enterprise; Islo does not document it.
Ports and SSH
boat serves up to 50 token-gated HTTPS URLs and SSH on every sandbox. smol cloud documents no SSH route and publishes up to 16 ports. Islo share links open to anyone with the URL and expire after 24 hours by default.
A flat price for steady work
One agent running all month is $26 on boat, $93 on smol machines and $420 on Islo in this page's estimate. boat bills a running sandbox at full rate, busy or idle, so a mostly idle machine can cost less on smol, which bills active CPU and memory.
Use boat when your agents need a whole machine on every plan: Docker, /dev/kvm, SSH, a desktop and a browser and up to 50 HTTPS URLs, at a flat per-second price for steady work. Compare it one to one: boat vs smol machines 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 smol machines cheaper than Islo?
In every scenario we priced, yes. One coding agent on workdays comes to $25 a month on smol machines and $101 on Islo, one agent running all month to $93 against $420, and 50 agents in parallel to $1,139 against $4,863. boat comes to $20, $26 and $317 for the same three.
Which is faster, smol machines or Islo?
Neither is in the public benchmarks we use, so we cannot say. smol machines publishes a boot time under 200 ms, which is a start time, not CPU speed.
Can smol machines and Islo run Docker and Android emulators?
Both run Docker inside their microVMs. smol cloud exposes nested virtualization on its Startup and Enterprise plans. Islo documents no /dev/kvm. boat has Docker, systemd and /dev/kvm on every plan.
Do they keep API keys out of the sandbox?
Both do. Islo's gateway injects stored credentials into outbound requests. smol cloud's stored credentials give the guest a placeholder and swap in the real value on HTTPS to allowed hosts; plain environment secrets stay readable. boat's optional proxy ($1 per UTC day plus $1 per 1,000 requests) covers supported AI providers only.
Can either fork a running sandbox?
Both can. smol machines branches a running machine into children that keep its memory and running processes. Islo snapshots a running sandbox's files and starts new sandboxes from that. boat forks a running sandbox from its last 1-minute disk snapshot, and the fork boots fresh.
Where do they run?
smol cloud has no region choice in its API, and open-source smolvm runs on your own laptop or servers. Islo does not publish its regions and can run in 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