Free on-call
Every customer request is triaged the moment it arrives.
Customer reports, tickets and alerts land in one place. NOFire AI checks what changed, what it affects and who owns it, before anyone is paged. Schedules, escalations and paging by Slack, push, SMS, phone and email, free for up to 15 users.
What's included
Everything on-call needs, from day one.
Rotations across time zones, escalations that move on when nobody answers, and routing that sends each alert to the team that owns it. Paged by Slack, push, SMS, phone or email.
Opsgenie migration
Migrate from Opsgenie in one step.
Atlassian shuts Opsgenie down on April 5, 2027, and deletes the data you don't move. Bring it all across and get paged the same way from day one.
- Teams, users and contact methods
- Schedules and overrides
- Escalation policies and routing rules
- Alert integrations and alert history
Reliability
A pager built like a distributed system.
Every page is a durable workflow on Temporal. Kill a worker mid-escalation and the page resumes from the exact step.
- Escalations always fire. Timers survive deploys and restarts.
- Retried until someone acks. Failed sends back off and move to the next channel.
- No race on ack. Escalation stops the moment someone takes the page.
SOC 2 evidence
Evidence for your SOC 2 audit, as you work.
Every page, acknowledgement and handoff is recorded with who and when. When the auditor asks how you respond to incidents, the answer is already written down.
- Mapped to the criteria auditors check. Evidence is grouped under CC7.3 to CC7.5, the SOC 2 criteria for detecting, responding to and recovering from incidents.
- Export a report in one click. Download a PDF your auditor can read.
- Nothing to collect by hand. No screenshots or spreadsheets before the audit. The record builds while your team works.
Free
Free for up to 15 users.
The full pager for teams of up to 15: schedules, escalations and every channel. No card, no trial that runs out.
Paging is half of on-call.
The other half is what happens next. See how your Level 1 and Level 2 teams get from the alert to the cause.
Frequently asked questions.
Is it GDPR compliant?
Yes. Your data can stay in the EU, and we sign a data processing agreement (DPA) with every customer that needs one.
Can we run it next to our current pager?
Yes. Send the same alerts to both for a week or two, compare who got paged alert by alert, and switch when they match.
What about our Opsgenie alert history?
It comes across with everything else: teams, schedules, escalation policies and your alert history. Import it before April 5, 2027, because Atlassian deletes it after that.
Can we import from other pagers?
Yes. Teams, schedules, escalation policies and alert history come across in one step from PagerDuty, incident.io, Grafana OnCall and Splunk On-Call, the same way as from Opsgenie.
What counts as a user?
Anyone who can be put on a schedule or paged. People who only view incidents don't count.
Can we export our data?
Yes. Schedules, escalation policies and the full page history can be exported at any time, through the API or as CSV. Nothing is locked in.
Can engineers swap shifts or cover for each other?
Yes. Overrides and swaps change who's on call for a set time without editing the schedule.
Which tools can send alerts?
Any monitoring tool that can send a webhook or an email, including Datadog, Grafana, Prometheus Alertmanager and CloudWatch.