Most teams do not start looking for Jira Service Management alternatives because the product is bad. They start looking because the invoice stopped matching the mental model. You budgeted for agent seats, then discovered that the asset management you needed sits behind a tier upgrade, the reporting you wanted is a Marketplace app, and that app bills against your total Jira user count rather than your agent count.

This guide covers what JSM actually costs once add-ons are included, what "service desk without add-ons" should mean, and how to evaluate replacements without swapping one dependency chain for another.

Four reasons account for nearly all of it.

Cost that scales the wrong way. Atlassian's list pricing puts JSM Standard around $20 per agent per month and Premium in the range of roughly $48 to $51 per agent per month, with a Free tier capped at three agents. The jump from Standard to Premium is not incremental — it is roughly a 2.5x step, and it is where asset and configuration management, advanced change management, and the virtual service agent live. Teams that need one Premium feature pay Premium for every agent.

Add-on dependency. Analyses of JSM deployments consistently find that Marketplace apps add somewhere between 50% and 100% to the total, and that most teams end up running three to six paid apps. Critically, some apps bill against the maximum number of users across all Jira products on the site, not against JSM agents — so a site with 100 Jira Software users and 40 JSM agents pays the 100-user rate for those apps.

Deployment lock-in. This is the newest and largest driver. Atlassian has confirmed that Data Center products reach end of life on 28 March 2029, with new customers unable to purchase Data Center subscriptions or Data Center Marketplace apps after 30 March 2026 and existing customers losing expansion rights after 30 March 2028. At EOL, Data Center instances and their apps become read-only. For organisations with data residency, air-gap, or sovereignty requirements, cloud-only is not a migration path — it is a disqualification.

Configuration weight. JSM is genuinely powerful and genuinely heavy. Request types, workflow schemes, permission schemes, notification schemes, and SLA calendars all have to be built before the first ticket lands well.

The phrase is doing real work, so define it precisely. A service desk is add-on free when these capabilities ship in the licence you already bought:

Run this table against any shortlisted product and price the row, not the headline. A tool at a higher list price with eight of nine rows included is usually cheaper than a lower list price with five.

1. Count the right units

Per-agent pricing sounds simple until you define an agent. Ask whether the following consume a paid seat: a developer who occasionally comments on a ticket, a manager who only reads dashboards, an approver who touches the system twice a month, an automation service account. The answer changes the total more than the per-seat rate does.

2. Decide the deployment question first

It filters the market faster than anything else. If you need on-premises or private cloud for compliance, data residency, or contractual reasons, resolve that before comparing features — and check the vendor's roadmap commitment, not just today's availability. The Atlassian Data Center wind-down is a reminder that a self-hosted option available today may be a migration project tomorrow.

3. Separate ITSM depth from ticket handling

Be honest about which you need. A team routing HR onboarding requests and laptop replacements needs intake, SLAs, approvals, and a knowledge base. A team running formal change enablement with a CMDB, problem records, and post-incident review needs materially more. Buying ITIL-grade depth for a request desk is the most common overspend in this category — and it is exactly the Standard-versus-Premium decision in JSM.

4. Check whether the service desk connects to delivery work

Most service desk tickets end in one of three places: answered from the knowledge base, resolved by a configuration change, or converted into development work. The third path is where tools break down. If a ticket becomes a bug or a feature request, does it carry its origin with it? Can support see that the fix shipped in release 4.2.0 and close the loop with the customer? In the Atlassian model this requires JSM and Jira Software licensed and linked. In a unified platform it is one object graph.

5. Price three years, not one

Include implementation, admin time, training, per-app renewal increases, and the cost of the migration you will eventually run. A tool that is 20% cheaper per seat but requires a dedicated administrator is not cheaper.

Rather than a ranked list that ages badly, sort the market into four shapes and pick the shape first.

•      Cloud help desk platforms — strong intake, ticketing, and deflection; usually per-agent; weaker at engineering-side traceability. Good for customer support desks.

•      Full ITSM suites — deep change, problem, and CMDB capability, priced accordingly. Justified when you have a formal ITIL practice and auditors.

•      Open-source self-hosted desks — no licence cost, real infrastructure and maintenance cost. The right answer when you have platform engineering capacity and unusual requirements.

•      Unified delivery platforms with a built-in service module — the service desk is one module inside a product that also handles requirements, development, testing, and release. Fewer integrations, and support tickets connect natively to the engineering work that resolves them.

Sanplex sits in the fourth category. Its feedback and ticket modules provide the service desk portal, ticket assignment, progress tracking, and time logging inside the same product as product management, project management, test management, and the document module — so a customer report can convert into a story, task, or bug without an integration, and the knowledge base is not a separate licence. Both cloud and on-premises deployment are supported, which matters given the Data Center timeline. Pricing is per user per year across Free, Standard, and Premium tiers rather than per agent per month; the pricing page carries the current figures.

The honest caveat: Sanplex's strength is delivery-connected service work. If you need a formal CMDB with discovery and dependency mapping for a large ITIL practice, evaluate a dedicated ITSM suite against it rather than assuming parity.

Three things decide whether a service desk migration succeeds.

1.    Decide what history to bring. Closed tickets older than two years are almost always better exported to cold storage than migrated. Migrate open tickets, the request catalogue, SLA definitions, and the knowledge base.

2.    Rebuild workflows rather than replicating them. Most JSM instances carry years of accreted request types, half of which are unused. Migration is the cheapest opportunity you will ever get to delete them. Pull usage data first: any request type with under a dozen tickets in twelve months is a deletion candidate.

3.    Run parallel for one full SLA cycle. Point new intake at the new system while the old one drains. Do not cut over mid-month if your SLA reporting is monthly.

Where the alternative offers an automated import from Jira, use it for structured data and treat attachments, custom fields, and automation rules as manual work regardless of what the tooling claims.

What are the main alternatives to Jira Service Management?

They fall into four categories: cloud help desk platforms for customer support, full ITSM suites for formal ITIL practices, open-source self-hosted desks for teams with platform engineering capacity, and unified delivery platforms such as Sanplex where the service desk is a module alongside development and test management.

How much does Jira Service Management cost per agent?

At Atlassian's list pricing, the Free tier covers up to three agents, Standard is around $20 per agent per month, and Premium sits in the region of $48 to $51 per agent per month, with Enterprise quoted individually. Marketplace apps commonly add 50–100% on top. Confirm current figures on Atlassian's pricing page before budgeting.

What is the difference between Jira Service Management and Jira Software?

Jira Software is an issue tracker for engineering teams managing sprints, bugs, and feature work. Jira Service Management is an ITSM product for service requests, incidents, and on-call alerting. They share a platform but are separate products with separate licences and separate pricing.

Is there a self-hosted alternative to Jira Service Management?

Yes. Since Atlassian Data Center products reach end of life on 28 March 2029 and close to new customers after 30 March 2026, organisations with data residency requirements are actively evaluating self-hosted options, including open-source service desks and commercial platforms such as Sanplex that offer on-premises deployment.

Can I run a service desk without Marketplace apps?

Only if the capabilities you need are in the base licence. Audit which of your installed apps cover intake forms, SLA logic, reporting, approvals, and asset tracking, then check each candidate product against that list — those five categories account for most Marketplace spend on service desks.

What is the difference between a help desk and a service desk?

A help desk resolves incoming issues reactively, ticket by ticket. A service desk manages the broader service relationship: a request catalogue, SLAs, problem management, change enablement, and knowledge management. The distinction matters because it determines which product tier you need.