illari vs Opsgenie
Facts checked 2026-09-21. Vendor pricing changes; verify before deciding.
Opsgenie Heartbeats do the same core job as illari: expect a check-in, alert when it's missing. The bigger question for anyone relying on it isn't the feature list. It's that Atlassian stopped selling Opsgenie in mid-2025 and is retiring it in 2027.
| Opsgenie | illari | |
|---|---|---|
| Product status | No new sales since June 2025. Support ends April 5, 2027; customers migrate to Jira Service Management | Actively developed |
| Model | Heartbeat check-in, fixed interval | Heartbeat + run content, cron-expression aware |
| Heartbeats available on | Standard and Enterprise plans only | Every plan, including free |
| Pricing | Per user: Standard ~$19.95/user/mo, Enterprise ~$31.90/user/mo | Flat $20/mo, monitors and seats not metered |
| Free tier | Up to 5 users, no Heartbeats | 25 monitors, Heartbeats included |
| Scheduling | Fixed interval (expect a ping every N minutes) | Full 5-field cron + IANA timezone, DST handled |
| Run content | Received or missed, no payload | Exit code, duration and metric anomaly, threshold rules, hung-run |
Confirm the current migration timeline on Atlassian's own pages before relying on any of this.
Where illari is different
- Not on a sunset clock. Opsgenie Heartbeats work today, but the product they live in is being retired. illari has no forced migration in front of it.
- Heartbeats aren't paywalled behind a per-user plan. Opsgenie only offers Heartbeats on Standard and up. illari includes check-in monitoring on the free tier.
- Real cron scheduling. Opsgenie expects a ping every fixed N minutes. illari takes an actual cron expression and an IANA timezone, so “weekdays at 06:15 Eastern” is a schedule, not an approximation.
- Checks on what the run reported, not just whether a ping arrived: exit code, a run far off its baseline, and threshold rules on numbers the job sends (
rows < 1,cost_usd > 5).
Where staying on Opsgenie is fine, for now
- You're already paying for a Standard seat. If Heartbeats are already included in a plan you're not dropping, there's no urgency to add a second tool before you have to.
- April 2027 is real but not close. There's runway to plan a migration deliberately instead of scrambling.
- You're deep in the Atlassian ecosystem. If Jira Service Management is where your incidents already live, moving on-call there when Opsgenie sunsets may be the simpler path, though its heartbeat-monitoring story isn't settled yet.
Opsgenie Heartbeats still work today, on a published end date with an unclear replacement. Pick something for missed-job detection that isn't also counting down.
Try illari
25 monitors free, $20/mo for everything, monitors not metered. One HTTP request from the job.