Questions

An inbox for the alerts your infrastructure already sends. Proxmox, Uptime Kuma, Alertmanager, Grafana, Beszel, your cron jobs and scripts report to InfraInbox; it groups repeats into incidents, applies your rules and quiet hours, and notifies you on Telegram, Slack, Discord, a webhook or the iPhone app.

When you acknowledge an incident, re-notifying stops everywhere. When the matching recovery arrives, the incident closes and records how long it lasted.

Keep your monitors. InfraInbox doesn’t probe your services: it listens to the tools that do. Uptime Kuma keeps checking your sites; its notifications go to InfraInbox, which turns them into incidents alongside everything else you run.

That works for one tool. With five, a flapping service sends DOWN and UP all night, the backup report looks like every other message, nobody in the group chat knows who is handling what, and the job that silently stopped running never says anything at all.

InfraInbox sits in between: one incident per problem, one acknowledgement, recoveries that close things, and heartbeats for jobs that fail by not running.

People who run their own infrastructure: homelabs and self-hosters first, and small teams running a few servers for a business. If you have more than one tool sending you alerts, it is for you.

Sources: Proxmox VE and Proxmox Backup Server, Uptime Kuma, Prometheus Alertmanager, Grafana alerting, Gotify-compatible senders such as Beszel, Watchtower, Scrutiny and Unraid, heartbeat pings from any scheduler, and anything that can make an HTTP request.

Destinations: Telegram, Slack, Discord, signed webhooks and the InfraInbox iPhone app. Email, ntfy, Pushover and Gotify destinations and an Android app are planned.

No. InfraInbox receives and routes alerts; it never controls your infrastructure. It has no shell, start or stop actions.

Not in v0.1. It notifies the destinations your rules name and re-notifies critical incidents until someone acknowledges them, but it has no rotas or escalation chains.

Self-hosting is free. InfraInbox Cloud starts as an invite-only beta and is free during the beta. Pricing for Cloud will be announced before the beta ends.

A machine that runs Docker Compose. The compose file starts the InfraInbox server and PostgreSQL; the web dashboard is built into the server. For tools outside your network, or the phone app away from home, the server needs an address they can reach.

Not to self-host. The server, the app and the push relay work without an account.

No. Your events, incidents and settings stay on your server. If you use the iPhone app, notifications travel through our push relay end-to-end encrypted: the relay forwards ciphertext it can’t read and keeps only aggregate counts.

The server and the web dashboard will be released under AGPL-3.0 with v0.1. The API contracts, SDKs, templates and the agent are Apache-2.0. The mobile apps and the push relay are closed source and free to use.

The same product, run by us, so there is nothing to install or upgrade. Its first job is the one a self-hosted server can’t do for itself: an off-site heartbeat that notices when your whole homelab goes dark, InfraInbox included.

InfraInbox v0.1 is in development. The self-hosted release and the Cloud beta open on the same day. Join the waitlist and we’ll tell you when.

An iPhone app is in private testing and will ship with v0.1. Android is planned. One app can be paired with several InfraInbox servers.

Not in v0.1. Notifications follow your phone’s Focus and Do Not Disturb settings.

Yes. Quiet hours, severity rules and silences run on the server, so they apply to Telegram, Slack, Discord, webhooks and the app at once.

InnovaSoftware SRL, a software company in Romania.

Start with the docs and their troubleshooting page. Bugs and feature requests go to GitHub once the repository is public; until then, write to us from the contact page.