Jira Service Management costs $25 per agent per month on Standard and $57.30 on Premium for teams of up to 15 agents, and it is free for up to 3 agents. Atlassian's pricing page shows $20, but that figure is an average for a 75-agent team. Jira Service Management is also no longer sold on its own. It comes inside Atlassian's Service Collection.
This guide lists all 4 plans with their real per-agent prices, the 5 factors that change what a team actually pays, and three worked team budgets. Every figure comes from the price tables on Atlassian's Service Collection pricing page, checked on October 4, 2026.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Jira Service Management Pricing at a Glance
| Plan | Price per agent per month | Agents | Key additions |
|---|---|---|---|
| Free | $0 | Up to 3 | Portal, queues, knowledge base, alerts and on-call, 2 GB storage |
| Standard | $25.00 (agents 1 to 15) | Up to 100,000 | Rovo AI, Assets, custom-branded help center, audit logs |
| Premium | $57.30 (agents 1 to 15) | Up to 100,000 | Incident, problem, and change management, virtual service agent, 99.9% SLA |
| Enterprise | Annual only, through sales | Up to 100,000 | Atlassian Analytics, Guard Standard, up to 150 sites, status pages |
Prices are Service Collection monthly billing. Jira Service Management customers are free on every plan.
The 4 Jira Service Management Plans
1. Free: $0 for Up to 3 Agents
The Jira Service Management Free plan costs nothing for up to 3 agents and unlimited customers. It suits a small internal IT or HR help desk.
Included: the request portal, intake by email, chat, Slack, and Microsoft Teams, customizable forms and queues, the embedded knowledge base, and alerts with on-call schedules and escalation policies.
Limits:
3 agents
The hard ceiling. Customers are unlimited, so 3 agents can serve thousands of requesters. A 4th agent ends the Free plan.
1,250 automation steps per month for the whole site
The allowance is shared across the subscription, not per agent. Auto-assignment, SLA reminders, and auto-close rules each use steps.
2 GB of storage
Screenshots fit. Log files and screen recordings fill it fast.
Community support only
Help comes from the public Atlassian Community forum, not Atlassian staff.
Free has no Rovo AI, no Assets, and no custom-branded help center.
The 4th agent: when a Free site adds a 4th agent or runs out of storage, Atlassian moves it onto a 14-day Standard trial automatically. After the trial, every agent is billed.
2. Standard: $25 per Agent per Month
Jira Service Management Standard costs $25 per agent per month for agents 1 to 15 and $18.75 for agents 16 to 100, on monthly billing. Most paying teams use Standard.
Standard adds to Free:
- Rovo AI search, chat, and agents, with 250 Rovo credits per agent per month.
- Assets for asset and configuration management, with 5,000 objects included.
- A custom-branded help center on your own URL.
- Unlimited email notifications for customers, agents, and admins.
- 3,000 automation steps per agent per month, pooled across the site.
- Audit logs and multi-region data residency.
A 10-agent team pays $250 a month on Standard. Standard fits an internal help desk or a support team that escalates incidents without a formal process.
3. Premium: $57.30 per Agent per Month
Jira Service Management Premium costs $57.30 per agent per month for agents 1 to 15 and $49.95 for agents 16 to 100, on monthly billing. Premium is built for IT operations teams that run formal incident, problem, and change processes.
Premium adds to Standard:
- Advanced incident and problem management, with affected-service tracking, post-incident reviews, and heartbeat monitoring.
- Change management, with approval workflows, risk assessment, and deployment gating for CI/CD tools.
- AIOps, for AI-driven alert grouping and incident creation.
- The virtual service agent, a conversational AI that answers chat requests, with 1,000 assisted conversations a month included.
- Advanced asset management, with Data Manager, hardware asset management, and 50,000 objects included.
- 6,500 automation steps and 700 Rovo credits per agent per month.
- Unlimited storage, a 99.9 percent uptime SLA, and 24/7 support, with a 1-hour response for critical issues.
4. Enterprise: Annual Only, Through Sales
Jira Service Management Enterprise is sold only on annual contracts through Atlassian sales, with no self-serve monthly price. Enterprise adds Atlassian Analytics and the Data Lake, Atlassian Guard Standard for SSO and SCIM, up to 150 sites, public and private status pages, 9,500 automation steps and 1,500 Rovo credits per agent per month, and 500,000 Assets objects. A team only needs Enterprise when its security or procurement team asks for centralized identity or multi-site administration by name.
5 Things That Change What You Actually Pay
1. The $20 Headline Is a 75-Agent Average
The $20 per agent on Atlassian's Service Collection pricing page is a blended rate for a 75-agent team, not the price for small teams. The page's calculator opens preset to 75 agents. A 75-agent team pays $25 for its first 15 agents and $18.75 for the next 60, which is $1,500 a month, or $20 per agent on average. The $51.42 Premium headline is the same calculation.
2. Monthly Pricing Is Graduated
Jira Service Management monthly billing is graduated, so each agent is billed at the rate of the band that agent falls in. The first 15 agents always cost the top rate.
| Agents | Standard, monthly | Premium, monthly |
|---|---|---|
| 1 to 15 | $25.00 | $57.30 |
| 16 to 100 | $18.75 | $49.95 |
| 101 to 250 | $12.55 | $33.25 |
| 251 to 500 | $8.60 | $22.90 |
| 501 to 1,000 | $8.25 | $21.20 |
On monthly billing, Atlassian charges each month for the exact number of agents. Removing an agent lowers the next month's bill.
3. Annual Billing Only Saves Money at the Top of a Band
Annual Jira Service Management billing saves up to 17 percent, but only when the agent count sits near the top of its annual band. Annual Service Collection is sold in flat agent bands, and Atlassian bills "for the tier that most closely matches your user count." A team at the bottom of a band pays the same as a team at the top.
| Agents | Standard, annual | Premium, annual | Annual beats monthly from |
|---|---|---|---|
| 1 to 3 | $750 | $1,700 | 3 agents |
| 4 to 5 | $1,250 | $2,850 | 5 agents |
| 6 to 10 | $2,500 | $5,750 | 9 agents |
| 11 to 15 | $3,750 | $8,600 | 13 agents |
| 16 to 25 | $5,650 | $13,600 | 21 agents |
| 26 to 50 | $10,300 | $26,000 | 41 on Standard, 42 on Premium |
| 51 to 100 | $19,700 | $51,000 | 83 agents |
The last column compares each annual band with 12 months of graduated monthly billing.
A 26-agent team pays about 48 percent more on annual Standard. A 16-agent team pays about 20 percent more, and a 6-agent team about 39 percent more. A 15-agent team saves the full 17 percent, paying $3,750 a year instead of $4,500.
Rule: pay monthly when the agent count sits just above a band floor. Pay annually when it sits near a band ceiling.
4. Only Agents Are Billed
Jira Service Management bills agents only. Customers and helping developers are free.
- Agents are billed. An agent works requests and talks to customers: views queues, reports, and SLA metrics, writes customer-facing and internal comments, manages customers, and edits the knowledge base.
- Customers are free and unlimited. A customer is anyone who raises a request through the portal or by email. Atlassian says you will "never be limited to how many customers can access Service Collection."
- Jira users help for free. A developer with a Jira license can add internal comments to a request and watch it. The developer cannot reply to the customer, work the queue, or see SLA metrics.
Jira and Service Collection licenses are counted separately. A team of 6 agents and 30 developers buys 6 agent seats and 30 Jira seats, not 36 of each.
The seat that is easy to buy by accident is an agent license for someone who only needs a status. A team lead watching the queue or an account manager checking an escalation costs $25 a month as an agent.
5. Usage Charges Sit on Top of Seats
Jira Service Management has four usage-based charges beyond agent seats. None cost anything until a team uses the feature.
- Assets objects: 5,000 included on Standard, 50,000 on Premium, and 500,000 on Enterprise. Extra objects start at $0.02 per object per month.
- Virtual service agent conversations: 1,000 assisted conversations a month included on Premium and Enterprise. Extra conversations start at $0.30 each. A conversation counts when it matches an intent, whether or not the AI resolves it.
- Automation steps: 1,250 per month for the whole site on Free, then 3,000, 6,500, or 9,500 per agent per month, pooled. Automation rules stop running when the site runs out, until the next month.
- Rovo credits: 250 per agent per month on Standard, 700 on Premium, and 1,500 on Enterprise. Rovo search does not use credits. Rovo chat and agents do.
Jira Service Management Standard vs Premium
Choose Jira Service Management Premium only if your team runs formal change approvals or incident reviews. For 15 agents or fewer, Premium costs about 2.3 times as much per agent as Standard.
Premium earns its price when
- You run formal change approvals or a change advisory board
- Incidents affect services other teams depend on, and you need post-incident reviews
- Downtime has a contractual cost and you need the 99.9 percent SLA
- You want AI to answer chat requests before an agent sees them
Standard is enough when
- The help desk answers questions and fulfills requests
- Incidents are escalated to engineering, not run through a formal process
- Business-hours support is fine
- Nobody has asked for change management by name
The most common reason to upgrade is change management. An IT team approving changes in a spreadsheet or a Slack thread will usually get its money back on Premium.
What Jira Service Management Costs for 3 Real Teams
A 12-agent support team pays $3,600 a year for Jira Service Management Standard on monthly billing. The table shows three team sizes, all on Standard, with the cheaper billing option in bold.
| Team | Agents | Monthly billing | Annual billing |
|---|---|---|---|
| Small internal IT help desk | 5 | $125 a month, $1,500 a year | $1,250 a year |
| Growing support team | 12 | $300 a month, $3,600 a year | $3,750 a year |
| Support plus IT on one site | 25 | $562.50 a month, $6,750 a year | $5,650 a year |
On Premium, the same 12-agent team pays $687.60 a month, or $8,251 a year, on monthly billing, against $8,600 annually.
Engineers need Jira licenses on top. A 12-agent support team that escalates to 25 engineers on Jira Standard adds about $226 a month. The Jira pricing guide covers Jira's own plans.
Do You Need Jira Service Management at All?
Most software companies whose customer support already runs in another help desk do not need Jira Service Management. Atlassian now positions Jira Service Management for internal service, such as IT, HR, and facilities, and points external customer support to Customer Service Management, which comes in the same Service Collection license.
For a support team already on HubSpot, Zendesk, or another help desk, buying Service Collection means one of two things:
- Moving support into Atlassian. A real project: a new portal, new SLAs, new reports, and a new home for customer history that sales and customer success also need.
- Running two help desks. Support answers customers in one tool, and someone copies bugs into Jira Service Management so engineering can see them. The copying step is where bugs get lost.
What these teams usually need is narrower: a link from the support ticket to the Jira work item where engineering fixes the bug, with status and comments coming back. A link like that needs no agent licenses.
For support teams on HubSpot, IssueLinker provides that link. From a HubSpot ticket, support creates a Jira work item in one click, drafted from the ticket conversation, in the project engineering already uses. Comments sync both ways, and Jira status flows back to the ticket as it changes, so support can tell the customer the day the fix ships. IssueLinker links HubSpot tickets to Jira work items, not to Jira Service Management requests. The Jira Service Management HubSpot integration guide covers setups with and without Jira Service Management.
Connect HubSpot support to Jira without a second help desk
IssueLinker links HubSpot tickets to Jira work items and syncs comments and status both ways. Support answers from HubSpot, engineering stays in Jira, and nobody needs an agent seat to see a status. Flat monthly price, unlimited users, setup in about fifteen minutes.
IssueLinker costs $39 a month regardless of headcount, about one and a half Jira Service Management Standard agent seats. A support team that genuinely runs in Atlassian should buy Service Collection and use the native Jira link. A support team that runs in HubSpot should connect HubSpot to Jira instead.
How to Pick a Jira Service Management Plan
Pick the Jira Service Management plan for the limit your team has actually hit, not for the feature list.
A real plan for a small IT or HR help desk. Watch the 1,250 automation steps and plan for the 4th agent before you need one.
Unlimited notifications, Assets, Rovo, and enough automation for most teams. The right plan until formal change or incident management becomes someone's job.
Worth it for change approvals, post-incident reviews, the uptime SLA, or the virtual service agent. Not worth it for storage alone.
Guard, Analytics, multiple sites, and status pages. Without a named request for those, the sales conversation will not pay off yet.
5 Ways to Lower Your Jira Service Management Bill
The fastest way to lower a Jira Service Management bill is to match the billing cycle to where the agent count sits in its band.
Before your next renewal
- Check where your agent count sits in its annual band. Near the floor, monthly is cheaper. Near the ceiling, annual is.
- Remove agents who have left or changed roles. Every licensed agent is billed, active or not.
- Let developers help through internal comments on their Jira license instead of buying them agent seats.
- Separate people who reply to customers from people who only need a status. Only the first group needs an agent seat.
- Check Assets object counts and automation usage monthly, so neither surprises you during a busy period.
Is Jira Service Management Worth the Price?
Jira Service Management is worth the price for internal service desks, especially at teams already on Jira. Free customers, free developer collaboration, and Assets in the bundle make the per-agent price fair. The bill grows from two places a team controls: agent seats for people who only read, and annual bands bought at the wrong headcount.
For external customer support at a software company, a second help desk is usually not worth it. Connecting the existing help desk to Jira is cheaper and simpler. The Jira vs Jira Service Management guide, Jira vs Zendesk, and HubSpot vs Jira cover those tradeoffs.
