Directed deployment graph
Tryout with Compose and mock adapter
Verified for local evaluation. Compose runs Homenavi with simulated adapter data, so no home-device integration, radio, or hardware configuration is required.
Deployment guide
Choose a setup you can operate.
Start from the hardware and services you already have. This guide separates supported Homenavi paths from work that is planned, experimental, or dependent on an integration.
Interactive setup planner
Find the deployment that fits the home you run.
Answer five practical questions. The recommendation explains its trade-offs and only uses verified Homenavi paths.
- 1Hosting
- 2Hardware
- 3Connectivity
- 4Voice
- 5Experience
- 6Recommendation
Where should the core run?
Choose the boundary you want for the Homenavi core. Compose, hybrid, and Helm are standard choices; the tryout uses simulated data only.
Browse without the wizard
Supported deployment profiles
| Profile | Hosting | Complexity | Privacy and dependency | Ideal for |
|---|---|---|---|---|
| Tryout with Compose and mock adapter | Any computer that can run Docker Compose | Guided | The tryout runs locally and uses simulated adapter data. None for the Homenavi core or mock adapter. | Someone who wants to explore Homenavi before configuring devices or buying hardware. |
| Fully self-hosted with Compose | Your local server, NAS, or capable SBC | Guided | Core state and control remain on infrastructure you operate. Optional integrations may use external vendor APIs. | A first self-hosted deployment or a small household instance. |
| Hybrid local control | Existing local host plus explicitly chosen remote services | Moderate | Device control can remain local; external workloads need separate review. Only the external services you choose, such as remote inference. | Someone who wants local control without running every optional workload locally. |
| Advanced homelab with Helm | An existing Kubernetes cluster | Advanced | You control the cluster, network, storage, and secret boundaries. Optional, unless you configure external dependencies. | A homelab operator who already runs Kubernetes and wants its operational model. |
Architecture references
Know where the boundaries are.
Each map shows the control path, where devices attach, and the deployment boundary. The Compose tryout, local Compose, and Helm paths are verified; hybrid is in progress. Every production profile supports LAN/WAN integrations and Zigbee; Matter/Thread remains future work. For access outside your LAN, use Cloudflare Tunnel with cloudflared or Tailscale after local access is working and authentication is configured.
Verified
Directed deployment graph
Fully self-hosted with Compose
Verified on a local Docker host. Homenavi, storage, MQTT, and the edge run together; supported LAN/WAN integrations and Zigbee2MQTT communicate across the home network. Matter is shown as a future path.
Directed deployment graph
Hybrid cloud core with SBC adapters
In progress: run the Homenavi core in the cloud while an SBC keeps LAN/WAN and radio adapters at home. Keeping the core together is the advised model; splitting it into more parts is possible but not generally supported well.
Directed deployment graph
Advanced homelab with Helm
Verified for an existing Kubernetes operating model. Ingress, persistent storage, observability, and Homenavi services run in the cluster; LAN/WAN and Zigbee integrations remain supported, with Matter shown as future work.
Verified references