ALBDO is a Rust-native DOM render compiler and HTTP runtime for JSX / TSX apps. It statically analyses every component and ships exactly the right amount of JavaScript — including none at all.
By Bishal Sen & Pinaki Singha
Effect Lattice
ALBDO builds an EffectProfile for every component — hooks, async operations, I/O, side effects — and assigns a deterministic rendering tier. No annotations required.
No hooks, no async, no side effects. Ships zero JavaScript to the client.
Selective hydration for reactive regions only. The rest of the page stays static.
Complex client state. Full hydration where the component truly demands it.
Architecture
At compile time, ALBDO builds an EffectProfile for every component — analysing hooks, async, I/O, and side effects to determine exactly what JavaScript to ship.
SWC-powered AST analysis, lock-free parallel component traversal via DashMap, and a zero-JavaScript hot path served by axum + Tokio.
Tier A components produce zero bytes of client JavaScript. No hydration, no bundle, no runtime tax — pure HTML from the server.
Tier B components hydrate only the reactive islands that need it. The rest of the page remains inert, cutting transfer and parse time.
ALBDO accepts the JSX and TSX files your team already writes. No new primitives, no framework migration — just point and compile.
Ship a self-contained Rust binary. Docker images under 30 MB. Compare that to the 300–800 MB of a typical Node.js container.
Benchmarks
Measured on a working pre-release build. Not projections.
Explore the pre-release source, star the repo, or open an issue.