Jira Service Management plans and prices
| Plan | Monthly list price | Agents | What Atlassian lists |
|---|---|---|---|
| Free | 0 USD | Up to 3 | Alerts, on-call schedules and an incident template, request portal, forms, workflows, queues, 1,250 automation steps a month |
| Standard | 21.50 USD per agent | Up to 100,000 | Everything in Free plus asset and configuration management, custom branded help center, audit logs, multi-region data residency, 3,000 automation steps per user a month |
| Premium | 55.28 USD per agent | Up to 100,000 | Everything in Standard plus advanced asset management, a virtual service agent and AIOps capabilities |
| Enterprise | Quote, annual billing only | Large organizations | Everything in Premium plus advanced data analysis and enterprise scale and security |
Source: the Jira Service Management pricing page, read in October 2026 with monthly billing selected. Atlassian shows annual billing as saving up to 17 percent and takes quotes for Enterprise only. Prices on the page change with currency and the number of agents you enter, so confirm in the calculator before you budget.
Why other sites show different Jira Service Management prices
Pricing guides quote about 20 USD for Standard and about 47 to 53 USD for Premium, because they were written at earlier list prices or for annual billing. Atlassian's own page is the one to budget from, and it is also moving, since Jira Service Management is now sold inside Atlassian bundles. Ask for a written quote that names the plan, the agent count and the billing term.
Who counts as a Jira Service Management agent
An agent is a licensed user who works on requests and alerts. Customers who raise requests through the portal are unlicensed and free. For an engineering rotation that means everyone who acknowledges, escalates or resolves an alert needs a seat. If your on-call group is 15 engineers, you pay for 15 agents even though most of your Jira users never touch the service desk.
The Free plan stops at 3 agents. A rotation needs at least two or three people per shift and cover for holidays, so most teams outgrow Free the week they set up a real schedule.
What does Jira Service Management cost for 5, 15 and 40 agents?
Monthly cost at list price with every agent on call. JSM rows use the monthly rates above, IncidentBot rows use annual billing, and the last column is IncidentBot with a free read-only seat for each stakeholder.
| Setup | 5 agents | 15 agents | 40 agents |
|---|---|---|---|
| Jira Service Management Free | Not available | Not available | Not available |
| Jira Service Management Standard | 107.50 USD | 322.50 USD | 860.00 USD |
| Jira Service Management Premium | 276.40 USD | 829.20 USD | 2,211.20 USD |
| IncidentBot Starter (1 public status page) | 120 USD | 360 USD | 960 USD |
| IncidentBot Team (3 status pages, incident roles, Jira sync) | 245 USD | 735 USD | 1,960 USD |
Read it honestly. Standard is cheaper than IncidentBot Starter at every size, and if your team already runs a service desk in Jira, adding on-call agents to it is the lowest cost path. The numbers change when you want an incident room in Slack, a customer status page and a drafted postmortem as part of the same purchase, because those are not what the JSM plan list above sells. Premium costs more than IncidentBot Team from 5 agents up.
Where the Jira Service Management bill grows
- Every responder is an agent. Developers who only join incidents still need a license to work alerts.
- Premium for AIOps. Alert grouping and AI help are Premium features, so the price per seat more than doubles.
- Monthly against annual. The 17 percent annual saving needs a year commitment, and Enterprise is annual only.
- Jira is the home. Teams that plan in Jira Software but do not run a service desk pay for service desk features they never open.
- A status page and Slack incident flow are separate decisions from the plan list, so check what covers them before you count the total.
Is Jira Service Management enough, or do you need an incident tool?
JSM is a service desk that gained alerting. It fits IT teams that live in Jira, take requests from employees and treat incidents as one queue among many. Engineering teams that live in Slack tend to want the opposite: the alert starts a channel, a commander is named, customers see a status page, and the postmortem comes from the timeline.
| What you need | Jira Service Management | IncidentBot |
|---|---|---|
| Alerts, on-call schedules, escalation | Included from Free for 3 agents | Starter and Team |
| Request portal and employee service desk | Core product | Not offered |
| Slack incident channel with roles | Not part of the plan list above | /incident channel on Starter, commander, comms and scribe roles on Team |
| Customer status page | Not part of the plan list above | 1 public page on Starter, 3 public or private pages with subscribers on Team |
| Postmortem drafted from the timeline | Not part of the plan list above | Team, with action items synced to Jira and Linear |
| People who only follow incidents | Unlicensed customers only | Free read-only viewers on every plan |
JSM wins for a Jira-centric IT service desk, for asset management and for teams that want one vendor for requests and alerts. IncidentBot is the better buy when an outage involves more people than the rotation and the work happens in Slack. If you are leaving Opsgenie but stay on Jira Software, the Opsgenie replacement for Jira teams page prices that move with the Jira sync included.
Whichever tool you choose, treat the renewal as a contract. If you manage vendor terms in one place, contract management software keeps the agent count, renewal date and notice period together so a seat true-up does not surprise you.
What to ask Atlassian before you sign
- Is the quote for the plan, agent count and billing term I need, and what is the price at renewal?
- Do on-call engineers who only resolve alerts need a paid agent license?
- Which features that I need sit on Premium and not on Standard?
- What changes for Opsgenie customers on the April 5, 2027 shutdown date, and is migration support included?
- What does a status page and a Slack incident flow cost on top of the plan?
Put the same questions to every vendor on your shortlist. The Opsgenie pricing breakdown and the PagerDuty alternative comparison show the same table for the other common choices.
How much does Jira Service Management cost?
Jira Service Management costs 0 USD for up to 3 agents, 21.50 USD per agent a month on Standard and 55.28 USD per agent a month on Premium at monthly billing, according to Atlassian's pricing page. Annual billing saves up to 17 percent. Enterprise is annual only and quoted by sales.
Is Jira Service Management free?
Yes, up to 3 agents. The Free plan includes alerts, on-call schedules and escalation policies, a request portal, forms, workflows and 1,250 automation steps a month. It does not include asset management, audit logs or the Standard automation allowance, and a real rotation usually has more than 3 responders.
Does Jira Service Management include on-call scheduling?
Yes. Atlassian lists alerts with routing rules, escalation policies and on-call schedules on the Free plan, and the paid plans build on it. This is the capability Atlassian is moving Opsgenie customers toward before Opsgenie access ends on April 5, 2027.
What is the difference between Standard and Premium?
Standard adds asset and configuration management, a branded help center, audit logs and data residency. Premium adds advanced asset management, a virtual service agent and AIOps capabilities for 55.28 USD instead of 21.50 USD per agent. Teams that only need paging rarely need Premium.
Does a customer count as a Jira Service Management agent?
No. Customers who raise requests through the portal are unlicensed and not billed. Agents are the licensed users who work requests and alerts, so every on-call engineer who acknowledges or resolves alerts counts.
What is a good Jira Service Management alternative for on-call teams?
For engineering teams that run incidents in Slack, IncidentBot covers paging, schedules, escalation, the incident channel, a status page and postmortems from 24 USD per seat billed annually, with read-only viewers free. Action items sync to Jira on Team, so the Jira backlog stays the source of truth.
Price your rotation with the status page and readers included
Run a sample incident with an escalation policy and a status update, then create your account and point one alert source at IncidentBot.