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-beta-announcement.mdx
+35-11Lines changed: 35 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,18 @@
1
1
---
2
-
title: "BrowserPod: Client-side sandboxing in the browser using WASM"
3
-
subtitle: "BrowserPod: zero latency in-browser code sandboxes in WebAssembly"
4
-
description: "placeholder"
2
+
title: "BrowserPod: WebAssembly in-browser code sandboxes for Node, Python, and Rails"
3
+
description: |
4
+
BrowserPod Beta is live: zero latency in-browser code sandboxes in WebAssembly for Node, Python and Rails.
5
5
authors:
6
6
- alessandro
7
7
- stefano
8
-
pubDate: "December 10 2024"
9
-
heroImage: "./banners/BrowserPod_beta-hero.png"
8
+
pubDate: "December 10 2025"
9
+
heroImage: "./banners/BrowserPod_beta-hero.webp"
10
10
tags:
11
11
- BrowserPod
12
12
---
13
13
14
14
TLDR: We’re beta-launching BrowserPod today, a WebAssembly-powered code sandbox for Node.js, Python and Ruby on Rails. Pods are instantly provisioned in-browser containers that use client-side compute, and can be exposed to the public internet. You can [start using BrowserPod now][BP-link], or keep reading to learn more.
Agentic coding, vibe coding, generative coding – different flavours of LLM-created or assisted code are everywhere, and their omnipresence are giving sandboxed computing environments a major moment in the spotlight. AI agents generate untrusted code, can introduce vulnerabilities and execute malicious instructions through prompt injection attacks or, on occasions, decide to wipe your whole filesystem. Sandboxes protect systems, local networks and data from threats by isolating agentic code in a secure virtual computing environment.
21
17
22
18
Sandboxes are typically ephemeral cloud instances. This is at first sight a great solution to the problem; by virtue of being in the cloud they’re naturally isolated from your system and they come with the additional benefit of portability, easily accessed through API calls and customized if needed. But they also come with a few drawbacks, for instance:
@@ -37,6 +33,27 @@ At Leaning Technologies, we’ve been at the forefront of WebAssembly-based solu
37
33
38
34
BrowserPod represents for us an opportunity to package everything we’ve learned in our 10+ years of experience to solve the problem of sandboxed computing. We can take advantage of the capabilities of modern browsers to reduce boot latency, pressure on data centers and the operational costs of provisioning virtual machines for untrusted user payloads.
Over the years, we’ve pursued multiple approaches to executing large-scale native payloads as browser applications. Although the details change for every scenario, there are a few general patterns that hold, these can be logically separated into three components:
@@ -99,7 +116,14 @@ What this means, in practice, is that whenever a Pod is booted it is assigned a
99
116
100
117
Any port which is bound to public interfaces inside the pod will be exposed to the internet via this secret link. By sharing a link like this, you can show early adopters or clients how your application works without setting up any actual hosting. Moreover, you’ll be able to test your application from mobile devices, for example by encoding the link in a QR code on your main device screen.
0 commit comments