# What is InfraInbox?

> Your infrastructure inbox — what InfraInbox does, what it doesn't, and where to start.

Web page: https://infrainbox.app/docs/

Your infrastructure inbox. Keep your monitors. Fix your alerts. InfraInbox sits downstream of the tools you already run — Proxmox, Uptime Kuma, Alertmanager, a cron job, a script — and turns their notifications into one inbox with real incidents, sane deduplication, quiet hours and a route to wherever you actually want to hear about it: Telegram, Slack, Discord, a webhook, or its own phone app.

```text
Sources  →  Events  →  Rules  →  Incidents  →  Destinations
(Proxmox,     (what        (what to    (grouped,     (Telegram,
 Kuma,         arrived)      do with     deduplicated  Slack,
 a script,                   it)         problems)     Discord,
 the watcher)                                          webhook,
                                                        the app)
```

A **source** sends **events**. **Rules** decide what an event becomes: nothing worth a person's time stays in the log; anything that is groups into an **incident**, deduplicated by fingerprint so one flapping VM doesn't page you fifty times. Incidents route to **destinations** — one, several, or none, depending on severity, quiet hours and whatever else you've configured.

## What InfraInbox is not

- **Not a monitor.** It doesn't probe your hosts, poll your services or decide anything is down on its own. That's still Uptime Kuma's job, or Proxmox's, or Alertmanager's — InfraInbox becomes a source your monitor points at, not a replacement for it.
- **Not a push API.** You don't integrate against InfraInbox instead of Telegram; you point your existing tools at InfraInbox once, and it fans out to Telegram (and Slack, Discord, a webhook, its own app) from there.
- **Not on-call software.** There's no escalation chain, no paging schedule, no "page the next person if nobody acks in five minutes." It's one inbox with rules, silences and quiet hours — built for a homelab or a small team, not a 24/7 operations desk.

## Who it's for

Homelab operators and self-hosters first: people running Proxmox, a NAS, a handful of Docker hosts and a pile of monitoring tools that each shout into their own corner. If you've ever missed a failed backup because it was buried in fifty other Telegram messages, this is for you.

## Self-hosted, or Cloud

Run it yourself with one Docker Compose file and PostgreSQL — see the [quick start](https://infrainbox.app/docs/start/quickstart.md). InfraInbox Cloud, a hosted version, is in an invite-only beta and free for the duration of the beta; it isn't open for general sign-up yet.

## Where to go next

- [Quick start](https://infrainbox.app/docs/start/quickstart.md) — from a fresh install to your first incident
- [Core concepts](https://infrainbox.app/docs/start/concepts.md) — the vocabulary this guide uses
- [How sources work](https://infrainbox.app/docs/sources.md) — connecting the tools you already run
- [Cookbook](https://infrainbox.app/docs/cookbook.md) — recipes for common setups