leaningtech · alexp-sssup · Feb 17, 2026 · Feb 17, 2026 · Feb 17, 2026 · Feb 17, 2026
diff --git a/content/blog/banners/BrowserPod-for-nodejs.jpg b/content/blog/banners/BrowserPod-for-nodejs.jpg
diff --git a/content/blog/browserpod-1.0.mdx b/content/blog/browserpod-1.0.mdx
@@ -0,0 +1,164 @@
+---
+title: "BrowserPod: universal in-browser sandbox powered by Wasm (starting with Node.js)"
+description: |
+  BrowserPod 1.0 is live: universal in-browser code sandboxes powered by WebAssembly. Node.js available today.
+authors:
+  - alessandro
+pubDate: "February 18 2026"
+heroImage: "./banners/BrowserPod-for-nodejs.jpg"
+tags:
+  - BrowserPod
+---
+
+import BrowserPodDemo from "@leaningtech/astro-theme/components/blog/BrowserPodDemo_1.0.svelte";
+import BrowserPodDemoRepl from "@leaningtech/astro-theme/components/blog/BrowserPodDemo_1.0-repl.svelte";
+
+Today we’re releasing [BrowserPod](https://browserpod.io) 1.0: a browser-based code sandbox for running untrusted code next to the user, with near-native speed, extremely low latency, strong data locality and very low running costs, while maintaining high fidelity with native/cloud execution.
+
+This first release ships with **BrowserPod for Node.js**, the first engine in a broader, language-agnostic platform: a universal execution layer for browser-based compute. Support for Python, Ruby, Go and Rust engines will be released in the next six months. Linux-class sandboxes, powered by CheerpX, will be added by the end of 2026.
+
+BrowserPod relies on WebAssembly to provide high-fidelity, fully compiled runtime engines for multiple languages that are robust to real-world computationally heavy, multithreaded and multiprocess loads.
+
+To get an idea of what BrowserPod can do, feel free to experiment with the Node.js REPL below, running completely on your device.
+
+<figure class="w-full">
+	<div class="w-full relative">
+		<BrowserPodDemoRepl client:only="svelte" />
+	</div>
+	<figcaption class="text-center">
+		Node 22 REPL running live in BrowserPod.
+	</figcaption>
+</figure>
+
+## Why BrowserPod — and why now?
+
+Increasingly, software has a need to safely execute untrusted code: generated by models, written by users, pulled from libraries, or assembled by agents. That’s changing the economics and the threat model of code execution. The key question is not _how_ to run code, but _where_ to run it, what it can reach, and what it costs to operate at scale.
+
+Cloud sandboxes are a common, default solution. But they also come with recurring tradeoffs:
+
+- Latency (spinning up sandboxes, network rounds trips, cold starts)
+- Cost (per-session infrastructure adds up fast)
+- Data exposure (shipping inputs/outputs to remote systems expands the surface area)
+
+BrowserPod flips the model: **keep execution inside the browser**, leveraging WebAssembly and the browser’s security model, while still providing a Linux-compliant environment (filesystem, processes, and networking).
+
+## What you can build with it (today)
+
+BrowserPod is designed to be a universal compute platform, powered by multiple runtime engines, starting with Node.js, but expanding to other languages very rapidly.
+
+This technology is the culmination of more than 10 years of unique experience that we have in building browser-based development tools and virtual machines based on WebAssembly.
+
+Here are the use cases that shaped the architecture from day one:
+
+### **1) In-browser agentic coding**
+
+Run AI-generated code in a sandbox next to the user, with fast startup, strong isolation, and better performance than typical cloud-based sandboxes. This is the most direct path to cutting per-session sandbox costs while tightening security boundaries and improving performance.
+
+### **2) Web-based IDEs and full-stack dev environments**
+
+Power “real” development workflows in the browser: package installs, dev servers, build tools, previews. All with high fidelity.
+
+### **3) Interactive docs and “live” library demos**
+
+Turn documentation into a runnable environment: examples people can modify, execute, and share without leaving the page.
+
+### **4) Education at scale**
+
+High-fidelity environments with minimal operational overhead. If you can avoid per-student sandboxes, you can meaningfully change what’s economically feasible.
+
+With BrowserPod, not only can compute stay local, but user data as well, making privacy-first applications much more practical and removing any jurisdiction risk connected to shipping user information to the cloud. Paired with the already visible trend towards the on-device execution of agentic models, we envision a world in which BrowserPod can power local-only personal agentic workloads in absolute privacy.
+
+## The feature that unlocks a lot: Portals
+
+BrowserPod includes **Portals**, a controlled networking feature that lets you expose services running inside a Pod through shareable URLs.
+
+That means you can run a dev server inside its sandbox and still get:
+
+- Live previews
+- Interactive demos
+- Collaborative troubleshooting
+- Shareable “click-to-open” environments
+
+All this, without computation being delegated to backend infrastructure.
+
+To see Portals in action, scan the QR code (below) with your mobile device. Any change to the code, will be reflected immediately to the device as well.
+
+<figure class="w-full">
+	<div class="w-full relative">
+		<BrowserPodDemo
+			client:only="svelte"
+			projectSource={{ type: "local", path: "vite1" }}
+			apiKey="bp1_650b51af6579eb358452af0ced948bc34a6d98693c2969af6ad1b1e74c3948ee"
+		/>
+	</div>
+	<figcaption class="text-center">
+		Svelte + Vite running live in BrowserPod.
+	</figcaption>
+</figure>
+
+## How does this work?
+
+<figure class="w-full">
+	![BrowserPod diagram](./images/Browserpod-diagram_2.webp)
+	<figcaption class="text-center">
+		Diagram of the BrowserPod architecture, illustrating the main components.
+	</figcaption>
+</figure>
+
+At its core, BrowserPod is built to be a high-fidelity, multi-language runtime environment.
+
+Pods provide:
+
+- Modular support for arbitrary language engines
+- A sandboxed runtime with a virtual filesystem. Disk state is provided via images streamed on-demand to the user device. Any change stays local to the browser and can be persistent, making it possible to get back to the previous disk state after reloading a Pod.
+- Process isolation and true concurrency via WebWorkers, suitable for real tools and workloads.
+- Controlled networking (ingress and egress) via Portals.
+
+BrowserPod builds on our previous experience in building browser-based virtual machines, with [WebVM](https://webvm.io) being its spiritual predecessor. The syscall layer of WebVM, which is powerful enough to run large scale, [unmodified native applications](https://labs.leaningtech.com/blog/webvm-20), serves as the core foundation of BrowserPod.
+
+## Why Node.js first
+
+We started with Node.js deliberately, not as an easy first step, but because it is one of the most challenging environments to test the robustness and fidelity of BrowserPod.
+
+Modern Node workloads are complex: they are package managers, build pipelines, dev servers, file watchers, and tooling ecosystems with complex dependencies, which assume a lot about the environment.
+
+Shipping Node.js as the first engine forces the platform to be robust from the start, and it sets the bar for everything that follows.
+
+## Roadmap and vision
+
+Today’s release of **BrowserPod for Node.js** is the first step of our ambitious release plan.
+
+Our roadmap includes numerous releases of new engines in the course of 2026:
+
+- March 2026: command line tools (shared by all engines) - bash, git, coreutils, ssh, and many others
+- April 2026: Python support
+- May 2026: Ruby support
+- July 2026: Go support
+- August 2026: Rust support
+- November 2026: **Linux-class workloads** (powered by the CheerpX WebAssembly Linux virtualization engine)
+
+By the end of 2026 BrowserPod will be able to run any Linux container in the browser with support for modern full-stack development, realizing our vision of building a universal in-browser execution layer.
+
+Throughout the year, we’ll also keep shipping continuous improvements in performance, compatibility, and developer ergonomics as we learn from real usage.
+
+If you have any questions or ideas for us, get in touch. The whole Leaning Technologies team, myself included, is available on [Discord](https://discord.leaningtech.com)
+
+## Try it out now
+
+import LinkButton from "@leaningtech/astro-theme/components/LinkButton.astro";
+
+<div class="flex items-center gap-2 flex-wrap">
+	<LinkButton
+		type="primary-browserpod"
+		href="https://console.browserpod.io"
+		label="BrowserPod Console"
+		iconRight="mi:arrow-right"
+		target="_blank"
+	/>
+</div>
+
+If you want to see what BrowserPod feels like in practice, start here: [https://console.browserpod.io](https://console.browserpod.io) and follow the instructions, or simply use our npm quickstart.
+
+`npm create browserpod-quickstart`
+
+We believe BrowserPod is a concrete step toward a bigger goal: making the browser a first-class execution environment for tools, services, and the next generation of AI-native products. We cannot wait to see what the community will build with BrowserPod.
@@ -61,6 +61,10 @@ const {
 				type === "secondary-mono-cj",
 			"border-white border-opacity-30 bg-blurple text-white hover:border-opacity-80":
 				type === "discord",
+			"border-white bg-[#2DA682] hover:bg-emerald-400 text-white hover:bg-[#909090] hover:text-white":
+				type === "primary-browserpod",
+			"bg-white/10 hover:bg-white/20 text-white border border-white/20":
+				type === "secondary-browserpod",
 		},
 	]}
 >

@@ -0,0 +1,21 @@
+<script>
+	import { TerminalPanel } from "@leaningtech/svelte-browserpod-editor";
+</script>
+
+<div
+	id="demo-repl"
+	class="flex w-full h-[25rem] p-2 bg-black/30 backdrop-blur-md border border-white/10 rounded-2xl"
+	aria-label="In-browser Node.js demo playground"
+>
+	<TerminalPanel
+		ctxId="demo"
+		tabs={[
+			{
+				id: "repl-standalone",
+				label: "REPL",
+				commands: [["node"]],
+				autoRun: true,
+			},
+		]}
+	/>
+</div>
@@ -0,0 +1,112 @@
+<script>
+	import {
+		BrowserPodEditorProvider,
+		EditorPanel,
+		TerminalPanel,
+		PreviewPanel,
+		setAnalyticsCallback,
+	} from "@leaningtech/svelte-browserpod-editor";
+	import "@leaningtech/svelte-browserpod-editor/theme.css";
+
+	let { projectSource, children, apiKey } = $props();
+
+	const terminalTabs = [
+		{
+			id: "build",
+			label: "Build",
+			commands: [
+				["npm", "install"],
+				["npm", "run", "dev"],
+			],
+			autoRun: true,
+		},
+		{
+			id: "repl",
+			label: "REPL",
+			commands: [["node"]],
+			runOnActivate: true,
+		},
+	];
+</script>
+
+<div
+	id="demo"
+	class="flex w-full max-w-6xl h-[50rem] sm:h-[38rem] md:h-[32rem] lg:h-[34rem] mx-auto rounded-2xl overflow-hidden relative"
+	aria-label="In-browser Node.js demo playground"
+>
+	<div
+		class="flex flex-col md:flex-row w-full h-full gap-2 md:gap-4 p-2 bg-black/30 backdrop-blur-md border border-white/10 rounded-2xl"
+	>
+		<BrowserPodEditorProvider
+			{projectSource}
+			{apiKey}
+			ctxId="demo"
+			defaultFile="src/lib/Counter.svelte"
+		>
+			<!-- Editor + Terminal column -->
+			<div
+				class="flex flex-col gap-2 md:gap-4 w-full md:flex-[2] min-w-0 h-[55%] md:h-full"
+			>
+				<div class="editor-slot">
+					<EditorPanel />
+				</div>
+				<div class="terminal-slot">
+					<TerminalPanel tabs={terminalTabs} />
+				</div>
+			</div>
+
+			<!-- Preview column -->
+			<div class="preview-slot">
+				<PreviewPanel />
+			</div>
+		</BrowserPodEditorProvider>
+	</div>
+</div>
+
+<style>
+	:root {
+		--bpe-color-primary: #10b981;
+		--bpe-color-primary-hover: #059669;
+	}
+
+	.editor-slot {
+		display: flex;
+		flex: 1;
+		min-height: 0;
+		overflow: hidden;
+	}
+
+	.terminal-slot {
+		display: flex;
+		min-height: 6rem;
+		height: 35%;
+		overflow: hidden;
+	}
+
+	@media (min-width: 640px) {
+		.terminal-slot {
+			min-height: 10rem;
+		}
+	}
+
+	@media (min-width: 768px) {
+		.terminal-slot {
+			height: 35%;
+		}
+	}
+
+	.preview-slot {
+		display: flex;
+		flex-direction: column;
+		min-width: 0;
+		width: 100%;
+		height: 60%;
+	}
+
+	@media (min-width: 768px) {
+		.preview-slot {
+			flex: 1.7;
+			height: 100%;
+		}
+	}
+</style>
@@ -27,6 +27,8 @@
 		"./components/JNLPRunnerButton.astro": "./components/JNLPRunnerButton.astro",
 		"./components/AppletRunnerButton.astro": "./components/AppletRunnerButton.astro",
 		"./components/blog/BrowserPodDemo_Beta.svelte": "./components/blog/BrowserPodDemo_Beta.svelte",
+		"./components/blog/BrowserPodDemo_1.0.svelte": "./components/blog/BrowserPodDemo_1.0.svelte",
+		"./components/blog/BrowserPodDemo_1.0-repl.svelte": "./components/blog/BrowserPodDemo_1.0-repl.svelte",
 		"./components/nav/global/GlobalNavbar.astro": "./components/nav/global/GlobalNavbar.astro"
 	},
 	"scripts": {},
@@ -49,7 +51,9 @@
 		"@codemirror/lang-json": "^6.0.2",
 		"@codemirror/view": "^6.39.2",
 		"@iconify/svelte": "^5.1.0",
+		"@leaningtech/browserpod": "^1.0.0",
 		"@leaningtech/global-navbar": "workspace:^",
+		"@leaningtech/svelte-browserpod-editor": "^0.2.11",
 		"@replit/codemirror-lang-svelte": "^6.0.0",
 		"@sveltejs/vite-plugin-svelte": "^5.1.1",
 		"@tailwindcss/typography": "^0.5.10",