FAQ

Yes — AlertINT is self-hosted. It runs as a single binary with local state, so your alert data stays with you.

No. Alertmanager still routes and manages alerts. AlertINT receives a webhook copy and builds investigation context.

No. AlertINT never changes Alertmanager, Kubernetes, or your infrastructure — see Scope and limits.

Because engineers increasingly investigate through agentic tools. MCP lets those tools inspect AlertINT state and query telemetry without copy-pasting alert text into chat.

Alert payloads alone are shallow. Prometheus queries let the connected agent inspect metrics around the incident window.

No. AlertINT observes and reports. Operator-controlled, approval-gated write workflows are a far-future direction.

AlertINT is Fair Source. Fair Source is a publishing model — pioneered by Sentry and others — where the code is public to read, use, modify, and self-host, with one narrow restriction (you can't repackage it as a competing commercial offering) that lifts on a fixed schedule.

Concretely, AlertINT is licensed under FSL-1.1-ALv2 (the Functional Source License), and every release automatically converts to the Apache 2.0 open source license two years after it ships. So it is not OSI "open source" on day one, but each version becomes fully open source on a predictable timeline — a practice called Delayed Open Source Publication.