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
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.
A storageKey disk opens in one tab at a time, with a catchable error you can show in your editor.
What people build
In-browser IDEs
An editor, a terminal and a live preview, all running in the tab.
Framework playgrounds
Templates that install their dependencies and start a dev server on load.
Repository explorers
Clone a repository, browse it and run its scripts without a local checkout.
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.
-
Node.js, Rust, git, bash, npm
Node.js 22, Rust, git, bash, npm and pnpm. Vite, Next.js, Nuxt and Express run with Wasm overrides.
-
Loads on demand
A POSIX-like filesystem that streams in as needed and persists between visits with a storageKey.
-
Process isolation
The dev server, the watcher and the shell run as separate processes on one kernel.
-
Portals
A running dev server gets a public URL, so a preview is a link.
-
Embeddable
Use the built-in terminal or your own, inside your editor's layout.
From repo to running app
-
Boot a pod
Start a pod with a storageKey so the project survives reloads.
-
Bring the code
Write files through the API, or git clone a repository with Edge.
-
Install and run
npm install, then start the dev server, all in the pod.
-
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.
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.










