Open the incident
Create it manually or let an alert open it with service and severity context.
Incident response, redesigned
One place to run incidents well.
Open incidents, pull the right evidence window, and send clear updates — all in one workflow.
500+incidents/mo
99.99%uptime SLA
<1sevidence pull
GitHub
Stripe
Vercel
Notion
Figma
AtlassianCore principles
One home. One evidence workflow.
One clean update path.
01
Built for real incidents
Open, route, investigate, update, and close incidents in one place.
02
Bounded by evidence
Pull the right time window, scope it to the right service, and keep the result usable.
03
Clear for every audience
Give engineers depth and everyone else safe, clear status.
Collaboration And Delivery
Keep the right people informed without extra work
Send clear updates to responders, stakeholders, and support teams from the same incident workflow.
Role-aware updatesPublic or private delivery by policySafer summaries for non-technical audiences
Engineering
Full trace + root cause analysis
Private
Support
Redacted summary + ETA
Private
Stakeholders
Status + business impact only
Public
On-call
Alert context + runbook link
Private
Connected Sources
Keep the tools you already run
Relay can work with your current observability stack, so teams do not need to replatform before they can start using it.
Connect existing telemetry toolsPull incident windows without a stack rewriteStart without migrating your observability setup
SlackMessaging
TeamsMicrosoft
GitHubCode
BitbucketCode
GitLabCode
Google ChatMessaging
PagerDutyOn-call
SentryErrors
How it works
From intake to closure
Relay keeps the flow simple. Open the issue, gather the right evidence, then move the work forward from the same record.
Pull the evidence window
Relay gathers the right telemetry and marks whether the result is complete, partial, or blocked.
Analyze the context
Review the evidence pack, recent changes, and incident history to understand what is most likely happening.
Update and close
Track work, send updates, record the fix, and keep a clean incident record.
Comparison
Relay replaces scattered incident work with one focused workflow.
Without Relay
With Relay
Incidents scattered across chat threads, docs, ticketing tools, and internal memory
One system of record that stays current from intake to post-incident review
Engineers guessing where to start and support teams asking for updates from a different tool
A shared incident record with ownership, evidence, safe summaries, and next steps
Unclear whether missing telemetry means 'all good' or 'the source already dropped it'
Explicit evidence completeness and retention caveats surfaced in the workflow
Raw logs pasted into stakeholder updates or hidden entirely from support
Redacted snippets and role-aware views for engineers, escalators, viewers, and admins
A separate project to stand up logging and monitoring for teams that want help fast
An optional hosted observability add-on with setup artifacts and SDK-guided onboarding
Integrations
Connect the tools around the incident.
Relay pulls from where your telemetry already lives and pushes updates where your teams already work.
Observability Sources
Where evidence comes fromDatadog, Grafana, Prometheus, Loki, CloudWatch, New Relic, Sentry
Logs, metrics, traces, alerts, and change context
Manual window pull or automatic incident lookback
Collaboration
Where updates goSlack, Microsoft Teams, and email
Issue opened, progress, resolved, and weekly status updates
Private or broad delivery depending on provider and policy
Escalation And Ownership
Who should move nextPagerDuty and on-call context
Assignment-aware notifications
Incident lead, owner team, watchers, and escalation flow
Trust and control
Built to keep updates clear, useful, and easier to trust.
Relay helps teams share the right context, move faster during incidents, and keep a cleaner record after the work is done.
Share Updates Safely
Keep everyone aligned without oversharingDifferent audiences can follow the same incident without seeing more than they need.
Give stakeholders clear status without pasting raw technical detail
Share support-safe evidence snippets instead of unrestricted logs
Keep engineers and non-engineers in the same incident flow
Move Faster Under Pressure
Spend less time gathering contextRelay keeps the incident record, evidence, and updates together so teams can act sooner.
See the incident window, evidence status, and next steps in one place
Reduce context switching across chat, dashboards, and docs
Make it easier to hand work across support, ops, and engineering
Keep A Better Record
Close incidents with more clarityRelay preserves the important details teams usually lose during fast-moving incidents.
Keep ownership, updates, evidence, and resolution notes together
Make post-incident follow-up easier and less reconstructive
Give support teams clearer context when customers ask what happened
Pricing
Start small, keep the meter easy to understand.
Core Relay handles incident workflow and evidence retrieval. Hosted observability can be added when teams want a simpler telemetry path.
Free
For trying Relay with a small team
$0/mo
Core workflow only
Manual, API, and webhook intake
Timeline, roles, ownership, and safe summaries
Basic collaboration updates
Connected-source evidence pull
Manual incident windows up to 7 days back
Telemetry subject to source retention
Community support
Pro
For production teams that need speed and context
$20/mo
Core plan + advanced analysis
Everything in Free, plus:
Evidence pack auto-assembly
AI-assisted diagnosis on retrieved evidence
Admin support dashboard
Advanced role permissions and delivery controls
Weekly status and incident digest workflows
Priority support
Enterprise
For larger or regulated environments
Custom
Dedicated deployment and support options
Everything in Pro, plus:
SSO (SAML & OIDC)
Hosted observability add-on or dedicated tenancy
Custom retention and data boundaries
Audit logs & compliance
Private cloud deployment
Dedicated success manager
Custom integrations
99.99% SLA