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

For Enterprises

BrowserPod on your own infrastructure

Self-host the runtime and the network stack, vendor BrowserPod into your build, or ship it inside your product. Your pods, your network, your logs.

Built by Leaning Technologies, the team behind WebVM and CheerpJ. Trusted by organisations around the world.

NASA
Siemens
Moody's
Euronext
Ticketmaster
Yarn
ADP
Dalkia
US Customs

A real on-premise solution

01

Self-hosted runtime

Mirror the runtime and disk images on your own servers, or vendor them into your build, for air-gapped and regulated networks.

02

Self-hosted networking

Run your custom network stack, or self-host BrowserPod Edge, and get full control of your users' data.

03

Redistribution

Ship BrowserPod inside your product to your own customers, under an OEM agreement.

04

Support

Support with agreed SLAs and a dedicated engineer for your team.

Self-hosting

Enterprise users of BrowserPod get a licensed copy of all the BrowserPod runtime assets and disk images to serve from their own servers. Pods are served by the self-hosted runtime, and load nothing from our CDN.

Custom images and custom networking implementations that run on-premise can be used in conjunction with the self-hosted runtime.

BrowserPod Edge can also be self-hosted. Edge is based on Cloudflare Workers and Durable Objects. Self-hosted, it runs on your own Cloudflare infrastructure, with your own certificate authority and API domain, and your pods connect to it instead of ours. The egress rules, the audit logs and the Portal domain are all yours to customise.

Redistribution, such as shipping BrowserPod inside a hostable platform to your own customers, and vendoring can be provided with a custom license arrangement.

Your network, your rules

Hosted Edge carries pod traffic through our infrastructure, under our audit and retention policies. That suits most teams. If your users' traffic can't pass through a third party, self-hosted Edge keeps it on yours.

Hosted or self-hosted

Part Hosted Self-hosted, with Enterprise
Runtime and disk images Our CDN Your servers or your build
Pod network traffic Through our Cloudflare network Through your own Cloudflare account, or your custom network backend
Egress rules Default allowlist, or custom on Pro Your own policy
Audit logs Kept by us for 12 months Kept by you
Portal domain and certificate authority Ours Yours

How we work together

  1. Talk to us

    Tell us what you're building and where it has to run.

  2. Prototype

    Build on the free library and hosted Edge while we scope the setup.

  3. Self-host

    Deploy the runtime, images and Edge on your infrastructure with our engineers.

  4. Ship

    Go live with Enterprise support, out-of-cycle updates, and a dedicated engineer.

Questions

Is BrowserPod open source?

No. It is free for any use, with attribution, under a short licence. Enterprise adds the rights to self-host, vendor and redistribute it.

Can we pin a version?

Yes. Every runtime version is permanent, and a lockfile pins it.

Can it run without reaching your servers?

Yes, with Enterprise. You host the runtime, the disk images and Edge, and pods never contact our infrastructure.

What does hosted Edge see?

Code and files stay on the device. With hosted Edge, traffic passes through our network, encrypted end to end except HTTP and HTTPS to Cloudflare-hosted sites, which our Worker re-originates. Self-hosting keeps all of it on yours.

Can we remove the attribution?

Yes. Enterprise removes it.

Do we need Enterprise to use BrowserPod in production?

No. The library is free for any use, production included, with attribution. Enterprise is for self-hosting, vendoring and redistribution.

Can we use hosted Edge while we evaluate?

Yes. Prototype on the free library and hosted Edge, then move to self-hosting when you're ready.

Can we bring our own disk images?

Yes. With Enterprise, the root and user images can come from your own servers, built with the tools your pods need.

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