Inbound events

Keep your monitors. Change where they page.

Provider adapters normalize familiar payloads into one incident lifecycle. Every key is scoped to one service, can overlap safely during rotation, and carries a plan-bounded trigger limit.

Native adapters

Cloud, metrics, and infrastructure signals.

Datadog

Trigger and recover alerts while preserving the monitor identity for correlation.

Prometheus Alertmanager

Translate firing and resolved alert groups into stable WarnFire incidents.

Grafana

Receive Grafana alerting webhooks with source context and lifecycle state.

AWS

Accept CloudWatch through SNS and EventBridge event patterns.

Azure Monitor

Map Azure alert payloads into canonical trigger and resolution events.

Google Cloud

Ingest GCP monitoring notifications through a dedicated adapter.

Nagios and Icinga

Connect established infrastructure checks without replacing the monitoring layer.

PagerDuty Events API v2

Point compatible senders at WarnFire using familiar routing-key and dedup semantics.

Generic Events API

Send canonical trigger, acknowledge, and resolve events from custom systems.

Credential safety

One key, one service.

Create overlapping integration keys for rotation, set expiry and unused-key warnings, and revoke a key immediately without affecting unrelated services.

Storm control

Capacity that matches the plan.

Fresh triggers are bounded per key at 60/minute for Trial and Homelab, 300 for Team, 1,000 for Business, and 5,000 for Enterprise. Key-specific settings can lower—not raise—the plan ceiling. Idempotent retries are free, and recovery traffic remains open.

Testing

Exercise the real path before production.

Send labeled test events through the same validation, deduplication, rate limiting, incident creation, and notification path used by real monitoring traffic.

Connect one service and prove the loop.

Start with a test trigger, acknowledge it, and send its recovery.

Create a workspace →