Drop sandboxes untrusted programs and agent-generated code in rootless, disposable Linux home dirs via user namespaces and optional gVisor, no root needed.
Yes, Drop is open source under the Apache-2.0 license.
Drop is free to use.
Yes, Drop can be self-hosted (the source is available under the Apache-2.0 license).
Apache-2.0 rootless Linux sandbox that runs untrusted programs and agent-generated code in disposable, isolated home directories using user namespaces, with optional gVisor for a stronger boundary. Access is governed by a TOML file and nothing needs root or a container runtime, so you can execute a coding agent's output or a third-party dependency without giving it your real user account.
Once agents start writing and running code, "just run it" becomes a security decision. The usual isolation answers — Docker, microVMs — are heavier than a lot of teams want for the simple job of running one agent's output safely. Drop is the lightweight middle: rootless user-namespace isolation, a throwaway home directory per run, and a TOML file that says what the sandboxed process may touch, with gVisor available when you want a firmer wall. For anyone piping coding-agent output or untrusted dependencies through their own machine, it is a low-ceremony way to contain the blast radius, and it is Apache-2.0. The honest read: it is Linux-only, local, and modestly sized — treat it as a sane isolation habit for dev workflows, not a hardened multi-tenant runtime, and turn on gVisor if the boundary needs to hold.