Jira Service Management pricing in 2027: what you'll actually pay
What JSM really costs in 2027: per-agent rates after the October 2026 increase, the December 3 AI usage meters, sample bills and the Data Center deadlines.

Key takeaways
- Standard costs $26.90 per agent per month for agents 1 to 15 and $20.15 for agents 16 to 100 on monthly billing; a 50-agent team pays about $1,109 a month.
- Premium costs $61.60 per agent per month for agents 1 to 15 and $53.70 for agents 16 to 100; a 50-agent team pays about $2,804 a month. Enterprise is quote only.
- Seat prices rose 7.5 percent on Standard and Premium and 10 percent on Enterprise on October 13, 2026.
- From December 3, 2026, usage above your allowance bills automatically: $0.01 per Rovo credit and $0.50 per 1,000 automation steps, with extra usage on by default.
- JSM Data Center stops selling expansions on March 30, 2028 and goes read-only on March 28, 2029.
Jira Service Management pricing changed twice in fall 2026, and both changes land in 2027 budgets. On October 13, 2026, Atlassian raised the list price of Jira Service Management (JSM) seats by about 7.5 percent. And from December 3, 2026, AI usage, automation steps and asset records above your plan's allowance bill by usage, on top of the seat price.
So planning a 2027 JSM budget now takes two calculations instead of one. The first is the seat bill, which is easy to predict. The second is the usage bill, which depends on how much your agents and employees lean on AI. This guide walks through both, with current per-agent rates, worked monthly bills for 10, 50 and 100 agents, the meters that now carry a price, and the Data Center deadlines that make 2027 a decision year for on-premises customers.
One naming note before the numbers. JSM is now sold only inside Atlassian's Service Collection, a bundle of Jira Service Management, Customer Service Management, Assets and Rovo. When you search for JSM pricing today, you land on Service Collection pricing. The two terms mean the same price list. And "Jira pricing," around $9.70 per user, is Jira (formerly Jira Software), the developer product, which isn't what a service desk buys.
What changed in JSM pricing, and when each change hits you
Three separate changes make up 2027 JSM pricing: an October 13, 2026 seat price increase, December 3, 2026 usage billing, and the Data Center end-of-life schedule that runs to March 28, 2029. They're on different calendars, so it helps to treat them separately.
| Date | What changes | Who it affects |
|---|---|---|
| March 30, 2026 | Data Center stops selling to new customers | Organizations that never owned Data Center |
| October 13, 2026 | Seat prices rise 7.5 percent (Enterprise 10 percent) | Monthly plans from the next bill; annual plans at the next renewal or quote |
| December 3, 2026 | Usage billing starts for Rovo credits and automation steps | Every cloud customer whose usage exceeds the included allowance |
| March 30, 2028 | Data Center expansions, upgrades and new apps end | Existing Data Center customers |
| March 28, 2029 | Data Center goes read-only | Existing Data Center customers |
Change 1: seat prices rose on October 13, 2026
Atlassian raised Service Collection list prices, which includes JSM, by 7.5 percent on the Standard and Premium plans and 10 percent on Enterprise. The new prices took effect on October 13, 2026. On Atlassian Government Cloud, JSM rose 10 percent.
| Plan | Change | Before (agents 1 to 15, monthly) | After (agents 1 to 15, monthly) |
|---|---|---|---|
| Standard | +7.5% | $25.00 per agent | $26.90 per agent |
| Premium | +7.5% | $57.30 per agent | $61.60 per agent |
| Enterprise | +10% | Quote only | Quote only |
When you actually pay the new price depends on how you're billed:
- Monthly subscriptions: any bill dated on or after October 13, 2026 uses the new price. That's already happened.
- Annual subscriptions: any quote generated or modified on or after October 13, 2026 uses the new price, so the increase reaches you at your next renewal. For most annual customers, that's somewhere in 2027.
- New purchases, plan upgrades and user-tier upgrades: new price from October 13, 2026.
Customers coming off multi-year deals or discounted renewals can see a larger jump than 7.5 percent, because renewals are re-quoted from the new list price.
Change 2: AI and automation bill by usage from December 3, 2026
Atlassian announced on September 1, 2026 that several meters would start billing above your included allowance on December 3, 2026. For JSM buyers, the ones that matter are Rovo credits (AI), automation steps, and Assets objects. Extra usage is switched on by default, so usage above the allowance bills automatically unless an admin sets a cap or turns it off. The next section explains each meter.
Change 3: Data Center is on a fixed path to read-only
If you run JSM Data Center (on-premises), these dates set your timeline:
- March 30, 2026: new customers can no longer buy Data Center licenses. This date has passed.
- March 30, 2028: existing customers can no longer buy new Data Center subscriptions, expansions, upgrades or Marketplace apps.
- March 28, 2029: Data Center licenses expire and products go read-only.
A migration usually takes many months to plan, test and run, so for most Data Center teams the real decision happens in 2027. We cover what that means for your budget further down.
Discounts still apply
Atlassian offers Service Collection cloud at 50 percent off for eligible academic institutions and 75 percent off for eligible Community (nonprofit) customers. If you're in higher education or a nonprofit, apply those percentages to every seat figure in this guide. Usage meters are billed separately from the seat discount, so check how your discount treats them.
JSM plans and prices for 2027, and what each one includes
JSM has four plans: Free for up to 3 agents, Standard, Premium, and Enterprise (quote only). You pay per agent, meaning anyone who works tickets. Employees and customers who only submit requests are free and unlimited.
| Feature | Free | Standard | Premium | Enterprise |
|---|---|---|---|---|
| Monthly price, agents 1 to 15 | $0 (max 3 agents) | $26.90 per agent | $61.60 per agent | Annual quote only |
| Monthly price, agents 16 to 100 | n/a | $20.15 per agent | $53.70 per agent | Annual quote only |
| Rovo AI credits included | None | 250 per agent per month | 700 per agent per month | 1,500 per agent per month |
| Automation steps included | 1,250 per site per month | 3,000 per agent per month | 6,500 per agent per month | 9,500 per agent per month |
| Assets objects included | None | 5,000 | 50,000 | 500,000 |
| Virtual service agent | No | No | Yes, 1,000 conversations per month included | Yes, 1,000 conversations per month included |
| Change management | No | No | Yes | Yes |
| Uptime SLA and support | Community support | No financially backed SLA listed | 99.9% SLA, 24/7 Premium Support | 99.95% SLA |
How the per-agent price really works
Monthly pricing is progressive: each agent is priced by the band it falls into. Your first 15 agents cost the band-one rate, agents 16 to 100 cost the band-two rate, and rates keep stepping down above 100. That's why Atlassian's pricing page shows a different "per agent" figure depending on the team size its calculator defaults to. A 100-agent Standard team pays an average of about $21.16 per agent. A 10-agent team pays the full $26.90.
Annual billing works differently. You buy a band of agents, not an exact headcount, and Atlassian says annual can save up to 17 percent. On Standard, the annual list price for 50 agents moved from $10,300 to $11,000, and for 100 agents from $19,700 to $21,000.
One monthly billing detail catches teams out. Atlassian bills monthly subscriptions on the highest number of seats assigned during the cycle. If you add contractors mid-month and remove them a week later, you still pay for the peak.
What's included in every paid plan
- Request, incident and service request management, with queues, SLAs and forms
- A help center portal plus email, Microsoft Teams and Slack request channels
- Customer Service Management (CSM), the external-support app, at no extra seat cost
- Assets for asset and configuration management, up to your plan's object allowance
- Rovo search, chat and agents, up to your plan's credit allowance
- An embedded knowledge base
What's not included, or costs extra
- AI usage above your Rovo credit pool: $0.01 per credit from December 3, 2026.
- Automation above your step allowance: $0.50 per 1,000 steps.
- Assets above your object allowance: from $0.02 per object per month.
- Virtual service agent conversations above 1,000 a month (Premium and Enterprise): from $0.30 per assisted conversation.
- CSM AI agent resolutions: $1.00 each, with no included allowance. This applies to external customer support, not internal employee requests.
- Advanced knowledge features: page permissions, advanced analytics and similar features need a paid Confluence plan.
- SAML single sign-on and directory sync on Standard and Premium: these need an Atlassian Guard subscription. Enterprise includes Guard Standard.
- Marketplace apps: priced separately per app, and commonly a meaningful share of total cost.
The JSM usage meters: Rovo credits, automation steps and Assets
From December 3, 2026, JSM usage above your plan's allowance bills automatically: $0.01 per Rovo credit, $0.50 per 1,000 automation steps, and from $0.02 per Assets object per month. The seat price buys an allowance, and anything above that allowance is a separate line on your invoice.
| Meter | What counts | Included (Standard / Premium / Enterprise) | Price above allowance |
|---|---|---|---|
| Rovo credits | AI actions: chat messages, agent runs, help center AI answers, enriched data calls from outside AI tools | 250 / 700 / 1,500 per agent per month, pooled | $0.01 per credit ($10 per 1,000) |
| Automation steps | Every trigger, condition, action, branch and loop that runs | 3,000 / 6,500 / 9,500 per agent per month, pooled | $0.50 per 1,000 steps |
| Assets objects | Each asset or configuration record stored | 5,000 / 50,000 / 500,000 per site | From $0.02 per object per month |
| Virtual service agent conversations | Conversations matched to an intent, or answered by AI and closed | Premium and Enterprise: 1,000 per month | From $0.30 per conversation |
| CSM AI agent resolutions | External customer inquiries the AI resolves with no human handoff | None | $1.00 per resolution |
How Rovo credits are spent
Rovo credits are the meter most JSM teams will notice first, because AI now sits in the agent workspace and the help center. Atlassian sorts AI actions into three price levels:
- Free: Rovo Search, definitions and summaries inside Atlassian apps.
- Basic, 10 credits per action: Rovo Chat quick answers, workforce management routing in JSM, and basic Rovo agents.
- Premium, variable credits per action: advanced Rovo agents, Rovo Chat in "think deeper" mode, Request Resolver, Alert Intelligence, and the Self-service Agent that answers employees in your help center. Credits vary with how much reasoning, searching and tool use a request needs.
That last group matters most for a service desk. The AI features that answer employees and resolve requests on their own are exactly the ones priced at the variable, higher level.
Rules worth knowing before your first metered month
- Credits pool across your organization. A 50-agent Standard team gets one shared pool of 12,500 credits a month, not 250 per person. Heavy users draw down everyone's allowance.
- Allowances reset monthly and don't roll over. The reset falls on your usage billing date, which isn't necessarily the first of the month.
- Extra usage is on by default. Admins get alerts at 80 and 100 percent of the allowance. If an admin turns extra usage off, AI features pause until the reset. Turning off automation extra usage stops automation rules from running until the reset, too.
- Outside AI tools draw on the pool. When tools like ChatGPT or Claude pull context from your Atlassian data through Atlassian's MCP server or Teamwork Graph, enriched calls cost about 1 to 10 credits each.
- The $1 resolution fee is for external support. If you use JSM for internal IT and HR requests, your AI cost runs through Rovo credits and, on Premium, virtual service agent conversations. The $1 per resolution fee applies to Customer Service Management's AI agent for external customers.
How much does Jira Service Management cost? Sample bills for 10, 50 and 100 agents
On monthly billing in 2027, a 10-agent JSM Standard desk costs $269 a month, a 50-agent desk costs $1,108.75, and a 100-agent desk costs $2,116.25, before any usage charges. Premium costs roughly 2.3 to 2.6 times as much, depending on team size. These figures use Atlassian's published progressive rates: $26.90 and $20.15 per agent on Standard, and $61.60 and $53.70 on Premium.
Step 1: the seat bill
| Agents | Standard per month (before Oct 13, 2026 → now) | Standard average per agent | Premium per month (before → now) | Premium average per agent |
|---|---|---|---|---|
| 10 | $250.00 → $269.00 | $26.90 | $573.00 → $616.00 | $61.60 |
| 50 | $1,031.25 → $1,108.75 | $22.18 | $2,607.75 → $2,803.50 | $56.07 |
| 100 | $1,968.75 → $2,116.25 | $21.16 | $5,105.25 → $5,488.50 | $54.89 |
Here's the math for 50 agents on Standard: 15 agents × $26.90 = $403.50, plus 35 agents × $20.15 = $705.25, for a total of $1,108.75 a month. That's $77.50 more each month than before October 13, or $930 more a year.
Annual billing brings the seat bill down. Twelve monthly bills for 50 Standard agents add up to $13,305, against an annual list price of $11,000. For 100 agents, it's $25,395 against $21,000. Both work out to roughly 17 percent saved for committing to a year.
Step 2: the usage bill
The seat bill is predictable, but the usage bill depends on behavior. Take a 50-agent Standard desk with a pooled allowance of 12,500 Rovo credits a month. Say employees have 2,000 conversations a month with the help center's Self-service Agent, and agents use about 5,000 credits of their own on chat and summaries.
The Self-service Agent bills variable credits, so we can't give one exact cost per conversation. The table shows the result at three illustrative averages:
| If each help center conversation averages | Credits used per month | Credits above the 12,500 pool | Extra cost per month | Extra cost per year |
|---|---|---|---|---|
| 10 credits | 25,000 | 12,500 | $125 | $1,500 |
| 25 credits | 55,000 | 42,500 | $425 | $5,100 |
| 50 credits | 105,000 | 92,500 | $925 | $11,100 |
At the high end, AI usage adds 83 percent on top of a $1,108.75 seat bill. That spread is the point. Your exposure depends on how heavily employees use AI, which is the thing most service desks are actively trying to increase.
Step 3: a full 2027 bill for a 100-agent Premium desk
Here's an illustrative bill for a 100-agent Premium desk serving about 3,000 employees:
| Line | Assumption | Monthly cost |
|---|---|---|
| Seats | 100 agents on Premium, monthly billing | $5,488.50 |
| Rovo credits | 70,000 included. Usage is 90,000: 3,000 help center conversations at 25 credits, plus 15,000 agent credits | $200.00 |
| Virtual service agent | 1,000 included. 4,000 conversations a month at the $0.30 starting rate | $900.00 |
| Automation steps | 650,000 included. Usage stays within the allowance | $0.00 |
| Assets objects | 50,000 included. 40,000 records stored | $0.00 |
| Total | $6,588.50 |
That's $79,062 a year, against $65,862 for seats alone, so usage adds about 20 percent in this scenario. Volume discounts on virtual service agent conversations and prepaid credit packs can bring that number down. Heavier AI adoption can push it up.
JSM Data Center in 2027: why this is the decision year
JSM Data Center goes read-only on March 28, 2029, and existing customers lose the ability to expand licenses on March 30, 2028. For most on-premises teams, that makes 2027 the year to choose a destination and fund the move. Planning, testing and running a migration typically takes many months, so a decision in 2028 leaves little room.
What Data Center customers should know about cost:
- Renewals stop at the deadline. You can keep renewing until March 28, 2029, but a 12-month renewal that runs past that date is prorated to end on it.
- Cloud has a different cost structure. Cloud seats are priced on the Service Collection per-agent list above, and the usage meters covered earlier have no Data Center equivalent. Model both lines rather than comparing seat prices alone.
- Data Center itself got more expensive. JSM Data Center list prices rose 15 percent on February 17, 2026, and Advantaged plans rose 18 to 40 percent depending on tier.
- Atlassian offers migration incentives. These include free cloud migration trials that match the rest of your Data Center subscription, up to 12 months, step-up credits for unused Data Center maintenance, dual licensing for larger customers, and a 10 to 20 percent first-year discount on Cloud Enterprise for qualifying purchases made by June 2027.
- Exceptions exist, but don't plan around them. Atlassian says it will offer extended maintenance after March 28, 2029 to certain customers by exception, and it's preparing FedRAMP High and Impact Level 5 environments for US government.
A forced migration is also the cheapest moment to ask whether the destination should be the same product in the cloud. The migration project, the data cleanup and the retraining happen either way. If you're weighing that, our webinar on how Atlassian changes how it uses your Jira and Confluence data and our look at how many fulfiller seats you'll need in 2029 are useful background.
How to plan your 2027 JSM budget
To build a reliable 2027 JSM budget, price the seats at the new list rate, measure your actual meter usage, set spending caps, and only then decide on monthly versus annual billing. Seven steps:
- Count agents, not users. Licensed agents drive the seat bill, and requesters are free. Remove inactive agents before your renewal quote, and keep monthly peaks down, since monthly bills charge for the highest seat count in the cycle.
- Re-price seats at the new list rate. Use $26.90 and $20.15 per agent (Standard) or $61.60 and $53.70 (Premium) for monthly billing, or request an annual quote. If your last quote predates October 13, 2026, assume it won't be honored at renewal.
- Pull your meter data. In Atlassian Administration, go to Usage, then Meters. Check Rovo credits, automation steps and Assets objects. Export the Rovo CSV to see which features and which users spend credits.
- Set a spending cap on every meter. Extra usage is on by default. A cap keeps AI and automation running up to a number you've approved, without surprises.
- Decide what happens at the cap. With extra usage off, AI pauses and automation rules stop until your usage billing date. For automation that routes or escalates tickets, a pause can cost more than the overage.
- Model AI adoption, not just today's usage. If you plan to push more employees to self-service in 2027, your credit use rises with that success. Budget the usage line from your adoption target.
- Compare monthly and annual billing last. Annual saves up to about 17 percent but locks in your agent band. Choose it once you're confident in your agent count.
For a wider view of what a service desk costs beyond licenses, see what ITSM actually costs. For the AI line in particular, see what an AI agent actually costs, and how to answer the CFO.
Is it time to look at a JSM alternative?
For many teams, the 2026 changes aren't a reason to leave JSM. A 7.5 percent seat increase is real but modest. The better question for 2027 is whether your AI costs are going to grow faster than your seat costs, and whether you're facing a forced Data Center migration anyway.
When JSM is still the right fit
- Engineering and IT share one workflow. Linking service tickets to Jira issues, deployments and Confluence is where JSM is strongest, and few tools match it.
- Your service desk is small. The free plan for 3 agents and sub-$27 entry pricing are hard to beat for small teams.
- Your agents already live in Atlassian tools. Familiarity has real value, and switching costs are real.
When an alternative is worth evaluating
- Most of your requesters aren't technical. If HR, finance and frontline employees file most requests, a conversation in Microsoft Teams or Slack usually serves them better than a portal.
- You want AI to answer more requests, but metered credits make that a budgeting risk. On a usage model, every success in self-service shows up as a higher bill.
- You're on Data Center and have to migrate anyway. You'll pay for a migration project either way, so it's the natural moment to compare destinations.
If you're comparing options broadly, our guides to the best IT ticketing systems and Freshservice vs Jira Service Management cover the wider field.
Rezolve.ai as a JSM alternative: how the model differs
Rezolve.ai is an AI-native service desk built to resolve employee requests inside Microsoft Teams and Slack, before they become tickets. It's priced per person rather than by usage, and that's the clearest point of contrast with JSM's 2027 model. On Rezolve.ai's core product, there are no per-resolution fees and no token charges. Model costs are included in the seat price, so when more requests move to AI, the bill doesn't rise with them.
The second difference is what happens to seats over time. Rezolve.ai licenses technician seats only to people who work tickets, and those seats true down at renewal. When AI resolves up to 85 percent of routine requests, you need fewer fulfiller seats, and the next term's bill reflects that.
| Area | Rezolve.ai | Jira Service Management (at the time of writing) |
|---|---|---|
| How AI is priced | ✓ Included in the seat price on the core product, with no per-resolution or token fees | Allowance of Rovo credits per agent, then $0.01 per credit from December 3, 2026 |
| What happens as self-service grows | ✓ The bill stays flat, and fulfiller seats can true down at renewal | Credit use rises with adoption, and overage bills automatically unless capped |
| Employee chat channels | ✓ Microsoft Teams and Slack at the same time, plus email, web and voice | Per Atlassian's documentation, the virtual service agent works in the help center plus one chat tool: Microsoft Teams or Slack |
| Working with Jira | ✓ Can sit in front of JSM and create and resolve JSM tickets, with engineering escalations kept as linked Jira issues | Native linkage across Jira, Confluence and deployments |
| Best fit | ✓ Organizations with 2,000 or more employees, where most requesters aren't technical | Teams of any size, especially where engineering and IT share tooling |
You don't have to replace JSM to change the cost curve. Many teams run Rezolve.ai alongside the ITSM they already have. In that setup, Agentic Sidekick handles employee conversations in Microsoft Teams and Slack, and JSM stays the record for engineering-linked work. Others move the full service desk to Rezolve.ai's own system of record.
Rezolve.ai serves 200+ enterprise customers and achieved the highest score of 10 products evaluated in two of three Use Cases (AI for End-User Self-Service and AI for IT Agents) in the 2026 Gartner® Critical Capabilities for AI Applications in IT Service Management. For a side-by-side view, See Rezolve.ai vs Jira Service Management, or see how Rezolve.ai pricing works.
Last updated on November 18, 2026
Get summary with:
See the agentic service desk in action
Watch Rezolve.ai autonomously resolve real IT and HR tickets: governed, auditable, glass-box.
Frequently asked questions
How much does Jira Service Management cost per agent in 2027?
On monthly billing, JSM Standard costs $26.90 per agent per month for agents 1 to 15 and $20.15 for agents 16 to 100. Premium costs $61.60 and $53.70 for the same bands. Enterprise is quote only, on annual billing. The free plan covers up to 3 agents.
Did Jira Service Management prices go up in 2026?
Yes. On October 13, 2026, Atlassian raised JSM (Service Collection) list prices by 7.5 percent on Standard and Premium and by 10 percent on Enterprise. Monthly customers pay the new price from their next bill. Annual customers pay it at their next renewal or quote.
When does Atlassian start charging for Rovo AI usage?
Extra usage billing for Rovo credits starts December 3, 2026. Usage above your included allowance (250, 700 or 1,500 credits per agent per month on Standard, Premium and Enterprise) bills at $0.01 per credit. Extra usage is on by default, and admins can cap it or turn it off.
Is Rovo included in Jira Service Management?
Yes. Rovo search, chat and agents are included in paid JSM plans, along with a monthly credit allowance pooled across your organization. Basic actions cost 10 credits each. Advanced agents, including the help center Self-service Agent and Request Resolver, use a variable number of credits per action.
What is the difference between Jira Service Management and Service Collection?
They're the same purchase. Atlassian now sells JSM only inside Service Collection, which bundles JSM, Customer Service Management, Assets and Rovo under one per-agent price.
Do I pay for employees who submit tickets?
No. JSM charges per agent, meaning people who work requests. Employees and customers who only submit and track requests are free and unlimited.
Does the $1 AI resolution fee apply to internal IT support?
Generally, no. The $1.00 per resolution fee applies to Customer Service Management's AI agent for external customer support. Internal employee AI support in JSM uses Rovo credits and, on Premium and Enterprise, virtual service agent conversations (1,000 a month included, then from $0.30 each).
Is annual billing cheaper than monthly for JSM?
Usually, yes, by up to about 17 percent. Twelve monthly bills for 50 Standard agents total $13,305, against an annual list price of $11,000. Annual billing is priced by agent band, so you pay for the band, not your exact headcount.
What happens to Jira Service Management Data Center?
New Data Center licenses stopped selling on March 30, 2026. Existing customers can expand or add apps until March 30, 2028, and licenses become read-only on March 28, 2029. Renewals that run past that date are prorated to end on it.
Will Jira Service Management prices go up again in 2027?
Atlassian hasn't announced a 2027 increase. It has updated cloud list prices in October in several recent years, though, so it's prudent to budget for a possible increase at your 2027 renewal and to ask for price protection in multi-year quotes.



