daytonaio/daytona
Went closed source in June 2026; the public repository is now explicitly unmaintained. Also the reason this site treats 'open source' as a claim to verify. → full assessment
This is the chapter that saves the most time, and the one nobody writes. These repositories are not necessarily bad — most contain at least one good idea — but the expected hassle and risk look larger than the likely benefit, and there are better uses for your evening.
A few hundred stars, a promising README, and no commits for four to eight months. It is not archived, which is worse: the blocklists and default profiles are rotting in place and there is no signal that maintenance stopped. Look at the last-commit date before the star count, every time.
Impressive architecture, a Hacker News thread, and development that stopped days after the launch. One thorough first-wave project — with egress inspection, branch isolation and blocked merges — went quiet two days after its announcement thread. The engineering was real; the commitment was not.
Twelve commits on one day, no releases, one author, five to fifteen stars, and a README describing a complete security model. These are sketches, not software. Some contain a genuinely good idea — time-travel debugging for agent microVMs is a real invention — and the idea is the part worth keeping.
A GPL-3.0 desktop application that would be useful to study, except that copying any of it would relicense your product. Combine that with a stalled project and there is nothing left to take but the screenshots.
The project that built its reputation on being open source and then closed the production code while leaving the public repository unmaintained. For a sandbox, the source is the trust boundary, so this is not a licensing inconvenience — it removes the mechanism by which you could check the claim.
Tools that give an agent more access, presented in lists alongside tools that contain it. An MCP server that controls your Windows desktop, a runner that executes on your host, an "agent framework" with no boundary at all. Useful, sometimes excellent, and not what you are looking for when you search for a sandbox.
Each entry names the reason. Several are worth reading for their ideas — that is why some of them appear in the watch list analysis rather than being dismissed outright.
Went closed source in June 2026; the public repository is now explicitly unmaintained. Also the reason this site treats 'open source' as a claim to verify. → full assessment
The browser IDE. Interesting history in WebContainers; the agent story moved to the SDK.
Not a sandbox. Included only because it showed up in a sandbox list; left here as a reminder to check your sources.
Node.js in a browser tab. Nobody has committed to the public repository since April 2025.
Cedar-policy container wrapper from StrongDM. Ships a DISCLAIMER.txt disclaiming support, and the repo has been quiet since April 2026.
BPF program runner for container awareness. Archived since May 2021.
E2B-based local sandbox with a VNC desktop, Electron shell, GPL-3.0, stalled since April 2026, and a README that injects an unrelated project recommendation. → full assessment
Fast Apple-Silicon Seatbelt wrapper. Commits stopped in February 2026.
Docker sandbox with automatic worktrees. Quiet since March 2026 and never took off.
DML-style runtime authorization SDK. Fifty-six stars.
MCP server that hands out ephemeral shells. Last push March 2026.
Lightweight ephemeral Linux sandboxes. Last push October 2025.
Tart-backed ephemeral macOS VM per agent. AGPL, quiet since December 2025.
Resource Sets as committed team policy. Forty-three stars and no traction since March.
Multi-backend (Docker/Firecracker/WASM) execution engine. Thirteen stars.
Ephemeral worktrees with copy-on-write and network gating. Twelve stars and two days of development.
Per-project Arch VMs with nftables egress zones. 8 stars, one author, no credential story.
Merkle-logged audit receipts for hook events. Seven stars, clever, unproven.
Unix permissions as a boundary. Six stars; the idea is old and the repo is thin.
Five stars, one author, stale since February 2026.
Policy-based authorization with post-run verification. Five stars.
Per-task Firecracker VMs. Four stars and one day of commits.
Agent microVMs with a Git-first workflow. The repository no longer resolves at its original URL — which is itself the cautionary point about building on a wrapper with one author and no release history.
These are useful pieces of software that do not contain the agent. Including them here is not a criticism; it is a warning about how they get misremembered after you have read three comparison tables in a row.
Gives an agent the whole Windows desktop. The inverse of a sandbox, and it should be labelled that way. → full assessment
"The agent can control my desktop" and "the agent is contained on my desktop" are opposite claims, and they appear within a page of each other in several published lists. If a tool needs full UI control to work, it cannot be sandboxed by the same tool that gives it that control — the containment has to come from somewhere else, which in practice means a VM.
You almost certainly want one of these instead: a rootless Podman container with a hardened flag set and a narrow mount; your agent's own built-in sandbox left on; or a VM managed by Lima, Incus, UTM or Multipass. Every item on this page is a wrapper around one of those, and the wrapper is the part that stops being maintained.
The security people are looking for in abandoned wrappers is usually available from three changes that have nothing to do with which project you install: move credentials out of the agent's environment, put the egress policy in the kernel, and make the agent's workspace a copy rather than your original. That is a weekend of work with no dependency risk at all.
Most of these repositories were written by one person who saw a real problem and shipped something for it in a weekend. Several of them are better thought through than projects with fifty times the stars. The judgement here is not about the quality of the work — it is about whether a stranger should build a production dependency on something that has not yet been maintained for long enough to be predictable. If one of these starts shipping releases again, revisit it.