Jira Service Management vs ServiceNow: Licensing and Total Cost Compared
This page compares Jira Service Management and ServiceNow on licensing and total cost rather than feature checklists. It is written to stay credible with buyers who may reasonably choose either — including the places where ServiceNow is genuinely the better answer.
The short answer: the most defensible finding in this whole comparison is an asymmetry of evidence. Atlassian publishes its prices. ServiceNow publishes none at all — its ITSM pricing page shows tiers and “Get Custom Quote,” and does not even state the licensing unit. Every ServiceNow figure below comes from a reseller rate card, a benchmark dataset or an advisory estimate, and we label them as such.
How each one licenses
Jira Service Management — now the Service Collection
Standalone JSM is no longer sold. It is bought as the Service Collection, bundling Jira Service Management, Customer Service Management, Assets and Rovo AI, plus the platform apps. Per-agent pricing did not increase at the transition.
| Plan | Monthly | Annual equivalent | Agent cap |
|---|---|---|---|
| Free | $0 | — | 3 agents |
| Standard | $20/agent/mo | ~$16.60/agent/mo | 100,000 |
| Premium | $51.42/agent/mo | ~$42.68/agent/mo | 100,000 |
| Enterprise | Quote only, annual billing | 100,000, up to 150 sites | |
Customers and requesters are free and unlimited. You license agents — the people who work tickets. That is the cleanest structural difference in the comparison.
But JSM is not purely per-agent any more. Three consumption meters now exist: Assets objects (5,000 included on Standard, 50,000 Premium, then $0.02 per object per month), Virtual Service Agent (1,000 assisted conversations a month, then $0.30 each), and Rovo credits (250/700/1,500 per user per month by plan, pooled org-wide, $0.01 per credit overage). A page that says “JSM pricing didn’t go up” is technically true and materially incomplete.
ServiceNow — role-based, and unpublished
ServiceNow’s model has three subscription categories. The one that matters for ITSM is role-based, counted by querying role-assignment tables, with four counted tiers:
- Fulfiller — active users holding a fulfiller role. The expensive seat.
- Fulfiller + Requester — used by collaborative products.
- Business Stakeholder — approvers without fulfiller roles, measured across role-assignment and approval-activity tables.
- Unrestricted User — all active instance users counted. Used by HRSD and Employee Center Pro.
What converts a free user into a billable fulfiller: assignment of any role granting write access to other people’s task records — most commonly itil, but also custom roles inheriting write permissions. Billing triggers on role assignment, regardless of actual usage.
One contested point we will not assert either way. Some advisory sources state flatly that ServiceNow approvers are free. ServiceNow’s own community licensing guide describes Business Stakeholder as a counted, measured tier. These are not reconcilable from public sources. The honest position: requester portal access is generally included, but whether approvers are free depends on the product and your contract. Get it in writing.
The one published ServiceNow price list we found
A UK government framework rate card, published by a reseller in mid-2025, per user per month in GBP — using the pre-2026 tier names:
| Item | Fulfiller | Unrestricted User |
|---|---|---|
| ITSM Standard | £80 | £12 |
| ITSM Professional | £120 | £16 |
| ITSM Enterprise | £180 | £24 |
Benchmark data from procurement platforms puts the median ServiceNow contract at roughly $127,000 a year across 108 purchases, with a median discount around 38% off published rates. A US federal agreement signed in 2025 secured up to 70% off list on certain bundles — useful mainly as hard evidence that ServiceNow list prices carry very large discount headroom.
Where ServiceNow costs escalate
- Custom applications and tables. Custom apps on the Now Platform are licensed separately from ITSM. Contracts typically include an allowance of around 20 custom tables per application; tables created outside properly scoped applications, or touching ITSM data, can trigger separate charges or a tier upgrade. Table counts commonly grow 15–40% within a single contract term.
- IntegrationHub transactions. Billed per execution of an integration action — a REST call, a script step, a spoke action. Per-record loops and retry logic inflate consumption substantially.
- Additional product SKUs. ITOM, ITAM, SecOps and HRSD are separate purchases. Note that HRSD uses the Unrestricted User model — it scales with total headcount, not IT staff. That is the structural cost trap when expanding beyond IT.
- Capacity-based billing is measured at peak, not average — relevant for ITOM and ITAM where discovered device counts spike.
- Renewal uplift. Default annual uplift is around 7%; renewals without an uplift cap commonly reset 18–35% higher.
Where JSM has real limits
This section matters more than the pricing one for credibility, so here it is plainly. Gartner’s September 2025 Magic Quadrant for AI Applications in ITSM placed ServiceNow as a Leader and Atlassian as a Niche Player. Gartner’s specific caution on Atlassian: limits on the number of intelligent actions to automate AI workflows “have disrupted larger customers” — so the Rovo credit ceiling is an analyst-documented friction point at scale, not a theoretical one.
Genuine capability gaps:
- CMDB depth and discovery. ServiceNow provides an enterprise CMDB with native agentless and agent-based Discovery and Service Mapping. JSM Assets has no equivalent native discovery and operates on object-count limits with per-object overage. For sprawling or heavily virtualised infrastructure, Assets is not a substitute.
- ITOM, event management and AIOps. JSM has none of this. It is a category absence, not a maturity gap.
- Out-of-the-box ITIL process coverage. ServiceNow ships structured ITIL-aligned processes; JSM takes a lighter, more configurable approach that requires work to reach rigorous compliance.
- Complex multi-departmental workflows. ServiceNow spans ITOM, HR, security, legal, finance and customer service on one platform. JSM remains fundamentally IT and development centred.
- Asset management maturity. ServiceNow has dedicated hardware and software asset management with licence reconciliation. JSM Assets is a flexible object database, not a licence-compliance engine.
- Extensibility dependency. Several JSM gaps are closed with Marketplace apps at an estimated $3–10 per agent per month — real cost and real vendor-management overhead. ServiceNow’s claim that JSM relies on third-party apps for capabilities that are standard in ServiceNow ITSM has some substance to it.
For balance, Gartner’s cautions on ServiceNow: the only vendor in the evaluation not offering a free trial, complex AI search configuration requiring low-code rule creation, and having lagged competitors in tailoring language models for ITSM-specific use cases.
Modelled cost: 50 agents, 2,000 employees
Modelled, not quoted. Neither vendor quoted these figures. Atlassian inputs are published list prices; ServiceNow inputs are benchmark estimates. Assumptions: 50 agents or fulfillers, 2,000 employees as requesters, annual billing, ITSM only with no ITOM, HRSD or SecOps, around 5,000 configuration items, moderate AI use.
| Line | JSM / Service Collection | ServiceNow (estimated) |
|---|---|---|
| Licence, annual | $9,960 (Standard) to $25,608 (Premium) | $40,800–$66,000 at negotiated rates |
| Assets / CMDB | 5,000 CIs fits Standard exactly; growth at $0.02/object/mo | Included in ITSM; Discovery is a separate SKU |
| Virtual agent overage | ~$3,600/yr at 2,000 conversations/mo | Assist pools with overage |
| Marketplace apps if needed | $1,800–$6,000/yr | — |
| Implementation, year 1 | No independent dataset exists | $75,000–$400,000 (one estimate); 3–5× licence (another) |
| Ongoing admin | — | 1–3 dedicated FTE |
| Software total, modelled | ~$10,000–$35,000/yr | ~$41,000–$200,000/yr |
That is roughly a 4–6× difference on modelled steady-state software spend, and 3–6× per seat at list. But the comparison is only fair if scope matches — a ServiceNow estate that includes Discovery, CMDB and ITOM is not doing the same job as JSM Standard. If you need those capabilities, the multiple is not a saving, it is a difference in what you are buying.
Note also the evidentiary asymmetry on implementation: ServiceNow implementation cost has multiple independent estimates, and two credible ones disagree by roughly 2×. For JSM, no rigorous independent dataset exists — only vendor and partner claims. We would rather say that than quote a number we cannot stand behind.
What actually migrates?
Moves reasonably well, with commercial tooling: users and admins, companies to organisations, incidents to requests, knowledge bases with categories and articles, attachments, custom fields, comments and approvals. Service catalogs map to JSM request types.
Does not move: workflows, automations, SLA definitions, the CMDB and CI records, and integrations. Scripted ServiceNow customisations — Business Rules, Client Scripts, UI Policies — have no JSM equivalent at all. Migration partners describe this as “not a lift-and-shift but a transformation,” which is the polite way of saying business logic gets rebuilt.
We found no equivalent tooling or documented path for the reverse direction. Do not assume symmetry.
What changed in 2025 and 2026
- ServiceNow, April 2026: five tiers collapsed into Foundation, Advanced and Prime. Legacy SKUs reached end of sale on 1 July 2026, and legacy pricing cannot be reinstated after that date. If a proposal in front of you says “ITSM Pro,” it is using retired naming.
- ServiceNow AI is no longer a separate add-on. It is bundled into every tier via an assist pool with consumption-based overage. Pool sizes run 1,500 / 3,000 / 6,000 assists per ITSM fulfiller by tier. Critically, large agentic actions consume 150 assists each against 25 for small ones — a 12× faster burn under heavy use. Top-up unit rates are the negotiation point and must be fixed pre-signature. Only Prime permits custom AI agent creation.
- Atlassian, October 2025: Service Collection launched; standalone JSM withdrawn for new customers; per-agent price unchanged. Existing customers auto-transitioned at renewal between February and June 2026, with projects and configurations preserved.
- Atlassian AI monetisation moved to credits at the same time, with the consumption meters listed earlier.
The pattern on both sides is the same: headline per-seat pricing held roughly flat while variable cost moved into consumption meters. Model AI consumption before signing, on both sides.
Frequently asked questions
Do we pay for requesters and approvers?
On JSM, no — customers and requesters are free and unlimited. On ServiceNow, requester portal access is generally included, but approvers may be counted as Business Stakeholder licences depending on the product. Get it in writing.
Can I get a ServiceNow price without talking to sales?
No. Nothing is published. Benchmarks suggest a median contract around $127,000 a year and a median discount near 38% off list, which tells you the list price is a starting position rather than a price.
Will JSM Assets replace a real CMDB?
Not for sprawling infrastructure. There is no native discovery, object counts are capped by plan with per-object overage above that, and CI sprawl is directly billable. For a modest, well-understood estate it can be sufficient. For an enterprise CMDB programme it is not the same product.
What do we give up moving off ServiceNow?
Native Discovery and Service Mapping, ITOM and event management, mature hardware and software asset management, out-of-the-box ITIL rigour, and enterprise governance depth. That is a real list and it should be weighed honestly.
How long does implementation take?
ServiceNow ITSM-only estimates run 8–14 weeks with $75,000–$400,000 in services; enterprise-wide programmes run 12–24 months. JSM is claimed to be weeks rather than months, but no independent cost dataset exists for it.
Our renewal is coming and we are on legacy ServiceNow SKUs. Does that matter?
Yes. Legacy SKUs reached end of sale on 1 July 2026 and legacy pricing cannot be reinstated. Whatever you do next, do it with the Foundation / Advanced / Prime structure and the assist-pool mechanics in front of you, and fix the top-up rates before signing.
Atlassian pricing verified 19 September 2026 against Atlassian’s published Service Collection pricing and Rovo usage documentation. ServiceNow publishes no list pricing; figures shown are from a published government framework rate card, procurement benchmark datasets and advisory estimates, each labelled accordingly. Gartner placements are from the September 2025 Magic Quadrant for AI Applications in ITSM. TCO figures are modelled, not quoted.
The honest comparison depends on scope, not sticker price
If you need Discovery, ITOM and a real CMDB, the cost multiple is not a saving. We model both properly against what you actually need to run — and handle the migration, including the workflow rebuild that no tool does for you.