Standard
Contact vendor for exact pricing and packaging details.
Plan type: Commercial. Billing period: Custom.
Jira Service Management publishes per-agent pricing across four tiers: Free for up to 3 agents, Standard at $17.65 per agent per month, Premium at $44.27 per agent per month, and Enterprise at a custom quote — all billed annually for cloud deployment.
Atlassian also offers a Data Center option for self-hosted environments, priced on a separate annual license model. The published rates make initial comparison straightforward, but the pricing story gets more complicated once you account for the October 2024 packaging changes that moved core ITIL capabilities out of the Standard plan.
The question most JSM evaluators need to answer is not which tier has the best features-per-dollar ratio — it is whether the team's actual ITSM requirements land in the Standard tier or demand Premium.
That distinction determines whether the effective per-agent cost is $17.65 or $44.27, which repositions JSM against an entirely different competitive set. A team budgeting at the Standard rate and discovering six months later that change management requires Premium faces a 150% per-agent cost increase that was avoidable with better upfront planning.
Editorial policy: How we review software · How rankings work · Sponsored disclosure
Use this Jira Service Management pricing page to understand commercial fit, rollout assumptions, and where pricing conversations need more detail.
The Free plan covers up to 3 agents with service request management, basic incident handling, a self-service portal, and Confluence knowledge base integration. It is a permanent tier — not a trial — and provides enough functionality for a two- or three-person IT team to run a basic help desk indefinitely.
The 3-agent ceiling makes it a proof-of-concept tool or a small-team solution, not a growth platform. The free tier does not include SLA management beyond basic configurations, change management, problem management, the CMDB, or the AI virtual agent.
Standard at $17.65 per agent per month adds multi-language support, custom domain for the portal, audit logs, and 250 automation rule executions per month. Since Atlassian's October 2024 packaging change, Standard no longer includes change management, problem management, or advanced incident management workflows.
This makes Standard viable for teams that only need a service request portal and basic ticket routing — but inadequate for any organization running formal ITIL processes. The 250 automation execution limit is also restrictive: a service desk processing more than a few dozen tickets daily with automated assignment, escalation, and notification rules will exhaust that allocation within the first two weeks of the month.
Premium at $44.27 per agent per month is where JSM becomes a complete ITSM platform. It includes the full incident management module with major incident coordination and post-incident reviews, change management with risk assessment and CI/CD deployment gating, problem management with root cause tracking, asset and configuration management through the native CMDB, the AI virtual agent with 1,000 conversations per month, and unlimited automation executions.
For any team that needs ITIL-aligned processes, Premium is not an upgrade — it is the baseline. The price jump from Standard represents a 150% increase per agent, but the feature gap makes it non-optional for operational IT teams.
Enterprise requires a custom quote and layers on cross-product analytics (Atlassian Analytics), Atlassian Guard for advanced security and governance policies, unlimited managed accounts, and sandbox environments for testing configuration changes. Enterprise pricing is negotiated based on agent count and organizational requirements — expect significant volume discounts at scale, but also expect longer procurement cycles with Atlassian's enterprise sales team. Enterprise is relevant for organizations with 200+ agents, multi-region deployments, or compliance requirements that exceed what Premium provides.
Jira Service Management pricing should be evaluated in the context of rollout scale, admin ownership, and the commercial metric that drives expansion cost over time.
Pricing pages should help buyers understand not just what the vendor charges, but what implementation scope, support needs, and operational complexity mean for total ownership. Use this page to frame vendor conversations before final procurement.
Start the evaluation by mapping the team's ITSM process requirements against the Standard-Premium boundary. If the team runs — or plans to run — change advisory boards, tracks root causes through problem records, coordinates major incidents across multiple teams, or needs a CMDB for asset dependency mapping, the answer is Premium.
If the team's scope is limited to receiving service requests through a portal, routing tickets to the right queue, and tracking resolution — without formal change or problem processes — Standard is sufficient. There is no middle ground: Atlassian does not sell individual ITIL modules as add-ons to the Standard plan.
For teams on the free tier evaluating a move to paid, calculate the agent count at 18 months rather than at launch. JSM's per-agent model means costs scale linearly with headcount, and organizations that extend service management to HR, facilities, or legal add agents faster than the initial IT team anticipates.
A team launching with 10 IT agents at Premium pricing pays $5,313 annually; if that grows to 25 agents across three departments within 18 months, the annual cost reaches $13,281. Atlassian's volume discounts reduce per-agent rates at higher seat counts (the per-agent price decreases at 15+, 50+, and 100+ agent thresholds), but the growth trajectory should be modeled before budget approval.
Data Center pricing operates on a different model entirely — annual license fees based on agent tiers rather than per-agent monthly subscription. Data Center is relevant for organizations with regulatory constraints against cloud-hosted ITSM, but Atlassian's product development investment is concentrated on Cloud.
New features, AI capabilities, and automation improvements ship to Cloud first, and some may never reach Data Center. Organizations choosing Data Center should weigh the compliance requirement against the feature velocity gap and factor in the infrastructure costs (server provisioning, database management, patching, backups) that Cloud eliminates.
Contact vendor for exact pricing and packaging details.
Plan type: Commercial. Billing period: Custom.
The single most expensive mistake in JSM procurement is budgeting at the Standard rate when the team's requirements demand Premium. Before requesting a quote or approving a budget, document whether the team needs change management, problem management, major incident coordination, the CMDB, or the AI virtual agent. If the answer to any of those is yes, the per-agent cost is $44.27, not $17.65. Presenting a Standard-based budget to leadership and later requesting a 150% upgrade creates procurement friction and erodes trust in the evaluation process.
JSM's published per-agent rate does not include Marketplace apps that many deployments require. Advanced forms beyond the built-in dynamic forms, time tracking for SLA compliance reporting, enhanced dashboards and reporting beyond JQL-based widgets, and customer satisfaction survey integrations each add per-agent or flat monthly costs. Survey the Marketplace for the specific apps the deployment will need, add their costs to the per-agent rate, and use that total when comparing JSM against competitors like Freshservice or SysAid — which include some of these capabilities natively. A typical mid-market deployment adds $5-15 per agent per month in Marketplace app costs.
JSM deployments that start with a single IT team frequently expand to HR, facilities, legal, and finance service desks within the first year. Each new department adds agents to the license count. Before approving the budget, identify which departments are likely to request service portals within 18 months and include their expected agent count in the cost model. A 10-agent IT deployment that grows to 30 agents across four departments triples the annual license cost — and that growth is predictable if you ask the right questions before procurement.
If the team is considering Standard to save on per-agent costs, validate that the 250 monthly automation execution limit is sufficient for the team's actual ticket volume and automation complexity. Create representative automation rules during the free-tier evaluation — auto-assignment, SLA breach escalation, notification triggers, ticket transitions — and project the monthly execution count based on current ticket volume. If projected consumption exceeds 250 within the first two weeks, the team will either need Premium (unlimited automation) or will need to disable automation rules mid-month, which undermines the operational value of the platform.
Atlassian publishes tiered pricing that decreases the per-agent rate at higher seat counts. The published $17.65 and $44.27 rates are the base rates for small agent counts. At 15+ agents, 50+ agents, and 100+ agents, the per-agent rate decreases progressively. For any deployment above 15 agents, request the specific volume pricing from Atlassian or an Atlassian Solution Partner before finalizing the budget comparison against competitors. The volume discount can meaningfully narrow the pricing gap between JSM Premium and alternatives like Freshservice that include ITIL processes in lower tiers.
Jira Service Management costs $17.65 per agent per month on the Standard plan or $44.27 per agent per month on the Premium plan, both billed annually. The Free plan supports up to 3 agents at no cost. Enterprise pricing requires a custom quote. Volume discounts reduce per-agent rates at 15+, 50+, and 100+ agent thresholds. Since October 2024, the Standard plan no longer includes change management, problem management, or advanced incident management — so teams needing full ITSM capabilities should budget at the Premium rate.
Yes — the Free plan is a permanent tier, not a time-limited trial. It supports up to 3 agents with service request management, basic incident handling, a self-service portal, and Confluence knowledge base integration. There is no expiration date. The Free plan is distinct from the 7-day free trial of paid plans (Standard and Premium), which provides temporary access to paid features for evaluation. For small IT teams with 3 or fewer agents whose needs are limited to service requests and basic incident tracking, the Free plan is a viable long-term option.
The critical difference since October 2024 is ITIL process coverage. Standard handles service requests, basic incident management, and provides 250 automation executions per month. Premium adds change management with risk assessment and CI/CD gating, problem management with root cause tracking, major incident coordination, the native CMDB for asset and configuration management, the AI virtual agent (1,000 conversations per month), and unlimited automation executions. The price difference is $17.65 versus $44.27 per agent per month — a 150% increase — but the feature gap makes Premium the only viable option for teams that need formal ITIL processes.
Freshservice includes incident, change, problem, and asset management in its Growth tier at $29 per agent per month billed annually. JSM requires the Premium tier at $44.27 per agent per month to match that ITIL coverage. For teams that need full ITSM processes without existing Atlassian ecosystem investment, Freshservice is cheaper on a per-agent basis and includes comparable ITIL capabilities in a lower tier. JSM's pricing advantage exists for teams already on Atlassian Cloud — where the platform infrastructure cost is already absorbed — and for teams that derive measurable value from the native Jira Software and Confluence integration that Freshservice cannot replicate.
Atlassian offers two evaluation paths: a 7-day free trial of the Standard or Premium paid plans, and a permanent Free tier for up to 3 agents. The free tier is the better evaluation path for most teams because 7 days is insufficient to validate ITSM workflows, SLA configurations, and automation rules in a production-representative environment. Start with the Free tier to test portal configuration, request types, Atlassian ecosystem integration, and basic automation — then use the 7-day trial specifically to evaluate Premium-only features like change management, the CMDB, and the AI virtual agent once the team has a clear sense of what it needs.
Yes — Jira Service Management Data Center is available for organizations that require self-hosted deployment. Data Center uses annual license fees based on agent count tiers rather than per-agent monthly subscription pricing. The annual license cost is separate from Cloud pricing and includes software maintenance and support. Organizations choosing Data Center also bear the infrastructure costs: server provisioning, database management, SSL certificates, security patching, backups, and disaster recovery. Data Center receives fewer feature updates than Cloud, and AI capabilities like the virtual agent are Cloud-only. Request Data Center pricing directly from Atlassian or an Atlassian Solution Partner.
Use the next pages below to move from pricing back into category context, product detail, alternatives, comparisons, and glossary terms.
Return to the category hub when the team needs broader buying context before narrowing further.
Check which tools in this category offer free tiers, trials, or community editions.
Check the commercial model, official pricing notes, and what to validate before procurement treats the pricing as settled.
Use alternatives when the product is credible but the buying team still needs stronger pressure-testing against competing fits.
Use comparison pages once the shortlist is specific enough for direct vendor-to-vendor evaluation.
Use glossary terms when the product page raises category language that needs a clearer operational definition.