01
Processes as Wasm instances
Each process is an isolated Wasm instance — own stack, heap, syscalls, and permissions. One crash can never corrupt another.
// erlang-inspired · webassembly · rust
Isolated lightweight processes, fault tolerance, per-actor sandboxing, HTTP/WS/SSE serving, and secure clusters you can hook into live — written in Rust, TypeScript, or Go.
Each process is an isolated Wasm instance — own stack, heap, syscalls, and permissions. One crash can never corrupt another.
Wasmtime fibers suspend a guest’s “blocking” call while the host awaits. Millions can wait for almost nothing.
Tokio tasks multiplexed over a few threads, with epoch interruption for BEAM-like fairness. ~2.4M spawns/sec.
Traps become process exits; links and monitors propagate failure so supervisors restart exactly what broke.
A component becomes a high-throughput web server — a fresh sandboxed instance per request, one process per connection. Head-of-line blocking is impossible by construction.
Write a component in any of three languages over one actor wire, and they interoperate. A Rust client calls a TypeScript service, fully typed.
Nodes connect over QUIC + mutual TLS for cross-node messaging — and you attach a live JavaScript REPL to a running node, like iex --remsh.
Every process gets nothing unless granted — capabilities are explicit, scoped, revocable.
Processes, mailboxes, links, and supervisors — implemented as a runtime-agnostic core.