Self-hosted and Cloud
One product, two ways to run it. Self-hosting is a first-class edition, not a trial, and it stays free.
| Self-hosted | Cloud (beta) | |
|---|---|---|
| What runs | The InfraInbox server and PostgreSQL, on your hardware | The same core, run by us |
| Account | None. You create the first admin on your own server | An InfraInbox account, by invite |
| Price | Free | Free during the beta |
| Mobile push | Through our push relay, end-to-end encrypted, no account | Built in |
| When the whole homelab goes dark | Pair it with the Cloud’s off-site heartbeat, or a second machine you run | Built in |
| Your data | Stays on your server | Stored by us |
| Upgrades and backups | You, with the scripts in the compose bundle | Handled for you |
| Licence | Will be released under AGPL-3.0 | Hosted service terms (published with the beta) |
What you need to self-host
- A Linux machine, VM or LXC container that runs Docker Compose.
- An address your tools can reach. On your own network that can be a plain LAN address; for tools outside it, or the phone app away from home, a public HTTPS address or a tailnet.
- About ten minutes. The install guide walks through it, and TLS and reverse proxies covers Caddy, Traefik and Tailscale.
The push relay
Apple only delivers push notifications from a server holding the app’s signing key, so a self-hosted server reaches the iPhone app through our relay. The relay is free for self-hosters, with fair use per server key, needs no account, and only ever sees ciphertext: your server encrypts each notification for your device before it leaves.
InfraInbox Cloud
Cloud opens as an invite-only beta on the day v0.1 ships, and is free during the beta. Its first job is the one a self-hosted server can’t do for itself: noticing when your whole homelab, InfraInbox included, stops checking in. Pricing will be announced before the beta ends.