Replit vs Modal VM Sandboxes
Replit is an app builder: you describe an app, Replit Agent writes it, and Replit hosts it. Modal VM Sandboxes are full Linux VMs that your own code starts by the thousand. Each runs up to 24 hours, and a filesystem snapshot carries its work into a new sandbox.
The companies and products
Replit
Replit is an AI app builder and hosting platform: you describe an app in chat, Replit Agent writes it, and Replit publishes it.
You work in a browser workspace where Replit Agent sets up the project, writes the code, tests it and fixes problems, with system packages managed by Nix. When the app is ready you publish it as an Autoscale, Static, Scheduled or Reserved VM deployment, with Postgres and object storage next to it. It is built for people and teams who want a working app, not for programs that need to create many machines by API. This page compares the parts where the two overlap.
Modal VM Sandboxes
Modal is a serverless cloud for AI work, and VM Sandboxes are the version of its sandboxes that run in a virtual machine with their own Linux kernel.
You create a VM Sandbox from Python, TypeScript or Go code with runtime="vm", run commands in it, and terminate it when the job is done. Modal built the runtime on the Rust-based Cloud Hypervisor, so Docker, FUSE, systemd and nested cgroups work, with the same API, images and prices as its gVisor sandboxes. It became generally available on 1 October 2026. It suits teams that want many agent machines next to Modal's inference and training.
- Funding
- Over $1.2B raised
- Generally available
- 1 October 2026; early customers launched over 20 million VMs before that
- Compliance
- SOC 2 on every plan; HIPAA on Enterprise
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. “204th cheapest of 365” means 203 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 workload | Replit: price rank | Modal VM Sandboxes: price rank | boat: price rank |
|---|---|---|---|
| Software factory 100 at once · 4 vCPU / 8 GB · 2,200 sessions of 8 h a month boat ranks 5th and Modal VM 27th.Modal starts real VMs with Docker from code; to keep files past 24 hours, you snapshot the filesystem or use a Volume. Replit drives one app at a time through Replit Agent. boat saves the disk with no code and has a built-in desktop. | 204th of 365, with limits $2,000 a month | 27th cheapest of 365 $633 a month | 5th cheapest of 365 $634 a month |
| Always-on AI employees 50 machines 24/7 · 2 vCPU / 4 GB An agent that lives on its machine all month needs a snapshot and a new Modal sandbox each day, so Modal is not ranked here as-is. On Replit it means a Reserved VM that bills all month. On boat, turn auto-stop off (default 1 hour) on a paid plan. | 246th of 361, with limits $2,033 a month | Not ranked: misses a requirement | 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 Short code runs suit Modal's per-second billing on max(request, use). Replit's Autoscale is a web host that sleeps when idle, so you set up a code runner yourself. | 225th of 336, with limits $146 a month | Not ranked: misses a requirement | 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 Modal runs up to 5,000 containers at once on Team, and keeps a user's files through a filesystem snapshot. Replit does not publish how many deployments can run at once. boat ranks 3rd and keeps a stopped user sandbox's disk for at least 14 days. | 229th of 349, with limits $825 a month | Not ranked: misses a requirement | 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 Huge bursts of short rollouts suit Modal: no per-start fee and 5,000 containers at once on Team. Replit's docs describe no API to start many machines. boat charges for starts above 90 a minute and refuses them above 270. | 253rd of 349, with limits $4,226 a month | 163rd of 349, with limits $11,982 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 | 266th of 359, with limits $685 a month | Not ranked: misses a requirement | 10th cheapest of 359 $200 a month |
| CI runners 40 at once · 8 vCPU / 16 GB · 6,000 sessions of 12 min a month Modal and boat both run Docker builds in a VM; Replit's Nix-based environments do not document Docker. boat exposes /dev/kvm on every plan; Modal offers nested virtualization on Enterprise only, as an experimental option. | 278th of 374, with limits $425 a month | 170th of 374, with limits $655 a month | 2nd cheapest of 374 $86 a month |
| 24/7 dev boxes 1 machine 24/7 · 4 vCPU / 8 GB A Replit workspace is a good place to code by hand, with SSH on paid plans. A Modal VM runs up to 24 hours, and you carry its files forward with a snapshot. On boat, turn auto-stop off on a paid plan. | 181st of 371, with limits $109 a month | Not ranked: misses a requirement | 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 boat ships a 60 fps desktop with Chrome and computer tools. Replit's VNC pane shows a desktop to a person. On Modal you set it up: its runnable example installs Xvfb, x11vnc, noVNC, Chromium and a Browser Use agent. | 225th of 367, with limits $619 a month | Not ranked: misses a requirement | 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 | 277th of 356, with limits $317 a month | Not ranked: misses a requirement | 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 | 282nd of 343, with limits $217 a month | Not ranked: misses a requirement | 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 | 147th of 327, with limits $4,378 a month | Not ranked: misses a requirement | 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 | 241st of 351, with limits $215 a month | 27th cheapest of 351 $464 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 | Replit | Modal VM Sandboxes | boat |
|---|---|---|---|
| Kind of product | AI app builder with browser workspaces and app hosting | Sandboxes inside a serverless AI cloud, created from Python, TypeScript or Go | Sandboxes you create, stop and fork by API, SDK or CLI |
| Isolation | Not documented for workspaces; the security page says strong logical separation between users | VM with its own Linux kernel on Cloud Hypervisor | Full VM with its own kernel, on boat's own hosts; vCPUs are shared |
| Creating machines from code | MCP server tools to create, update and publish apps; the docs describe no API to start many machines | SDK call with runtime="vm"; 100 containers at once on Starter, 5,000 on Team; no per-start fee | API, SDK and CLI to create, stop, resume and fork sandboxes; the $20 plan includes 12 starts a minute and 200 a day |
| Docker, systemd, root | System packages come from Nix; the docs do not describe Docker or systemd | Yes; you start dockerd yourself | Yes, in every sandbox |
| Nested virtualization | Not documented | Enterprise plan only, as an experimental option | /dev/kvm on every sandbox |
| CPU benchmark (V8 Web Tooling, 4 vCPU / 8 GB, StarSling run of 3 October 2026) | Not in the public benchmarks we use | VM runtime 15.48 runs/s, gVisor 12.60, both rank 7 of 15 (shared); measured with cpu=4 | 28.06 runs/s, rank 2 of 15 (shared), on a Ryzen 9 9950X host |
| Running for days | A Reserved VM runs continuously and bills all month at a fixed price | 24 hours at most (default 5 minutes); continue in a new sandbox from a filesystem snapshot | Auto-stop defaults to 1 hour; set up to 30 days, or turn it off on a paid plan for no cap |
| Files over time | Workspace files and Agent checkpoints; published apps keep data in Postgres or App Storage | No paused state; filesystem snapshots (kept 30 days by default, or with no expiry) or Volumes keep files, set up in your code | Disk saved every minute and at each stop with no code; a stopped disk is kept at least 14 days |
| Memory snapshots | Not documented | Yes, in alpha: snapshotting ends the sandbox and snapshots expire after 7 days | No; a resume is like a reboot |
| Desktop and computer use | VNC pane that streams a desktop to your browser; the docs describe no computer-use API | Not built in; Modal's runnable example installs Xvfb, x11vnc, noVNC, Chromium and a Browser Use agent | 1920x1080, 60 fps desktop with Chrome and computer tools built in |
| Coding agents and API keys | Replit Agent, drivable from an MCP client; managed keys for some AI models | You install the harness in the image; to keep keys out, you run a credential-injecting proxy in a Sidecar (experimental) from an official example | Seven harnesses with a prompt, steer and events API; optional paid AI credentials proxy ($1 a day plus $1 per 1,000 requests) |
| Hosting that sleeps when idle | Autoscale starts on the first request; no compute charge while idle, plus a $2 monthly base fee | No wake on request; encrypted and raw TCP tunnels while the sandbox runs | No wake on request; up to 50 HTTPS URLs, token-protected by default |
| Outbound network rules | The docs describe no egress allowlist | Block all, IP-range allowlist, domain allowlist (beta) | Open internet, no provider-side allowlist |
| Regions | North America, Europe, Asia, South America and Australia for published apps on Core and up | US, EU and Asia-Pacific; pinning a region costs 1.15x to 1.75x | Germany, Finland and France; you cannot pick a region; no US or Asia region |
Every feature Battleships tracks (43)
| Feature | Replit | Modal VM Sandboxes | boat |
|---|---|---|---|
| Full VM (own kernel) | Yes | Yes | Yes |
| Docker inside | Not published | Yes | Yes |
| Nested virtualization | No documented way | Yes | Yes |
| Root | Not published | Yes | Yes |
| Systemd | Not published | Yes | Yes |
| Desktop GUI | Yes | With your own setup | Yes |
| Browser | No documented way | With your own setup | Yes |
| Computer-use API | No documented way | With your own setup | Yes |
| SSH | Yes | With your own setup | Yes |
| Persistent disk | Yes | With your own setup | Yes |
| Pause/resume | No documented way | No documented way | Yes |
| Automatic snapshots | Yes | No documented way | Yes |
| Fork/clone | Yes | Yes | Yes |
| Live fork (no pause) | No documented way | Not published | Yes |
| Memory fork | No documented way | Yes | 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 | No documented way | No documented way |
| HTTPS preview URLs | Yes | Yes | Yes |
| Raw TCP inbound | Not published | Yes | Yes |
| Public IPv4 | No documented way | No documented way | No documented way |
| Egress allowlist | No documented way | Yes | No documented way |
| Secret proxy | Yes | With your own setup | Yes |
| Secret proxy for any API | No documented way | No documented way | Yes |
| Preinstalled agents | Yes | With your own setup | Yes |
| Agent harness API | Yes | No documented way | 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 | Not published | No documented way | No documented way |
| Self-hosting | No documented way | No documented way | No documented way |
| BYOC | No documented way | No documented way | No documented way |
| Open source | No documented way | No documented way | No documented way |
| Scoped API keys | Not published | Not published | Yes |
| Spend limits | Yes | Not published | Yes |
| Usage per sandbox (API) | Yes | Not published | Yes |
| Audit logs | Yes | Yes | No documented way |
| SSO | Yes | Yes | No documented way |
| SOC 2 | Yes | Yes | No documented way |
| HIPAA | No documented way | Yes | No documented way |
| EU data residency | Yes | Yes | No documented way |
| Zero data retention | Not published | Not published | Yes |
Performance
In StarSling's run of 3 October 2026 (run 37073680030), on the V8 Web Tooling Benchmark at 4 vCPU / 8 GB, boat did 28.06 runs per second, Modal's VM runtime 15.48 and Modal gVisor 12.60. That is about 1.8x the VM runtime. StarSling ran Modal with cpu=4 and the sandbox saw 4 CPUs (PR #121); sized that way, Modal bills 4 cores, $0.76 an hour. That boat sandbox 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. Providers ran on different hardware in different regions. Replit is not in that benchmark, so there is no comparable number for it.
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. Modal VM Sandboxes measured on: VM Sandbox, request = size. 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. Replit 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.
| Scenario | Replit, a month | Modal VM Sandboxes, 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 | $122 · Pro $100 (annual) · with limits | $0 · Starter | $20 · $20/mo |
| One agent that never stops 4 vCPU / 8 GB, 50 GB disk, running 24/7 all month | $122 · Pro $100 (annual) · with limits | $109 · Starter · with limits | $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 | $6,092 · Pro $2,500 (annual) · with limits | $1,480 · Starter | $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 | $403 · Pro $250 (annual) · with limits | $579 · 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 | $825 · Pro $1,000 (annual) · with limits | $1,911 · Team · with limits | $8,800 · $2000/mo · with limits |
Replit: Replit plans (Core $20, or $18 billed annually; Pro from $100) turn into monthly credits that pay for Agent work and hosting, then usage goes to pay-as-you-go. A Reserved VM has a fixed monthly price per size, such as $130 for 4 vCPU / 16 GB, and bills busy or idle. Autoscale charges a $2 monthly base fee plus usage while it serves requests.
Modal VM Sandboxes: Modal prices CPU per physical core, and one core equals two vCPUs. A 4 vCPU / 8 GiB sandbox is 2 cores + 8 GiB: $0.476 an hour when the request equals the size. Modal bills per second for the larger of what you request and what you use, until the sandbox ends. Starter is $0 with $30 of monthly credit, Team is $250 a month with $100 of credit, and pinning a region multiplies the price by 1.15x to 1.75x. Our scenario bills use a minimal request that bursts, which is not guaranteed.
Modal VM Sandboxes: Plans cost $20, $100, $500 or $2,000 a month, and the whole plan price comes back as VM time for that month. A 4 vCPU / 8 GB sandbox costs $0.036 an hour, billed per second while it runs, busy or idle. A stopped sandbox has no compute charge and keeps its disk for at least 14 days; saved snapshots above the included count and the AI credentials proxy still charge. Extra starts cost $0.03 to $0.07 each.
Limits in those scenarios
Replit does not fully fit any scenario because it is an app platform: each always-on machine is a published Reserved VM app, and it does not publish how many can run at once. A Modal VM Sandbox runs at most 24 hours; files carry over through a filesystem snapshot or a Volume that your code sets up. The 24/7 scenario has no break, so Modal needs a snapshot and a new sandbox each day and is marked as not fitting as-is. Modal's 1,000-job burst relies on shared CPU above a small request. boat does not fit 1,000 short jobs at once: its $2,000 plan includes 90 starts a minute, refuses starts above 270 a minute, and never queues a start.
| Scenario | Replit | Modal VM Sandboxes | boat |
|---|---|---|---|
| One coding agent, workdays |
| None for this scenario | None for this scenario |
| One agent that never stops |
|
| 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 Replit when
you want Replit Agent to build a web app from a description and host it for you, with databases, sleeping when idle and regions outside Europe.
- An app built and hosted for you. Useful if you want a working app from a description: Replit Agent builds, tests and publishes it with Postgres and storage.
- Hosting that sleeps when idle. Useful for web apps with uneven traffic: Autoscale wakes on the first request and has no compute charge while idle, plus a $2 monthly base fee.
- Regions on five continents. Useful if your users are spread out: published apps can run in North America, Europe, Asia, South America or Australia.
Use Modal VM Sandboxes when
your code runs huge bursts of short jobs that finish within a day, needs memory snapshots, strict outbound rules or a large disk, or sits next to models you already run on Modal.
- Real VMs started from code. Useful for agent platforms: your code starts a VM with its own kernel, Docker and root, with a 512 GiB root filesystem.
- Very large bursts. Useful for huge bursts of short jobs: Modal runs 5,000 containers at once on Team, with no per-start fee.
- Outbound rules and models on one bill. Useful if you need strict egress or already serve models on Modal: block or allowlist traffic, next to inference and training.
Where boat fits
If what you are really running is agents that work for hours or days, look at boat. Replit is built around one person building one app. Modal's VMs run up to 24 hours each, and your code carries work forward with snapshots. boat gives each agent a full VM that saves its disk with no code, with Docker, a desktop and coding agents installed.
A machine that keeps its work with no code
On Modal your code snapshots the filesystem before the 24-hour end, or keeps files in a Volume. Replit's published apps keep data in Postgres or App Storage. boat saves the disk every minute and at each stop, and has no session cap once auto-stop is off.
Docker, KVM and a desktop on every sandbox
Replit's docs do not describe Docker, systemd or /dev/kvm. Modal runs Docker; nested virtualization is Enterprise only, and you install the desktop from its example. In StarSling's run of 3 October 2026, boat did 28.06 runs/s against 15.48 for Modal's VM runtime and 12.60 for gVisor.
Agents driven from outside
Replit's MCP server drives only Replit Agent. On Modal you install the harness yourself. boat lets you prompt, steer and watch Claude Code or Codex. boat has limits too: start caps per plan, no GPU, and EU hosts only.
Use boat when your agents work for hours or days in a machine they come back to, with Docker, /dev/kvm, a desktop and coding agents you drive by API, on a VM that saves its disk with no code. Compare it one to one: boat vs Replit and boat vs Modal VM Sandboxes.
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 Replit cheaper than Modal VM Sandboxes?
It depends on the job. For one coding agent on workdays, Modal costs $0 inside Starter's $30 monthly credit, and Replit $122. For 50 agents in parallel, Modal comes to $1,480 and Replit to $6,092. For sandboxes for your users, Replit comes to $403 and Modal to $579, but only Modal fits that scenario. On boat these come to $20, $317 and $200.
Which is faster, Replit or Modal VM Sandboxes?
Replit is not in the public benchmarks we use, so we cannot say. In StarSling's run of 3 October 2026, Modal's VM runtime did 15.48 runs per second at 4 vCPU / 8 GB, Modal gVisor 12.60, and boat 28.06 on a Ryzen 9 9950X host.
Can Replit run Docker?
Replit sets up environments with Nix packages, and its docs do not describe running Docker, systemd or virtual machines inside. Modal VM Sandboxes run Docker if you start dockerd, and every boat sandbox has Docker, systemd and /dev/kvm.
How long can a Modal VM Sandbox run?
The default timeout is 5 minutes and the maximum is 24 hours. For longer work, Modal recommends a filesystem snapshot and a new sandbox started from it. A Replit Reserved VM runs continuously. On boat, auto-stop defaults to 1 hour, and on a paid plan you can turn it off for no cap.
Can I start many machines from code on Replit?
Not really. Replit's MCP server lets a client create, update and publish apps through Replit Agent, but its docs describe no API to start many machines. Modal and boat are both built for that; boat counts each create, fork and resume against the plan's start caps.
Try boat
Install the CLI, then run boat new.
7-day free trial