Running Node.js in the browser shouldn't require a sales call.
We built Nodepod because we had a problem at Scelar. We needed to run generated code securely in the browser for our AI platform builder. The only existing solution (WebContainers) was proprietary, opaque, and hidden behind an enterprise sales process. We couldn’t even get a straight answer on pricing.
So, we spent a year building our own, and we are making it 100% free and open-source (Custom MIT).
Nodepod is a browser-native Node.js runtime. Unlike other solutions that rely on heavy multi-megabyte WASM binaries, Nodepod is a lightweight (~600KB) system built on TypeScript polyfills and a custom execution engine.
What makes it different?
True Sync/Async Bridging: We use
SharedArrayBufferandAtomicsto allow synchronous Node methods (likereadFileSyncorexecSync) to run correctly in an async browser environment.Instant Boot: It starts in ~100ms (vs 2-5 seconds for WASM alternatives).
Full Tooling: It includes a virtual filesystem, a custom shell, and a Service Worker bridge for networking. You can run
npm install express, start a server, and preview it live.
To prove it works, we also released wZed—a browser-native IDE that runs entirely on Nodepod.
https://wzed.scelar.com/
We hope this helps anyone building code playgrounds, AI tools, or educational platforms who doesn't want to get locked into a proprietary ecosystem.
Frequently Asked Questions
What is Nodepod?
Nodepod is an open source tool listed on OpenHunts. The listing describes it as Running Node.js in the browser shouldn't require a sales call.
How does Nodepod work?
Nodepod highlights true sync/async bridging, instant boot, and full tooling. The listed feature details mention ways to we use SharedArrayBuffer and Atomics to allow synchronous Node methods (like readFileSync or execSync ) to run correctly in an async browser environment, it starts in ~100ms (vs 2-5 seconds for WASM alternatives), and it includes a virtual filesystem, a custom shell, and a Service Worker bridge for networking. You can run npm install express , start a server, and preview it live.
