- Home
- Sandbox Software
- microsandbox
microsandbox
What it is
microsandbox is a local-first microVM runtime for running untrusted workloads such as AI agents, user code, plugins, CI jobs, scrapers, and automation. Each sandbox has its own Linux kernel, filesystem, and network boundary rather than sharing the host kernel like a container. The local runtime starts on the user's machine without a daemon, root service, or account. It can also run on a user's servers or clusters, and the cloud platform can be deployed within a user's infrastructure. SDKs are available for TypeScript, Rust, Python, Go, and Ruby, alongside a CLI and MCP workflows. The runtime accepts OCI images from Docker Hub, GHCR, ECR, GCR, and other registries. Public internet access is enabled by default, while private, host-local, link-local, and metadata destinations are blocked; egress can be allowlisted or disabled. Secret substitution has limits: it requires intercepted TLS by default, and body substitution is opt-in with format and size limits. The runtime is open source under Apache 2.0. A free plan is available; paid plans start at $49 per month. Microsandbox Cloud is in private beta and requires an access request.
For and against
For
- Each sandbox has its own Linux kernel and network boundary.
- Local runtime needs no daemon, root service, or account.
- Supports five language SDKs, CLI, and MCP workflows.
- Free plan available; Builder costs $49 a month.
Against
- Cloud access is in private beta and requires a request.
- Secret substitution requires intercepted TLS by default.
- Free plan caps each sandbox at 1 vCPU and 512 MiB memory.
The verdict
microsandbox offers local and self-hosted microVM isolation, with a free plan and paid options starting at $49 a month. Its cloud service is still in private beta, and credential substitution has specific requirements and limits.
Who it suits
microsandbox may suit developers who need to run untrusted workloads locally or on their own infrastructure, with SDKs, CLI, and MCP workflows available.
Plans and prices
Free
5 vCPU-hours · 20 memory GiB-hours · 20 disk GiB-hours · up to 3 sandboxes
Read 30 Sep 2026 · microsandbox.dev
Builder
500 vCPU-hours · 2,000 memory GiB-hours · 2,000 disk GiB-hours · 50 GiB durable storage
Read 30 Sep 2026 · microsandbox.dev
Teams
2,000 vCPU-hours · 8,000 memory GiB-hours · 8,000 disk GiB-hours · 250 GiB durable storage
Read 30 Sep 2026 · microsandbox.dev
Enterprise
4,000 vCPU-hours · 16,000 memory GiB-hours · 16,000 disk GiB-hours · 500 GiB durable storage
Read 30 Sep 2026 · microsandbox.dev
On the record
- Cloud availability
- Microsandbox Cloud is in private beta and requires users to request access.docs.microsandbox.dev · read 30 Sep 2026
- Company
- Microsandbox is designed and engineered by Super Rad Company, whose stated purpose is building tools for the agentic future.superrad.company · read 30 Sep 2026
- Credential handling
- Bound secrets are represented by placeholders inside the sandbox and substituted host-side for supported intercepted requests to approved destinations.microsandbox.dev · read 30 Sep 2026
- Credential limitation
- Secret substitution requires intercepted TLS by default, and body substitution is opt-in with format and size limits.microsandbox.dev · read 30 Sep 2026
- Images
- The runtime accepts OCI images from Docker Hub, GHCR, ECR, GCR, or another registry.docs.microsandbox.dev · read 30 Sep 2026
- Integrations and languages
- The product supports SDKs for TypeScript, Rust, Python, Go, and Ruby, plus a CLI and MCP workflows.microsandbox.dev · read 30 Sep 2026
- Isolation
- Each sandbox is a microVM with its own Linux kernel, filesystem, and network boundary, rather than a container sharing the host kernel.docs.microsandbox.dev · read 30 Sep 2026
- License
- The runtime is open source under the Apache 2.0 license.microsandbox.dev · read 30 Sep 2026
- Local runtime
- The local runtime starts on the user's machine without a daemon, root service, or account.microsandbox.dev · read 30 Sep 2026
- Network controls
- By default, sandboxes can reach the public internet while private, host-local, link-local, and metadata destinations are blocked; egress can be allowlisted or disabled.microsandbox.dev · read 30 Sep 2026
- Self-hosting
- The runtime can be run on the user's own servers or clusters, and the cloud platform can be deployed in the user's infrastructure.docs.microsandbox.dev · read 30 Sep 2026
- Snapshots
- Local full snapshots can preserve disk, memory, and running processes; managed cloud currently supports disk snapshots from stopped persistent sandboxes and disk restore.microsandbox.dev · read 30 Sep 2026
- Support
- The product FAQ directs users with questions to its Discord community.microsandbox.dev · read 30 Sep 2026
- What it does
- Microsandbox is a local-first microVM runtime for running untrusted workloads, including AI agents, user code, plugins, CI jobs, scrapers, and automation.docs.microsandbox.dev · read 30 Sep 2026
