microsandbox.dev

mx

aspmx.l.google.com

alt2.aspmx.l.google.com

alt1.aspmx.l.google.com

alt3.aspmx.l.google.com

alt4.aspmx.l.google.com

ns

yew.ns.cloudflare.com

fatima.ns.cloudflare.com

caa

txt

google-site-verification=OpraNiRRy29clCCxlpksaHs49EE_v7h_evIJQ9HUAbE

v=spf1 include:_spf.google.com ~all

dmarc

v=DMARC1; p=reject;

User-agent: *
Allow: /
Content-Signal: ai-train=yes, search=yes, ai-input=yes

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: Googlebot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Bingbot
Allow: /

User-agent: Applebot
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: Meta-ExternalAgent
Allow: /

Sitemap: https://microsandbox.dev/sitemap.xml

# microsandbox

> a computer for anything, anywhere.

a real microvm with its own kernel. run generated code, third-party software, or your own apps. local, in our cloud, or inside your own perimeter.

macOS · Linux · Windows

private beta. access is by request.

## platform

- [local](https://microsandbox.dev/platform/local)
- [cloud](https://microsandbox.dev/platform/cloud)
- [byoc](https://microsandbox.dev/platform/byoc)

## features

- [isolation](https://microsandbox.dev/features/isolation)
- [network](https://microsandbox.dev/features/network)
- [credentials](https://microsandbox.dev/features/credentials)
- [sdk](https://microsandbox.dev/features/sdk)
- [snapshots](https://microsandbox.dev/features/snapshots)
- [performance](https://microsandbox.dev/benchmarks)
- [how we compare](https://microsandbox.dev/compare)

## organization

- [enterprise](https://microsandbox.dev/enterprise)
- [pricing](https://microsandbox.dev/pricing)

## use cases

- [coding agents](https://microsandbox.dev/use-cases/coding-agents)
- [code interpreter](https://microsandbox.dev/use-cases/code-interpreter)
- [browser agents](https://microsandbox.dev/use-cases/browser-agents)
- [multi-tenant code execution](https://microsandbox.dev/use-cases/multi-tenant)
- [agent evals](https://microsandbox.dev/use-cases/agent-evals)
- [regulated workloads](https://microsandbox.dev/use-cases/regulated)

## comparisons

- [all comparisons](https://microsandbox.dev/compare)
- [vs apple container](https://microsandbox.dev/compare/apple-container)
- [vs cloudflare sandboxes](https://microsandbox.dev/compare/cloudflare-sandboxes)
- [vs daytona](https://microsandbox.dev/compare/daytona)
- [vs docker](https://microsandbox.dev/compare/docker)
- [vs docker sandboxes](https://microsandbox.dev/compare/docker-sandboxes)
- [vs e2b](https://microsandbox.dev/compare/e2b)
- [vs firecracker](https://microsandbox.dev/compare/firecracker)
- [vs gvisor](https://microsandbox.dev/compare/gvisor)
- [vs modal](https://microsandbox.dev/compare/modal)
- [vs northflank](https://microsandbox.dev/compare/northflank)
- [vs vercel sandbox](https://microsandbox.dev/compare/vercel-sandbox)
- [benchmarks and qualifications](https://microsandbox.dev/benchmarks)

## docs

- [introduction](https://docs.microsandbox.dev/getting-started/introduction): what microsandbox is and why agents need isolated machines.
- [quickstart](https://docs.microsandbox.dev/getting-started/quickstart): install microsandbox and run your first sandbox.
- [ai agents](https://docs.microsandbox.dev/getting-started/agents): give agents the ability to create and manage sandboxes.
- [cli overview](https://docs.microsandbox.dev/cli/overview): manage sandboxes from the terminal.
- [sdk overview](https://docs.microsandbox.dev/sdk/overview): use microsandbox from typescript, python, rust, and go.
- [networking](https://docs.microsandbox.dev/networking/overview): control outbound access, dns, and tls interception.
- [images](https://docs.microsandbox.dev/images/overview): boot from oci and disk images.
- [recipes](https://docs.microsandbox.dev/recipes/docker): run microsandbox in docker on linux.

## agent discovery

- [api catalog](https://microsandbox.dev/.well-known/api-catalog)
- [openapi description](https://api.microsandbox.dev/docs/openapi.json)
- [mcp server card](https://microsandbox.dev/.well-known/mcp/server-card.json)
- [agent skills index](https://microsandbox.dev/.well-known/agent-skills/index.json)

## source

- [github repository](https://github.com/superradcompany/microsandbox)

## Blog

These posts explain microsandbox's agent runtime model, microVM isolation, filesystem work, and product direction.

- [Protect API keys in AI agent sandboxes](https://microsandbox.dev/blog/sandboxes-that-lie-about-their-secrets): Keep API keys outside your AI agent sandbox. A runnable microsandbox example with host-side secret substitution, destination rules, and violation policies. (published 2026-06-01; category Engineering; tags microsandbox, secrets, sandboxing, agents, security; [Markdown](https://microsandbox.dev/blog/sandboxes-that-lie-about-their-secrets/markdown))
- [We made our filesystem 47× faster by deleting it](https://microsandbox.dev/blog/oci-filesystem-47x-faster): We replaced our user-space filesystem with a real disk image that the VM mounts directly. Here's how we got there, and what fell out along the way. (published 2026-05-19; category Engineering; tags microsandbox, erofs, fuse, performance, microvms; [Markdown](https://microsandbox.dev/blog/oci-filesystem-47x-faster/markdown))
- [Bring your own init: PID 1 handoff](https://microsandbox.dev/blog/bring-your-own-init): microsandbox needs its own init to boot the guest. Linux services often need systemd in that same PID 1 slot. Handoff is how we make both true. (published 2026-05-08; category Engineering; tags microsandbox, systemd, init, microvms; [Markdown](https://microsandbox.dev/blog/bring-your-own-init/markdown))
- [Why your AI agent needs its own machine](https://microsandbox.dev/blog/your-agent-its-machine): Prompt injection has no clean fix at the model layer, and containers were never designed to isolate workloads from themselves. The case for running every agent inside its own microVM. (published 2026-04-14; category Announcements; [Markdown](https://microsandbox.dev/blog/your-agent-its-machine/markdown))