exec-sandbox review
A free, self-hosted QEMU sandbox with strong isolation and developer APIs.
Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026
exec-sandbox is an open-source Python asyncio library and command-line tool for running untrusted code inside a hardware-isolated QEMU microVM for each session. It targets developers building AI agents or other systems that need isolated execution. The project runs on users’ Linux or macOS hosts without a cloud account or API key, and supports Python, JavaScript/TypeScript, and shell runtimes. Its self-hosted deployment model suits solo developers and small to mid-market teams that want control over the execution environment.
There is no paid tier: exec-sandbox is free and open source. The API and CLI expose session state, stdout and stderr streaming, file read/write, and versioned package installation with caching. Saved VM instances can be encrypted and stored locally or in S3-compatible storage. Network access is disabled by default, with configurable domain allowlists for controlled outbound connections. KVM, HVF, or TCG acceleration options let the runtime use available host capabilities, while the Python API supports asynchronous integration into agent workflows.
The trade-off is operational ownership. Because deployment is self-hosted, teams must run the Linux or macOS environment and manage the underlying execution setup rather than use a hosted sandbox service. Community support and documentation are the listed support channels, which may not fit organizations seeking vendor-managed assistance. Outbound access also requires deliberate allowlist configuration, and the repository documents execution timeouts up to 300 seconds. Choose exec-sandbox when programmable QEMU isolation, persistence, and local control matter; choose a hosted alternative when managed deployment or broader support coverage is a priority.
exec-sandbox pros and cons
- Where it wins
- Hardware-isolated QEMU microVM per session
- Python asyncio API and sbx CLI with multi-language runtimes
- Encrypted persistence, package caching, and network allowlists
- Where it doesn't
- Deployment is self-hosted on Linux or macOS hosts
- Outbound networking starts disabled and requires domain allowlists
- Support is provided through community channels and documentation
exec-sandbox fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update