Nagomi is an early Zaguán Labs research track exploring Gecko/libxul as a non-Chromium desktop application runtime. It is not public yet, not product-usable yet, and not presented as a framework people can adopt today.
Technical thesis: prove the runtime boundary first: a Nagomi-owned Rust/C++ host, Gecko/XRE startup, controlled lifecycle, and eventually a small window, event loop, and IPC bridge API.
Nagomi sits in the same broad problem space as desktop webview toolkits, but its current focus is much narrower: can Gecko be embedded cleanly and controlled from Rust without fighting the engine?
For now, the durable output is research: scope notes, feasibility checks, architecture boundaries, and small proof points around Linux-first Gecko embedding. The goal is clarity before claims.
Nagomi is in an early feasibility and productization track, focused on proving whether the embedding boundary is real enough to build on.
The repository is private while the project validates basic runtime control and avoids creating expectations before there is something reproducible.
The initial question is intentionally Linux-first. Other platforms, packaging, CLI polish, and ecosystem work are out of scope until the runtime boundary holds.
Nagomi is not a public toolkit yet. It is a research effort, not a release announcement, SDK, or production framework.
Nagomi is not a Firefox wrapper, not a browser skin, and not affiliated with or endorsed by Mozilla.
The research direction is specifically non-Chromium and avoids presenting Chromium-style desktop app assumptions as inevitable.
There is no public release, no stable API, and no promise that the research track becomes a general-purpose toolkit.
The Gecko embedding slot has been mostly empty for years, while Chromium-based runtimes and WebKitGTK-based Linux stacks dominate desktop webview development. Nagomi asks whether a Rust-native Gecko path can exist without pretending the hard parts are solved.
If the answer is no, the research still has value. If the answer is yes, the embedding API becomes the product, and everything else can follow later.
No public release yet: Nagomi will stay quiet until there is a small, honest demo or reproducible milestone worth showing publicly.