The right installation depends on the provider that already runs your home and how closely you want Navet integrated with it.
| Route | Best for | What to expect |
|---|---|---|
| Home Assistant custom panel | A Navet entry inside Home Assistant | Home Assistant hosts the panel integration. |
| Home Assistant add-on | Home Assistant OS users who prefer an add-on | Navet runs as an add-on and opens through Ingress. |
| Docker / standalone | Independent hosting and container workflows | You operate Navet as its own web application. |
| Homey | Homey users | Navet connects through the Homey provider flow. |
| openHAB | openHAB users | Navet connects to your openHAB instance. |
| Navet Dev | Testing unreleased builds | Faster updates with higher change risk. |
Recommended starting point
If you use Home Assistant, begin with its guide and choose between the custom panel, add-on, and standalone routes based on where you want Navet to run. Use Navet Dev only when you intentionally want to test development builds.