Virtual containers,
running in your browser.
Drag a full backend stack onto a canvas — a Node app plus Postgres, Redis, Kafka and Search — and run it live. No CPU emulation: your app runs on the browser's own V8, the databases are WebAssembly, all wired over an in-tab network. No server, no install.
Databases, not VMs
Postgres, Redis, Kafka and Search compiled to WebAssembly — real wire protocols, no Linux VM, no CPU emulation.
Node on the browser's V8
Your Express or Next app runs on the tab's own V8. Dependencies install from npm right in the browser — no emulation, near-native speed.
Wired over an in-tab LAN
Drag the app onto a database and they share a virtual network — your code reaches db:5432 with the stock pg / ioredis / kafkajs clients.
Live preview
A same-origin service-worker bridge streams your app's HTTP server into an iframe. Edit the code, re-run, and watch it update.
A Node REPL
The app container opens an interactive Node REPL — require your packages and query the databases live, right in the tab.
Zero backend
It all runs in the tab. No servers to provision, nothing leaves your machine. Close it and it's gone.
How it works
Your app runs on the browser's own V8 — no CPU emulation. It's real Node.js (Express, Next), and its dependencies install straight from npm in the tab.
The databases are WebAssembly services — Postgres, Redis, Kafka and Search each speak their real wire protocol from a compact wasm module, with no operating system underneath.
App and databases share one in-tab virtual network, so the app reaches each by name over TCP with stock npm clients. A service worker forwards the app's port into a live preview iframe.
Node.js today — Python and Rust are coming next.
Build a stack and watch it boot.
Open the demo