Jira Service Management pricing explained: Free, Standard, Premium and the Assets question
Short answer
Atlassian now sells Jira Service Management as part of Service Collection, a single cloud subscription that also includes Customer Service Management, Assets and Rovo. Plans are Free, Standard, Premium and Enterprise. On Nov 6, 2026 the calculator on Atlassian's Atlassian Service Collection / Jira Service Management pricing page (default team size shown as 75 agents) displayed Standard at $21.50 and Premium at $55.28 per agent per month; Free is $0 forever for up to 3 agents. Pricing is progressive (volume discounts as seats grow), so your figure changes with agent count and monthly vs annual billing — use Atlassian's calculator for your number. Assets is included on paid plans with free object allowances of 5,000 (Standard), 50,000 (Premium) and 500,000 (Enterprise); above that, objects start at $0.02 USD per object per month. What usually forces Premium is change management, advanced incident and problem management, the virtual service agent, AIOps, the 99.9% uptime SLA and Premium support — not Assets itself, which already ships on Standard.
Contents
- Who this guide is for
- Free, Standard, Premium and Enterprise at a glance
- The Assets question: allowances, overages and when it matters
- What actually forces Premium (and what does not)
- How to read the bill for 10, 25 and 75 agents
- Costs outside the Service Collection seat price
- Best for / wrong choice when
- A plain decision guide
- Frequently asked questions
Who this guide is for
This guide is for IT and operations leaders evaluating Jira Service Management (JSM) for an internal service desk, typically 5 to 150 agents, and for existing JSM Cloud customers trying to understand a renewal, an Assets bill or a push toward Premium. It is also for finance partners who have been handed an Atlassian quote that now says "Service Collection" instead of "Jira Service Management".
Every price, allowance and plan difference below comes from Atlassian's own pages, checked on Nov 6, 2026: the Atlassian Service Collection / Jira Service Management pricing page, the Service Collection pricing page (EN), the Service Collection Pricing & Licensing page and Atlassian's How billing works for Atlassian Collections. Opinions about which plan fits which team are ours, from implementing JSM for mid-market IT teams, and are labelled as such.
Service Collection is how Atlassian sells JSM now
From late 2025 into 2026 Atlassian has been moving eligible Jira Service Management Cloud sites onto Service Collection. Per Atlassian's Transitioning to Service Collection documentation, existing JSM plans are being moved into Service Collection and receive the Customer Service Management app on the same cloud site, with no migration of users or data. You pay one collection price; you are not charged a separate seat for CSM. If your quote or admin console still says Jira Service Management alone, ask your admin whether the Service Collection transition has reached your site yet — the plan names and feature split in this guide match the Service Collection packaging.
Free, Standard, Premium and Enterprise at a glance
Service Collection has four cloud plans. The table summarises what Atlassian publishes on the pricing and licensing pages as of Nov 6, 2026. Dollar amounts for Standard and Premium are the calculator figures shown on the pricing page for its default team size of 75 agents; they are not a flat list price for every seat count.
| Plan | List / calculator price (checked Nov 6, 2026) | Agent limit highlights | What Atlassian positions it for |
|---|---|---|---|
| Free | $0 forever for up to 3 agents | 3 agents, 2 GB storage, Community Support | Trying Service Collection; very small teams |
| Standard | $21.50 per agent / month at the page's default 75-agent calculator setting (progressive) | Paid agents; unlimited customers; Assets included with 5,000 free objects | Getting started with service management plus Assets |
| Premium | $55.28 per agent / month at the same 75-agent calculator setting (progressive) | Everything in Standard, plus advanced ITSM, AIOps, virtual service agent, higher allowances | Scaling IT and operations with change, incident depth and SLA |
| Enterprise | Contact sales; annual billing only on the pricing page | Everything in Premium, plus advanced admin, Guard Standard included, multi-site (up to 150), status pages, highest allowances | Large or regulated orgs that need scale and security controls |
A few packaging facts matter before you compare numbers:
- Customers (requesters) are free. Atlassian's pricing FAQ defines a customer as anyone who creates requests via the portal or email. Customers do not consume a Service Collection licence, and Atlassian states you are never limited on customer count.
- Agents are named users who work tickets. An agent can view queues, reports and SLAs, comment internally and with customers, manage knowledge and manage customers. Jira Software users who are not licensed as agents can still leave internal comments and watch tickets, but they are not agents.
- One collection licence covers JSM and CSM. Customer Service Management is included with Service Collection Standard and Premium at no extra seat cost. Atlassian's FAQ says you are not charged separately for CSM and it does not add to the seat bill. Usage meters for CSM's AI agent are separate (see below).
- Data Center is a different product line. Service Collection is Cloud-only. Jira Service Management and Assets remain available as Data Center products for self-managed deployments, with their own lifecycle. If you are on Data Center, see our JSM Data Center to Cloud guide.
How Atlassian calculates the subscription
Atlassian's pricing FAQ says monthly subscriptions are billed on the exact number of Service Collection users you have, and annual subscriptions are billed for the tier that most closely matches your user count. Monthly pricing is progressive: each user's unit price depends on the pricing rate band that user falls into, with volume discounts as you add seats. That is why the calculator figure at 75 agents will not match the figure at 10 or at 200. Always run the calculator for your headcount, and treat any single per-agent number you see on a marketing page as illustrative for that team size.
For monthly subscriptions Atlassian also applies Maximum Quantity Billing: your bill is based on the highest number of seats assigned at any point in the billing cycle. Adding seats mid-cycle is prorated for the rest of the month; removing seats mid-cycle does not reduce that month's bill. That detail catches teams who temporarily grant agent access during projects.
The Assets question: allowances, overages and when it matters
Assets (Atlassian's CMDB / asset and configuration management) is one of the most common reasons teams open the pricing page — and one of the most misunderstood. Assets is included in Service Collection Standard, Premium and Enterprise. You do not buy a separate Assets SKU for Cloud Service Collection. What you do buy, if you exceed the free allowance, is extra object capacity.
| Plan | Free Assets objects included | Overage (Atlassian published rate) |
|---|---|---|
| Standard | 5,000 objects | Starts at $0.02 USD per object per month, with volume discounts |
| Premium | 50,000 objects | Same published starting overage rate |
| Enterprise | 500,000 objects | Same published starting overage rate |
Atlassian defines an Assets object as a representation of a single, unique thing of a particular object type in an object schema. The total counts all schemas on the site. System schemas used by other Jira features (for example Services), and Products, Entitlements and Services, are not charged. Extra capacity is managed in Atlassian Administration under Platform usage.
How to think about Assets cost before you buy
- Count objects, not assets in the loose sense. A laptop, a licence entitlement, a network switch and a business service can each be an object depending on how you model the schema. Over-modelling (every cable, every spare mouse) burns the allowance fast.
- Standard's 5,000 is enough for many mid-market CMDB starts if you model services, critical CIs and owned hardware deliberately. It is tight if you import every endpoint from discovery without filtering.
- Do not upgrade to Premium only for Assets headroom. Premium's 50,000 objects is a large jump, but Premium's seat price is also a large jump. Run the overage maths at $0.02 per object first. For example, 10,000 objects over Standard's 5,000 allowance is 5,000 billable objects; at the published starting rate that is a usage line, not automatically a plan upgrade.
- Discovery and imports drive spikes. A first discovery run that creates tens of thousands of objects overnight is a classic surprise. Stage imports, set object-type filters, and agree who may create schemas.
Our view
Assets rarely forces Premium on its own. What forces Premium is usually process scope (change, major incident, virtual agent) or the uptime SLA. Treat Assets as a usage meter you can manage, and upgrade the plan when the process features — not the object count — require it.
How to read the bill for 10, 25 and 75 agents
Because pricing is progressive, we do not multiply a single sticker price by agent count and call it annual cost. Instead, use this method with Atlassian's calculator on the pricing page:
A sober quoting method
- Count named agents who will work tickets — not every Jira Software user, and not requesters.
- Decide Standard vs Premium from process scope (change, major incident, virtual agent, SLA), not from a sales default.
- Estimate Assets objects for year one with a schema sketch; compare overage at $0.02 against the Premium seat jump.
- Run the official calculator for monthly and annual at your agent count; save screenshots with the date.
- Add expected virtual service agent conversations above 1,000/month if you are on Premium and plan to switch it on.
- Add Marketplace apps, Atlassian Guard (if not already included via Enterprise), and Confluence only if you grant product access beyond the embedded knowledge base pattern Atlassian describes.
| Scenario | Plan leaning | What usually dominates cost | Watch-outs |
|---|---|---|---|
| 10 agents, request + incident + knowledge | Standard | Seat subscription | Keep Assets schema lean; Free is only for ≤3 agents |
| 25 agents, formal change + on-call + major incident | Premium | Seat subscription (large step up from Standard) | Do not buy Premium only for Assets; confirm change/incident needs |
| 75 agents, CMDB + virtual agent + AIOps | Premium (Enterprise if multi-site / Guard-at-scale) | Seats + possible VSA overage + Assets if modelling is broad | Calculator figure at this size was $55.28/agent/month for Premium on Nov 6, 2026 — re-check live |
For a side-by-side with Freshservice's published per-agent prices and ServiceNow's quote-only model, use our Freshservice vs JSM vs ServiceNow pricing guide. That guide is the right place for total-cost framing; this guide is the right place for understanding Atlassian's own meters.
Best for / wrong choice when
Service Collection Standard is a good fit when
- You need a portal, email/chat intake, SLAs, queues and reporting for a mid-sized IT or shared-services desk.
- You want a real CMDB starter with Assets and can keep objects within or near the 5,000 free allowance.
- Your engineering organisation already lives in Jira, and agents collaborating with developers matters more than deep ITIL change.
- You can live without the virtual service agent and without Premium's advanced incident/change feature set in year one.
Premium is the better default when
- Change management, major incident / problem practice, or AIOps is in scope for year one.
- You need the financially-backed 99.9% uptime SLA and Premium support response times.
- You plan to run the virtual service agent on employee channels at any meaningful volume.
- Unlimited storage and higher automation / Rovo allowances are necessary, not nice-to-have.
Wrong choice when
- Wrong: buying Premium only because "we might need a big CMDB". Model objects and price overage first.
- Wrong: counting every employee as an agent. Requesters are free; only ticket-workers need agent seats.
- Wrong: ignoring CSM AI resolution meters if you turn on external customer AI. Internal-IT-only teams can ignore it; mixed IT + external support teams cannot.
- Wrong: treating Free as a production plan for a real company service desk. Three agents and 2 GB is a trial shape, not a department shape.
A plain decision guide
Before you sign or renew
- Confirm whether your site is already on Service Collection or still on legacy JSM packaging.
- Write down year-one processes: request, incident, problem, change, Assets scope, virtual agent yes/no.
- Produce an agent roster from identity groups you trust, and a separate requester count for portal design.
- Sketch the Assets object model and a year-one object estimate; compare overage vs Premium seats.
- Run Atlassian's calculator for your agent count on Standard and Premium, monthly and annual; date the screenshots.
- Ask which usage meters will be enabled on day one and who owns watching them monthly.
If JSM is on a shortlist next to Freshservice or ServiceNow, keep this guide for Atlassian's meters, and use our comparison and pricing guides for cross-vendor framing. If you are leaving Data Center, pair this with the Data Center to Cloud migration guide so licence timing and feature gaps are handled together.
Frequently asked questions
Is Jira Service Management the same as Service Collection?
Service Collection is Atlassian's cloud collection that includes Jira Service Management, Customer Service Management, Assets and Rovo under one subscription. JSM is the service-management app inside that collection. Existing JSM Cloud sites are being transitioned onto Service Collection per Atlassian's documentation.
How much does Jira Service Management Standard cost?
Atlassian uses progressive, calculator-based pricing. On Nov 6, 2026 the Service Collection pricing page calculator showed Standard at $21.50 per agent per month at its default team size of 75 agents. Your price depends on agent count and billing period — use Atlassian's calculator for an exact figure.
How much does Premium cost, and when do I need it?
On Nov 6, 2026 the same calculator showed Premium at $55.28 per agent per month at 75 agents. Premium is the realistic plan when you need change management, advanced incident/problem/AIOps, the virtual service agent, the 99.9% uptime SLA or Premium support, as described on Atlassian's pricing page.
Are Assets included, or do I pay extra?
Assets is included with Service Collection Standard, Premium and Enterprise. Free object allowances are 5,000 / 50,000 / 500,000 respectively. Above the allowance, Atlassian publishes overage starting at $0.02 USD per object per month with volume discounts.
Do requesters or customers need a licence?
No. Atlassian states customers who raise requests via the portal or email are free and unlimited. You pay for agents who work tickets.
Is there still a Free plan?
Yes. Service Collection Free is $0 forever for up to 3 agents, with 2 GB storage and Community Support, per Atlassian's pricing page checked on Nov 6, 2026.