What is BrowserPod?
BrowserPod is a sandboxed runtime that executes server-side code in the browser. It takes code written in supported languages as input and runs it inside a WebAssembly-based Linux kernel, producing a terminal session, a POSIX filesystem, and optionally a public URL for any server started within. The platform is built by Leaning Technologies, the company behind WebVM, and runs entirely on the user's device.
Key Features
- Zero-cloud Linux kernel — A Linux-compatible kernel runs in the browser via WebAssembly, so there is no cloud compute to provision or queue for.
- Low-cost compute — At $0.01 per hour with 1,000 free hours each month, it is positioned as 8x cheaper than typical cloud sandboxes.
- Browser-native isolation — Code runs inside the browser's security boundary, keeping untrusted code within the tab and away from local files or unauthorized network calls.
- POSIX-like filesystem — Storage uses the Origin Private File System or IndexedDB, supports persistent or ephemeral instances, and accelerates subsequent visits by reusing persisted storage.
- Portals for instant sharing — Watches for ports opened in the sandbox and maps them to shareable URLs, turning a running dev server into a live link.
- Multi-runtime support — Node.js and Rust are live, Python is in preview, with C++, Go, and Ruby on the roadmap; git, bash, npm, and a real terminal are included.
- Agentic output ready — Designed to run AI coding agents or their generated code without exposing your infrastructure.
Use cases
- AI coding agents: Run agent-generated code in a browser sandbox that stays within the tab, with no access to the host machine.
- Live product demos: Start a server inside a pod and share the generated URL to anyone, making the demo the actual running product.
- Runnable documentation: Embed a pod in documentation so readers execute examples rather than copying them manually.
- Development environments: Use git, bash, and npm within a browser-hosted terminal for full-stack development without a local setup.
How does BrowserPod work?
Users initialize a pod with an API key, create a default terminal, and write files to the pod's filesystem using the JavaScript API. Commands are executed in the WebAssembly-based kernel, with storage provided by OPFS or IndexedDB. Portals automatically generates a URL when the sandbox opens a network port, making the running service accessible to others.
FAQ
Does BrowserPod need a server?
No. BrowserPod runs entirely in the user's browser via WebAssembly, so there is no cloud compute to provision or queue for. It boots in milliseconds and does not degrade under load because each session uses the local device.
Which runtimes are supported?
Node.js and Rust are live, Python is in preview, and C++, Go, and Ruby are on the roadmap. The sandbox includes git, bash, npm, and a real terminal.
What does BrowserPod cost?
Compute is $0.01 per hour, and users receive 1,000 free hours every month. Storage is unlimited with no charges, and there is no limit on concurrent environments.
Is BrowserPod secure for untrusted code?
Yes. Since it runs inside the browser sandbox, it inherits the browser's battle-tested security boundary. Untrusted code cannot escape the tab to reach local files or make unauthorized network calls.
