# FAQ > Questions people actually ask before and after setting up InfraInbox. Web page: https://infrainbox.app/docs/help/faq/ ### Is InfraInbox a monitoring tool? No. It doesn't probe hosts or decide anything is down on its own — it sits downstream of the monitors you already run (Proxmox, Uptime Kuma, Alertmanager, a script) and turns what they send into one inbox with real incidents and routing. ### Isn't this just like Uptime Kuma, then? No — Uptime Kuma (or Proxmox, or Alertmanager) is a source *to* InfraInbox, not something it replaces. Keep running whatever already tells you a host is down; point it at InfraInbox and let InfraInbox handle deduplication, quiet hours and where the alert actually goes. ### Why not just send alerts straight to Telegram? You can, and plenty of tools do it natively. InfraInbox exists for what happens after you have more than one tool doing that: every source ends up with its own notification format, its own quiet hours (or none), and no way to see "did this actually go through?" in one place. InfraInbox gives you one inbox, one dedup logic and one set of routing rules across everything. ### What does it cost? Self-hosted InfraInbox is free. InfraInbox Cloud, the hosted version, is currently an invite-only beta and free for the duration of the beta. ### Is it open source? The core is planned to be released under the AGPL-3.0 licence. Its API contracts and its optional host watcher are planned as Apache-2.0. It isn't public yet. ### Does it phone home? No built-in telemetry calls home. The only outbound connections a self-hosted instance makes are to the destinations you configure (Telegram, Slack, Discord, your own webhook) and, only if you turn it on yourself, an OpenTelemetry endpoint you point it at. ### What data leaves my server? For a self-hosted instance: only what you send to the destinations you configure, and nothing else by default. Events, incidents and everything else stay in your own PostgreSQL database. ### Do I need an account? To use the dashboard, yes — a self-hosted instance creates its first administrator account during setup. Sending events doesn't need a user account at all; a source authenticates with its own key. ### Which tools work as sources today? Proxmox VE and Backup Server, Uptime Kuma, Prometheus Alertmanager and Grafana alerting, anything that speaks Gotify's format (Watchtower, Scrutiny, Beszel, Unraid and others), the InfraInbox agent (Docker and host heartbeats, currently a preview), and anything that can POST JSON via the generic events API. See [How sources work](https://infrainbox.app/docs/sources.md). ### Which destinations can I send to? Telegram, Slack, Discord, a signed webhook, and InfraInbox's own push notifications to a paired phone. Email, ntfy, Pushover and plain Gotify are not destinations yet. ### Is there an Android app? Not yet — the current app is iPhone-first. ### Does it support email? Not yet, as a source or a destination. ### Can I use it for more than one server? Yes — each source is independent, and a workspace can hold as many as you add. Running one InfraInbox instance across many physical servers, VMs and tools you monitor is exactly what sources are for. ### Can InfraInbox restart my containers or otherwise act on my infrastructure? No. InfraInbox only receives and routes notifications — it has no control-plane access to start, stop or otherwise manage anything it hears about. ### Is there a limit on how many sources or events I can have? There's no invented limit on the number of sources or events. There are payload limits on individual requests — see [Event fields and severities](https://infrainbox.app/docs/reference/event-fields.md) — and retention settings decide how long old data is kept. ### How long is data kept? Retention is configurable per workspace, per data type (events, resolved incidents, deliveries, raw payloads, audit log), in days — or kept forever if you set it that way. An open incident is never purged regardless of its age. ### Does it back up itself? No — you back up your own PostgreSQL database and the InfraInbox data volume (which holds the master encryption key), the same way you'd back up any self-hosted service. See [Backups and upgrades](https://infrainbox.app/docs/self-hosting/backup-and-upgrade.md). ### What happens during quiet hours? Notices below a destination's quiet-hours threshold (CRITICAL by default) are held back, not delayed — they don't arrive late once quiet hours end. See [Quiet hours](https://infrainbox.app/docs/notifications/quiet-hours.md). ### I muted/silenced a source — does it stop monitoring it? No. Events still arrive and incidents still open; only the alerts are held back. Silencing is purely about notifications, never about visibility. ### Can I try it before installing anything? Self-hosting is the way to try it today: one Docker Compose file plus PostgreSQL. See the [quick start](https://infrainbox.app/docs/start/quickstart.md). ### Where do I get help? [community link] for questions and discussion, or [support email] directly. ### I found a bug or have a feature request — where does that go? [community link].