Atlassian announces end of support for Opsgenie

Original Article ↗ Hacker News Discussion ↗

Nature of the change (shutdown vs “repackaging”)

  • Some see this as more than pricing/branding: Opsgenie as a standalone product is being ended, with APIs expected to stop working by April 2027.
  • Others stress that end-of-support is years away and that Atlassian is offering a long migration window, so the headline feels over-dramatic.
  • Confusion exists because the announcement language emphasizes “evolution” and migration options (Jira Service Management, Compass), not a clear “we’re shutting this down.”

Migration paths, product fit, and customer experience

  • Many commenters say Jira Service Management (JSM) and Compass are not feature-complete or one-to-one replacements; migration is described as painful, especially for complex schedules, escalation policies, and integrations.
  • A few report smooth migrations to JSM with rules auto-transferred and Opsgenie made read-only.
  • Several users say they received warnings and deprecation nudges for months; others (including large customers) say they first learned from the public blog post and saw no in-app notice, calling this a trust breaker for a mission-critical tool.
  • Atlassian’s product sprawl (multiple Jira variants, unclear admin dashboards, noisy/irrelevant Opsgenie notifications) is cited as confusing and possibly revenue-driven.

Reliability, criticality, and past behavior

  • Commenters recall a 2022 incident where Opsgenie was reportedly down for ~2 weeks for some customers during a broader Atlassian outage, seen as evidence Atlassian underestimates how critical paging infrastructure is.
  • Slow maintenance (e.g., a trivial SDK PR taking 9 months) is used to argue support had effectively been “over” for a while.
  • Some speculate Atlassian prioritizes higher-revenue products, effectively zeroing out value for affected Opsgenie users.

Alternatives and market dynamics

  • Thread is full of founders and users promoting or recommending alternatives: incident.io, Rootly, Better Stack, ilert, All Quiet, PagerTree, Zenduty, Temperstack, TaskCall, Pushover, and various open-source/self-hosted options.
  • There’s strong demand for: reasonable pricing for small teams, Terraform support, EU hosting and local phone numbers, and simple but reliable alerting.
  • Multiple people criticize stagnation at incumbents like PagerDuty/Opsgenie (UI pain, rigid overrides, slow innovation), seeing this as why so many startups target this space.
  • Self-hosting alerting is debated: some like the control; others call it “madness” and question who alerts you if your own alerting stack fails.
  • “AI-native” positioning in incident tools draws skepticism, especially around AI silencing or closing incidents; some accept AI for documentation/postmortems but not core alerting decisions.

Atlassian, acquisitions, and consolidation

  • Atlassian is criticized for mediocre integration of acquisitions and poor offboarding (e.g., Bitbucket/Mercurial).
  • Some note it’s surprising to buy Opsgenie for ~$295M then end it in ~6 years; others, including someone involved in the acquisition, say Opsgenie always should have become a feature inside JSM and that industry is swinging from “feature-as-product” back to consolidation.

Broader tooling and project management tangents

  • Discussion drifts into Jira alternatives (Linear, GitHub/GitLab issues, Asana, Fibery, even Trac) and ultra-low-tech solutions (whiteboards and sticky notes) that teams report surprisingly liking despite scaling issues.
  • Meta-comment: the high number of self-promotional posts is seen as evidence both of dissatisfaction with incumbents and of how hot the incident-management niche is.