The dashboard ships as a single Docker image and runs on hardware you control. Three database engines, no telemetry unless you configure it, and no account required to pull it.
No account, no registry login, no source checkout — the image is public on Docker Hub.
i18n.example.comAll systems operational
v0.23.0server mode
1156 keysoksmtp.example.comokgoogle-freeokWhat GET /api/healthreports on a running instance — the same probe your orchestrator and your uptime monitor read.
1
Container to run
3
Database engines
2
CPU architectures
0
Telemetry by default
There is no hosted dashboard to compare against — self-hosting is how the product runs. The honest question is not whether it is worth it, but what you take on.
Three modes, one image. The mode decides whether there is a login screen and what the instance depends on — it does not change the product.
Pick this if it is you, or one small team behind a network you already trust.
Pick this if several people need their own account on the same instance.
Pick this if you would rather not run a server at all.
All three carry the same 27 tables, so the choice is not about correctness. It is about how you back the instance up and who else needs to reach it.
What the published image ships and what the desktop app uses. No second service, no credentials to manage. The whole instance is this file plus one Docker volume.
127.0.0.1on purpose: reachable from this machine, from nowhere else. Local mode has no login screen, so widen it only behind a proxy, a firewall or a VPN you already trust.| Criterion | Desktop app | Self-hosted |
|---|---|---|
| Setup | Download and open | docker compose up -d |
| Database | SQLite, bundled | SQLite, PostgreSQL or MySQL |
| Where data lives | Your machine | Your infrastructure |
| Updates | Automatic | docker compose pull && docker compose up -d |
| Team access | Just you, on that machine | Your whole team — server mode needs an OIDC provider (yours, or ours) |
This page is the decision: whether to run it yourself, in which mode, on which engine. Everything that comes after the first successful boot is documented in one place, so there is only ever one version of it.