You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/browserpod-1.0.mdx
+26-13Lines changed: 26 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,18 +5,18 @@ description: |
5
5
authors:
6
6
- alessandro
7
7
pubDate: "February 18 2026"
8
-
heroImage: "./banners/BrowserPod_beta-hero.png"
8
+
heroImage: "./banners/BrowserPod-for-nodejs.jpg"
9
9
tags:
10
10
- BrowserPod
11
11
---
12
12
13
-
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.
13
+
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.
14
14
15
15
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.
16
16
17
17
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.
18
18
19
-
To get an idea of what BrowserPod can do, feel free to experiment with the [Node.js](http://Node.js) REPL below, running completely on your device.
19
+
To get an idea of what BrowserPod can do, feel free to experiment with the Node.js REPL below, running completely on your device.
20
20
21
21
[ REPL DEMO ]
22
22
@@ -34,7 +34,7 @@ BrowserPod flips the model: **keep execution inside the browser**, leveraging We
34
34
35
35
## What you can build with it (today)
36
36
37
-
BrowserPod is designed to be a universal compute platform, powered by multiple runtime engines, starting with [Node.js](http://Node.js), but expanding to other languages very rapidly.
37
+
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.
38
38
39
39
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.
40
40
@@ -79,7 +79,12 @@ To see Portals in action, scan the QR code (below) with your mobile device. Any
Diagram of the BrowserPod architecture, illustrating the main components.
86
+
</figcaption>
87
+
</figure>
83
88
84
89
At its core, BrowserPod is built to be a high-fidelity, multi-language runtime environment.
85
90
@@ -90,9 +95,9 @@ Pods provide:
90
95
- Process isolation and true concurrency via WebWorkers, suitable for real tools and workloads.
91
96
- Controlled networking (ingress and egress) via Portals.
92
97
93
-
BrowserPod builds on our previous experience in building browser-based virtual machines, with WebVM [LINK] being its spiritual predecessor. The syscall layer of WebVM, which is powerful enough to run large scale, unmodified native applications ( [LINK TO ALPINE ARTICLE]), serves as the core foundation of BrowserPod.
98
+
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.
94
99
95
-
## Why [Node.js](http://Node.js) first
100
+
## Why Node.js first
96
101
97
102
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.
98
103
@@ -102,7 +107,7 @@ Shipping Node.js as the first engine forces the platform to be robust from the s
102
107
103
108
## Roadmap and vision
104
109
105
-
Today’s release of **BrowserPod for [Node.js](http://Node.js)** is the first step of our ambitious release plan.
110
+
Today’s release of **BrowserPod for Node.js** is the first step of our ambitious release plan.
106
111
107
112
Our roadmap includes numerous releases of new engines in the course of 2026:
108
113
@@ -117,15 +122,23 @@ By the end of 2026 BrowserPod will be able to run any Linux container in the bro
117
122
118
123
Throughout the year, we’ll also keep shipping continuous improvements in performance, compatibility, and developer ergonomics as we learn from real usage.
119
124
120
-
If you have any questions or ideas for us, get in touch. The whole Leaning Technologies team, myself included, is available on Discord [LINK]
121
-
122
-
[LARGE DISCORD BUTTON]
125
+
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)
If you want to see what BrowserPod feels like in practice, start here with two clicks ( [https://console.browserpod.io](https://console.browserpod.io)) and follow the instructions, or simply use our npm quickstart directly.
141
+
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.
0 commit comments