BrowserPod 3.0 runs Rust BrowserPod 3.0 runs unmodified Rust programs in the browser Announcement
Using a coding agent? Not sure where to start? Talk to us
Sign up for Edge Get an Edge API key, with 1,000 free hours Contact us Talk to the team

Development environments that run in the tab

BrowserPod is a microVM that runs in the browser. Build IDEs, playgrounds and coding tools where npm install, git clone and dev servers run on the user's device.

Why build it on BrowserPod

A development environment needs the real toolchain: a package manager that installs, a dev server that watches files, git, and a shell to drive it all. BrowserPod runs those real programs as processes on a Linux-like kernel, instead of reimplementing them in JavaScript, so the whole toolchain works.

Projects live in a POSIX-like filesystem stored in the browser. With a storageKey a project survives reloads, and only the parts of the base image a workload reads are downloaded.

When the dev server starts, Portals give it a public URL, so a preview is a link you can open in a tab or send to someone else. BrowserCode, our open playground, is built this way, with framework templates and GitHub cloning.

What you need to know

Wasm builds for native dependencies

Swap packages that ship platform binaries for their Wasm builds through overrides, such as esbuild-wasm and @rollup/wasm-node. Next.js uses @next/swc-wasm-nodejs with --webpack.

One tab per project disk

A storageKey disk opens in one tab at a time, with a catchable error you can show in your editor.

What people build

01

In-browser IDEs

An editor, a terminal and a live preview, all running in the tab.

02

Framework playgrounds

Templates that install their dependencies and start a dev server on load.

03

Repository explorers

Clone a repository, browse it and run its scripts without a local checkout.

04

Developer tools as web apps

Mock servers, package inspectors and converters that run their real tooling in the page.

What your environment gets

A real toolchain, a real filesystem and a way to share what's running, without a server per user.

From repo to running app

  1. Boot a pod

    Start a pod with a storageKey so the project survives reloads.

  2. Bring the code

    Write files through the API, or git clone a repository with Edge.

  3. Install and run

    npm install, then start the dev server, all in the pod.

  4. Share the preview

    Portals turn the dev server's port into a URL you can open.

Start a dev server

Boot with Edge so the pod can reach npm and expose a Portal, then run the usual commands.

app.js
import { BrowserPod } from "@leaningtech/browserpod";

const network = await BrowserPod.createEdgeNetwork({ apiKey: "your-key" });
const pod = await BrowserPod.boot({ network, storageKey: "my-app" });
const terminal = await pod.createDefaultTerminal(document.querySelector("#console"));

pod.onPortal(({ url }) => preview.src = url);
await pod.run("bash", ["-c", "npm install && npm run dev"], {
  terminal,
  cwd: "/home/user/app",
});

Questions

Which frameworks work?

Vite with React, Svelte or Vue, Next.js, Nuxt and Express, with Wasm builds swapped in for native dependencies through overrides.

Is there an example to look at?

BrowserCode, our open playground, is built on BrowserPod. It's free, needs no login and is Apache-2.0.

Does git work?

Yes. git runs in the pod, and cloning from GitHub works when the pod is connected through BrowserPod Edge.

Can users keep their projects?

Yes. Boot with a storageKey and the project's disk persists in the browser between visits.

Can we self-host BrowserPod?

Yes. Enterprise covers self-hosting the runtime and the network stack, vendoring it into your build and redistributing it in your product.

Stay informed with BrowserPod news

BrowserCode: a browser-based coding playground, powered by WebAssemblyBrowserCode is a free, open source, fully client-side coding playground. Open a tab, pick a template, clone a repo or pick an agent and start building. No account, no installs, no servers, no setup. Ana GabySoftware Engineer @ Leaning TechnologiesBeyond WASI: Running any Rust application in the browser with BrowserPod 3.0BrowserPod can now run real Rust programs in the browser, compiled from unmodified source with stock rustc and cargo. Yuri IozzelliSenior Software Engineer @ Leaning TechnologiesA Linux-like kernel in a browser tab - deep dive in the BrowserPod architectureHow the BrowserPod kernel supports running many Linux applications concurrently in the browser using WebAssembly. Alessandro PignottiCTO @ Leaning TechnologiesBrowserPod 2.0: in-browser WebAssembly sandboxes. Run git, bash, node, python...BrowserPod 2.0 ships with a real bash shell, git, and core Linux utilities. Yuri IozzelliSenior Software Engineer @ Leaning TechnologiesBrowserPod: universal in-browser sandbox powered by Wasm (starting with Node.js)Stefano De Rossi, Alessandro PignottiCEO @ Leaning TechnologiesBrowserPod: WebAssembly in-browser code sandboxes for Node, Python, and RailsBrowserPod Beta is live: zero latency in-browser code sandboxes in WebAssembly for Node, Python and Rails. Alessandro Pignotti, Stefano De RossiCTO @ Leaning TechnologiesBrowserPod: In-browser full-stack environments for IDEs and Agents via WasmBrowserPod is a WebAssembly-based, client-side container that brings full-stack dev environments to the browser, ideal for web IDEs, docs, and AI agents.Alessandro Pignotti, Stefano De RossiCTO @ Leaning Technologies