Opsgenie pricing and cost per user: every plan, the volume ladder and the 2027 shutdown date
Opsgenie prices on a nine band marginal ladder, so multiplying headcount by the headline rate gets the wrong answer for any team over 25. Put your numbers in and the calculator applies the bands correctly on all three plans.
Opsgenie plan cost calculator
LiveRates read from atlassian.com/software/opsgenie/pricing in September 2026, USD list. The ladder is applied marginally, which is Atlassian's own stated model. Only responder users are counted, because stakeholders do not count toward the per-user price. SMS overage, call minutes and extra phone numbers are not included here, and the Essentials figures use the plan card orientation rather than the swapped ladder headers, both of which are explained below.
How much does Opsgenie cost?
Opsgenie costs $0 for up to 5 users, then $9.45 per user per month on Essentials, $19.95 on Standard and $31.90 on Enterprise when you pay annually. On monthly billing those become $11.55, $24.15 and $38.50. Those are marginal rates on a nine band volume ladder, not flat prices, so a large team pays the top rate only on the users above each threshold. The context that matters more than any of these numbers: Opsgenie went off sale on 4 June 2025 and support ends on 5 April 2027, so nobody can buy it new today and every existing customer has a migration deadline. If you are pricing Opsgenie in 2026 you are really pricing what replaces it.
The short version
- Free
- $0, up to 5 users
- Essentials
- $9.45 per user a month annually, $11.55 monthly
- Standard
- $19.95 annually, $24.15 monthly
- Enterprise
- $31.90 annually, $38.50 monthly
- Support ends
- 5 April 2027, off sale since June 2025
Opsgenie is off sale, and support ends on 5 April 2027
This has to come before the price list, because it changes what the price list is for. Atlassian has been folding Opsgenie's alerting into the rest of its platform since 2018, and on 4 March 2025 it confirmed the product would be withdrawn. Anyone pricing Opsgenie today is either an existing customer working out what renewal costs, or someone comparing it to a replacement. Nobody can start a new subscription.
01
4 March 2025
Atlassian announces the end of Opsgenie
The direction is set. Opsgenie stops being a product with a roadmap and becomes a migration project with a deadline.
02
4 June 2025
End of sale
No new purchases or signups, from Atlassian or from any partner or reseller. Plan upgrades and downgrades stop on this date too, so an existing customer is frozen on whichever tier they were on.
03
October 2025
Bundled Opsgenie withdrawn
Teams whose Opsgenie arrived bundled with Jira Service Management lost it at this point rather than in 2027.
04
5 April 2027
End of support
The service stops. Until then existing customers can renew and can still buy additional seats, which is the only way to grow a team on a product that is off sale.
Atlassian points existing customers at Jira Service Management or Compass. That is a sensible path if Opsgenie was always an extension of your Jira workflow. It is a much less obvious one if you bought Opsgenie for the on-call rota and the alerting, because those are the parts that do not map cleanly onto a service desk. Atlassian publishes no migration pricing on the Opsgenie pricing page, so what the move actually costs a given team is not something we can state from the source, and we are not going to guess it.
Every Opsgenie plan and what it includes
Four tiers. The prices below are the first band of the volume ladder, which is what the plan cards advertise and what applies to your first 25 users. The feature counts come from parsing all 75 comparable rows of Atlassian's own matrix, reading a tick as the check-mark element the page actually uses rather than by eye.
| Plan | Annual | Monthly | Billed | Features | What it adds |
|---|---|---|---|---|---|
| Free | $0 | $0 | Up to 5 users | 21 of 75 | Unlimited alerts, email and push, 100 account-wide SMS a month with no voice, 1 routing rule, 3 month retention, community support |
| Essentials | $9.45 | $11.55 | Per user | 36 of 75 | Adds Jira integration, service status pages, 100 incidents a month, 5 postmortems a month, 6 month retention. SMS is metered and charged per notification |
| Standard | $19.95 | $24.15 | Per user | 62 of 75 | Adds heartbeat monitoring, SSO, unlimited SMS and voice, 100 routing rules, call routing, analytics, custom roles, 1 year retention |
| Enterprise | $31.90 | $38.50 | Per user | 75 of 75 | Adds incident command center, templates, free stakeholder seats, edge encryption, unlimited retention, 24/7 phone support |
The jump worth noticing is Essentials to Standard. It roughly doubles the per-user price and it is where 26 of the 75 features arrive, including every one of the analytics products, single sign-on, unlimited SMS and voice, and the routing rule limit going from 1 to 100. A single routing rule is a real constraint for any team with more than one service, and it is the sort of limit that pushes an upgrade long before the feature list does.
The Opsgenie volume ladder, and why it is not a flat per-user price
Atlassian's own wording is "the detailed table of marginal prices per each plan". Marginal means these bands behave like tax brackets: each rate applies only to the users inside that band. On Standard, user number 501 costs $5.25 a month while users 1 to 25 are still costing $19.95 each. If you multiply your whole headcount by a lower band rate you will understate the bill badly, and if you multiply it by the headline rate you will overstate it.
| Users in band | Essentials annual | Essentials monthly | Standard annual | Standard monthly | Enterprise annual | Enterprise monthly |
|---|---|---|---|---|---|---|
| 1 to 25 | $9.45 | $11.55 | $19.95 | $24.15 | $31.90 | $38.50 |
| 26 to 50 | $8.40 | $10.50 | $17.85 | $22.05 | $25.30 | $30.80 |
| 51 to 100 | $7.35 | $9.45 | $16.80 | $21.00 | $23.10 | $28.60 |
| 101 to 250 | $6.30 | $7.35 | $15.75 | $18.90 | $18.70 | $23.10 |
| 251 to 500 | $5.80 | $6.85 | $11.55 | $13.65 | $12.10 | $14.30 |
| 501 to 1,000 | $5.25 | $6.30 | $5.25 | $6.30 | $5.50 | $6.60 |
| 1,001 to 2,500 | $4.75 | $5.25 | $4.75 | $5.25 | $4.95 | $5.50 |
| 2,501 to 10,000 | $4.20 | $4.75 | $4.20 | $4.75 | $4.40 | $4.95 |
| 10,000 + | $3.70 | $4.20 | $3.70 | $4.20 | $3.85 | $4.40 |
Essentials figures follow the plan card, where annual is the cheaper number. Atlassian's Essentials ladder prints these two columns the other way round, which is covered in the next section.
Above 500 users, Essentials and Standard charge exactly the same marginal rate
This is the part of the price list that nobody writes about, and it falls straight out of the ladder once you line the columns up. In all four bands above 500 users, Essentials and Standard charge an identical marginal rate, on both billing terms. Annual it is $5.25, $4.75, $4.20 and $3.70 on both plans. Monthly it is $6.30, $5.25, $4.75 and $4.20 on both plans. Eight exact matches, not approximations.
The practical consequence is that the Standard premium stops growing at 500 people. Below that threshold Standard costs 2.1111 times Essentials, and every hire widens the gap in absolute dollars. Past it, every additional person costs the same on either plan, so the ratio between the two bills falls steadily: 2.1111 at 25 users, 1.6559 at 1,000, and 1.0861 at 10,000. A large organization pays almost nothing extra, proportionally, for the tier that carries heartbeat monitoring, SSO and the analytics suite.
Enterprise behaves the same way and the collapse is even sharper. It costs exactly 1.5990 times Standard for the first 25 users and 1.0684 times at 10,000. So the tier premiums in this price list are aimed squarely at small and mid-sized teams. If you are a 20 person team, choosing Standard over Essentials is a genuine budget decision worth arguing about. At 5,000 people it is a rounding error, and the only sensible answer is to take the higher tier.
Standard divided by Essentials
| Users | Essentials | Standard | Ratio |
|---|---|---|---|
| 25 | $236 | $499 | 2.11x |
| 100 | $814 | $1,785 | 2.19x |
| 500 | $3,209 | $7,035 | 2.19x |
| 1,000 | $5,834 | $9,660 | 1.66x |
| 2,500 | $12,959 | $16,785 | 1.30x |
| 10,000 | $44,459 | $48,285 | 1.09x |
Monthly cost at the annual contract rate, ladder applied marginally. Rounded to the dollar.
Atlassian's Essentials table contradicts its own Essentials plan card
We are flagging this rather than quietly picking a side, because a reader checking our numbers against the vendor page deserves to know why two sources disagree. The Essentials plan card says $9.45 per user per month billed annually, or $11.55 billed monthly. The Essentials volume ladder further down the same page puts $11.55 in the column headed "Monthly prices (Annual contract)" and $9.45 in the column headed "Monthly prices (Monthly contract)". Read literally, the ladder says annual billing costs more.
Two things settle which reading is right. First, the Standard and Enterprise ladders carry the identical pair of column headers and are the right way round, matching their own cards at $19.95 against $24.15 and $31.90 against $38.50. Only Essentials is reversed. Second, the discount arithmetic gives it away: taking the card as correct, the annual saving is 18.18 percent on Essentials, 17.39 on Standard and 17.14 on Enterprise, which is a coherent set. Taking the ladder as correct would mean annual billing costs 22 percent more than monthly on one plan and 17 percent less on the other two.
The swap is consistent across all nine Essentials rows rather than appearing in a single cell, which is what you would expect from two column headings in the wrong order rather than a mistyped figure. So we publish the card orientation, annual $9.45 and monthly $11.55, throughout this page and in the calculator. If you are budgeting from Atlassian's ladder directly, check which column you are reading before you sign anything, because the difference on a 100 person Essentials team is about $12,600 a year.
Annual discount, card orientation
| Plan | Annual | Monthly | Saving |
|---|---|---|---|
| Essentials | $9.45 | $11.55 | 18.18% |
| Standard | $19.95 | $24.15 | 17.39% |
| Enterprise | $31.90 | $38.50 | 17.14% |
A coherent set. The ladder reading would make Essentials the only plan in the market where paying up front costs more.
What each Opsgenie tier actually unlocks
Eight rows from the 75 row matrix that decide most upgrades. The one to look at hardest if you are a small team is heartbeat monitoring, because it sits behind the $19.95 tier and it is the feature most often bought for its own sake.
| Feature | Free | Essentials | Standard | Enterprise | Notes |
|---|---|---|---|---|---|
| Heartbeat and cron job monitoring | No | No | Yes | Yes | Passive monitoring that alerts when a scheduled job stops checking in. Gated to Standard, so cron monitoring alone costs $19.95 per user per month |
| Single sign-on | No | No | Yes | Yes | Standard and above only |
| Service status pages | No | Yes | Yes | Yes | Available from Essentials up, which is unusually generous for this market |
| Unlimited SMS and voice | No | No | Yes | Yes | Essentials meters SMS and bills overage per notification. Standard and Enterprise do not |
| Routing rules | No | No | Yes | Yes | Free and Essentials allow exactly 1 rule. Standard and Enterprise allow 100 |
| On-call and efficiency analytics | No | No | Yes | Yes | All four analytics products start at Standard |
| Incident command center and templates | No | No | No | Yes | Enterprise only |
| Free stakeholder seats | No | No | No | Yes | Stakeholders are read-only users. They are free and included on Enterprise only, and only responder users count toward the per-user price |
Worth crediting Atlassian on one row: service status pages start on Essentials, not on the top tier. That is more generous than most of this market, where a status page is either an add-on or an enterprise feature. We track what the rest of the category charges for the same thing in our status page pricing comparison, and PagerDuty by contrast sells its page as an add-on from $89 per 1,000 subscribers a month.
The metered charges that sit on top of the per-user price
Opsgenie's per-user rate is not the whole invoice on Essentials. SMS and voice are metered there and billed per notification once the allowance runs out, while Standard and Enterprise include them without a published cap. That is a real difference in how predictable your bill is, and it matters most for teams that page people at night.
| Item | Essentials | Standard and Enterprise | Notes |
|---|---|---|---|
| Additional SMS or voice, US and Canada | $0.10 per notification | Free | Essentials includes users x 100 a month, then charges |
| Additional SMS or voice, international | $0.35 per notification | Free | Essentials includes users x 25 a month, then charges |
| Extra incoming phone number | Not available | $10 a month each | One number is included on Standard and Enterprise |
| Incoming call minutes, US and Canada | Not available | $0.10 per minute | 100 minutes included on Standard and Enterprise |
| Incoming call minutes, international | Not available | $0.35 per minute | No included international allowance |
| Data retention | 6 months | 1 year | Free is 3 months, Enterprise is unlimited |
One caveat Atlassian states openly and we will repeat: there is no preset limit on SMS and voice for Standard and Enterprise, but the page reserves the right to move a customer onto a usage-based plan if international volume looks abnormal. So "unlimited" here means uncapped in normal use rather than contractually unlimited.
Opsgenie never ran the check that finds the outage
This is the thing most price comparisons skip, and it decides whether the number above is your whole bill or half of it. Opsgenie is alerting and on-call: it takes an event from somewhere else and makes sure the right person's phone rings. It does not test whether your site, your API or your certificate is actually reachable.
Its heartbeat feature is the closest thing to monitoring in the product, and it is deliberately passive. Atlassian's own tooltip describes it as ensuring alerting works end to end by watching for systems that stop reporting in, and it notifies you when it does not hear from them in a set interval. That catches a dead cron job or a broken alert pipeline. It cannot tell you that your checkout page started returning a 500 to customers, because nothing in Opsgenie ever requests your checkout page.
So a team that bought Opsgenie to find out about downtime was always paying for two subscriptions: Opsgenie for the rota, and something underneath it doing the checking. If you are replacing Opsgenie before April 2027, that is worth revisiting rather than reproducing out of habit. Plenty of teams discover the monitoring tool they already pay for does the alerting they were buying separately.
Cost of cron monitoring alone
Heartbeat monitoring is gated to Standard, so a team that wants alerts when a scheduled job stops checking in has to buy the $19.95 tier for everyone who needs a login.
- 5 people on Standard
- $99.75 a month, $1,197 a year
- 10 people on Standard
- $199.50 a month, $2,394 a year
- 25 people on Standard
- $498.75 a month, $5,985 a year
Our own cron and heartbeat monitoring is priced per monitor and does not meter logins, so the same job does not get more expensive as the team grows.
Opsgenie pricing questions people actually ask
How much does Opsgenie cost?
Opsgenie costs $0 for up to 5 users, then $9.45 per user per month on Essentials, $19.95 on Standard and $31.90 on Enterprise at the annual rate. Monthly billing is $11.55, $24.15 and $38.50. A ten person team on Standard therefore pays $199.50 a month, or $2,394 a year, at the published annual rate.
Is Opsgenie being discontinued?
Yes. Atlassian announced on 4 March 2025 that Opsgenie would be withdrawn. It went off sale on 4 June 2025 and support ends on 5 April 2027. Existing customers can keep using it and can still renew and add seats until that date, but nobody can start a new subscription, and plan upgrades and downgrades stopped at the end of sale.
Can you still buy Opsgenie in 2026?
No. End of sale was 4 June 2025 and it applies to purchases from Atlassian directly and from every partner and reseller. If you are reading a price list for Opsgenie today and you are not already a customer, the practical answer is that these prices are historical. What you can still do as an existing customer is renew and buy extra seats on the tier you are already on.
What is Opsgenie cost per user?
It depends on team size, because the ladder is marginal rather than flat. The first 25 users cost $19.95 each on Standard at the annual rate, users 26 to 50 cost $17.85 each, and so on down nine bands to $3.70 above 10,000. So a 100 person team pays $1,785 a month, which is an effective $17.85 per user rather than the $19.95 headline.
Does Opsgenie pricing work like tax brackets?
Yes, and this is the single most misread thing about it. Atlassian describes the ladder as "marginal prices per each plan", which means each band applies only to the users inside it. On Standard, user number 501 costs $5.25 while users 1 to 25 still cost $19.95 each. Multiplying your whole headcount by the lowest band rate will understate the bill by a wide margin.
Why does the Opsgenie Essentials table show annual costing more than monthly?
Because the two column headers on the Essentials ladder appear to be swapped. The Essentials plan card says $9.45 billed annually and $11.55 billed monthly, while the ladder underneath prints $11.55 under "Annual contract" and $9.45 under "Monthly contract". The Standard and Enterprise ladders use the same two headers the right way round. Treat the card as correct: annual is the cheaper number on every plan.
Is Opsgenie Standard worth it over Essentials?
Below about 500 users Standard costs roughly 2.1 times Essentials, and what you buy is heartbeat monitoring, SSO, unlimited SMS and voice, 100 routing rules instead of 1, and the analytics suite. Above 500 users the question changes completely, because the two plans charge the identical marginal rate in every remaining band, so the extra features stop getting more expensive as you grow.
Does Opsgenie include heartbeat or cron job monitoring?
Only on Standard and Enterprise. Heartbeat monitoring is not on the Free or Essentials tiers, so a team that wants alerting when a scheduled job stops checking in has to be on at least the $19.95 per user plan. For a team of ten that is $2,394 a year for the tier, which is a lot of money for cron monitoring if it is the main thing you need.
Does Opsgenie monitor your website?
No. Opsgenie receives alerts from other systems and routes them to the right person on the rota. It does not check whether your site, API or certificate is reachable. Its heartbeat feature is passive, meaning it alerts when something stops reporting in, rather than actively testing an endpoint. So the real cost of knowing your site is down is Opsgenie plus whatever runs the checks.
How many users does the Opsgenie free plan allow?
Five. The free tier covers up to 5 users with unlimited alerts, unlimited email and mobile push, 100 account-wide SMS notifications a month with no voice calls, one routing rule and three months of data retention. It carries 21 of the 75 features on the comparison matrix. Support is community only.
Replacing Opsgenie? Start with what actually detects the outage
We check your sites, APIs, ports and cron jobs from six regions with auto-retry, then alert the right channel in seconds. Priced per monitor and never per seat, so migrating a team of thirty does not mean thirty licences, and a branded status page is in every plan.
More monitoring price lists, taken apart the same way
PagerDuty pricing
The other big on-call platform, where the free plan holds five users and the sixth costs $1,512 in year one.
Opsgenie vs PagerDuty pricing
Both price lists side by side at seven team sizes, and why the cheaper sticker is not the cheaper bill for a small team.
Hyperping pricing
The one vendor whose seat price rises as you climb, so Pro is never the cheaper plan for people at any team size.
Monitoring cost per user
Ten vendors and what each extra login costs, from $0 to $41 a month. The meter that decides most bills at year two.
Cron and heartbeat monitoring
The feature Opsgenie gates behind its $19.95 tier, priced per monitor instead of per person.
Uptime monitoring pricing compared
Every major vendor in one table, sorted by billing model, because the model decides the bill more than the sticker does.