Developer tools decision
CodeSandbox
A basic sandbox service (API + single-host or small-cluster containers, web editor, snapshots) is feasible to build and run by a technical user, but reproducing CodeSandbox's microVM performance and large-scale infrastructure is impractical without significant engineering and ops investment.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
Code CodeSandbox publishes itself
Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Programmatically create an isolated dev sandbox, run code, snapshot/restore state, and destroy the sandbox when finished.
What it still won’t have
- Highly optimized microVM snapshot/restore latency and fast fork/clone behavior
- Operational ability to handle millions of concurrent VMs at scale
- Enterprise polish, integrations, and brand trust
What remains hard
- Infrastructure at scale
We can handle millions of concurrent VMs and make it easy to provision, manage and decommission VMs.
- Infrastructure at scale
Our microVM infrastructure allows us to spin up entire VMs, clone them and restore snapshots within 2 seconds.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 22 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted sandbox service using Node.js + Express for the API, PostgreSQL for metadata, Docker (or Firecracker if available) for isolated runtimes, and a web UI using React + Monaco editor. Implement: 1) REST API to create/list/start/stop/destroy sandboxes with token-based auth; 2) worker that spawns a container/microVM per sandbox, exposes a web-socket terminal and filesystem mount; 3) snapshot and restore using container checkpointing or filesystem tarball snapshots; 4) background hibernation job that stops idle sandboxes and cleans resources; 5) basic persistence of project files in Postgres or object storage. Out of scope: multi-region autoscaling, supporting millions of concurrent VMs, proprietary microVM optimizations, and commercial integrations. Include error handling, logging, health checks, and unit tests for API and worker logic.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score61
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productCodeSandbox homepage
- open sourcegitpod-io/gitpod
- open sourceeclipse-che/che
Integrity checks
What held up, and what did not.
