What’s centrally operated, and what isn’t
WarmHawk centrally operates three things: this marketing site, the Stripe webhook that issues licenses, and the WarmHawk Connect relay that lets a licensed install sign a mailbox in with Google or Microsoft. Your self-hosted instance — containers, nginx, TLS, Postgres — is entirely yours to run, which is the whole point of a self-hosted product. You get your own bundled Uptime Kuma and a free OTEL export endpoint to monitor it yourself.
What WarmHawk operates centrally
Three things, and only three things, run on infrastructure WarmHawk itself controls. Everything else — every customer’s actual sending engine, dashboard, database, and mail delivery — runs on that customer’s own server instead.
The Connect relay stores nothing. It checks your license and forwards the mailbox sign-in back to your own server. Google’s sign-in tokens pass through it in transit, because Google requires a secret WarmHawk keeps off customer servers; Microsoft’s never reach it. See the privacy policy for exactly what passes through.
Your own instance
WarmHawk does not operate, and does not report uptime on, any customer’s own self-hosted deployment. Your containers, your nginx, your TLS certificate, your Postgres database — none of it runs on WarmHawk-controlled infrastructure, so there is no central status WarmHawk could honestly report on your behalf. That separation is the entire point of a self-hosted product: your instance’s uptime is exactly as good as the server you run it on, not tied to WarmHawk’s.
Instead, every install gets its own visibility built in, on by default:
- •A bundled Uptime Kuma instance, installed automatically by
install.sh, giving you real-time, 1-minute-interval health checks across every service on your own instance — visible only to you. - •A free, native OTEL export endpoint you can point at whatever deeper observability tooling you already use — Grafana, SigNoz, Honeycomb, or anything else that speaks OTLP — if you want more than Uptime Kuma’s dashboard gives you.
For backup/restore procedures and troubleshooting a self-hosted instance, see the docs.