A desktop application that manages the wiki server farms — local and hosted — for a community. The north star the DNS Module serves: the Guide turns DNS, pinning, and Embassy provisioning into buttons, so a Homelab is something you run, not something you hand-configure.
## What It Manages
- The **local farms** — start, stop, health, the wiki-local offline toggle - The **hosted farm** — the public mirror and its sync - **DNS** for every owned domain, through the deSEC-backed WASM on Spin service - **Pinning** and the Federated Pinning Service cluster - **Embassy provisioning** — a new Homelab from a form: domain, deSEC zone, Caddy front, services
## Tauri, Not Electron
The instinct is "Electron-style", but the modern choice is **Tauri**. Tauri ships a roughly 5 MB binary using the operating system's own webview and a Rust core; Electron bundles Chromium and Node for 80–150 MB and far more memory. Both take a TypeScript front-end, so the app code is much the same either way. Tauri also sits naturally beside the WebAssembly and Rust direction — the same Rust that powers the WASM on Spin service — and its small, auditable footprint fits a local-first tool a community will trust.
## The Shape
The Guide is the **orchestrator**, not the logic. It consumes the same services the rest of the stack exposes — the Spin DNS service, the pinning cluster, the farm scripts — and presents them. Every capability stays usable without it (a script, an API, a wiki page); the Guide is the friendly face over a system that already works headless.
## Links
- Tauri v2 
— the desktop framework
- deSEC — the DNS the Guide drives
## See - Farm DNS Automation — the first capability it drives - Calling the Module — why the Guide consumes a service, not the raw core - Federated Pinning Service — another limb it will manage