If you have a chance, check it out, build something, share it around, and leave us feedback! We’re in beta, so any and all comments, feedback, and suggestions are welcome! You can also join our Discord community!

discord.gg/xGu2N5e5dq

WASM's linear memory can only grow, no memory.shrink in the spec on any engine, so a long-running app leaks by construction unless something recycles it. Natyv's host checkpoints your state, recycles the instance, and resumes automatically, ~30ms end to end.

github.com/natyv-io

That idle CPU number wasn't a given. First real measurement caught natyv sustaining 70-93% CPU continuously at idle, a real bug found specifically by benchmarking against real alternatives instead of testing in isolation. Fixed now, and the fix is a real commit too.

We built the same mail client 3 ways to check the claim honestly: natyv, Electron, and Tauri, same machine, same workload.

Disk size: 27MB (Electron: 244MB)
Idle RSS: 58MB (Electron: 331MB)
Idle CPU: 0.0%

Real commit history behind every number, not just a claim.

Desktop apps built on Electron ship an entire Chromium instance just to render a UI, real memory overhead paid on every launch whether the app needs a browser engine or not. Natyv skips it entirely: no DOM, no bundled browser, unless you're literally writing your app logic in JS.