Integrations
Implemented channels are clearly separated from provider targets that need credentials and delivery enablement.
SlackImplemented
Incoming webhook notifications with structured incident and recovery payloads.EmailImplemented
wp_mail delivery with branded incident subjects and digest-ready copy.WebhooksImplemented
Signed outbound JSON with delivery logs and HMAC verification guidance.PagerDutyProvider Target
Trigger, acknowledge, and resolve mapping for ErrorNotifier incident state.Microsoft TeamsProvider Target
Incoming webhook or workflow-card mapping for incident and recovery notifications.DiscordProvider Target
Channel webhook message mapping for community or operations rooms.JiraProvider Target
Create-ticket and link-ticket workflow for confirmed incidents and grouped errors.LinearProvider Target
Issue-linking workflow for engineering triage queues.GitHubProvider Target
Release, commit, and issue association path tied to the release/artifact API.Provider readiness
Provider targets define the event mapping, credential shape, and operator expectation before live delivery is enabled.
Active delivery
Use email, Slack, and signed webhooks for production alerts today. Add PagerDuty or Teams through the generic webhook path until native delivery is enabled.
Next docs
Open the integration guide for provider mapping and secret-handling rules.
Public demo
Review the real product screens with read-only mock data
Open the demo workspace to inspect monitors, incidents, domains, alert channels, status pages, projects, issues, automated test runs, releases, artifacts, audit history, and umbrella reports without creating an account.