Jira Service Management Pricing 2026: Plans, Limits & True Cost

Jira Service Management pricing now sits inside Atlassian Service Collection. The current monthly view is straightforward at the license level: Free costs $0 for up to three agents, Standard costs $20 per agent per month, Premium costs $51.42 per agent per month, and Enterprise is sold on annual sales-assisted pricing.

The main pricing trap is assuming the per-agent license is the complete bill. It is not. Assets overage, virtual-service-agent usage, Marketplace apps, Atlassian Guard, implementation services and other Atlassian products can add cost depending on architecture and scale.

How Jira Service Management is sold in 2026

Atlassian now packages Jira Service Management cloud through Service Collection. Service Collection includes Jira Service Management, Customer Service Management and Rovo-related platform capabilities under one collection subscription.

This means buyers should evaluate the collection rather than an older JSM-only price sheet. A current JSM deployment can use the broader collection capabilities without buying each included application as a separate standalone subscription, but external Marketplace apps and separately licensed Atlassian products may still carry their own fees.

The billing model remains agent-centered for service work. An agent is a user who works tickets, sees queues and SLA information, comments internally or externally and manages service content. Customers who submit requests are not charged as agents. That distinction is crucial for employee service desks supporting hundreds or thousands of requesters with a much smaller operations team.

Free plan: $0 for three agents

The Free plan is currently free forever for up to three agents. It includes unlimited customers, service-management templates, request handling, basic incident and on-call functionality, an embedded knowledge experience and 1,250 automation steps per subscription per month.

For a two- or three-person IT team, this is a genuine production entry point rather than a time-limited demo. The free license can be sufficient when the service desk is small, workflows are uncomplicated and advanced asset, AI, change or governance capabilities are unnecessary.

The limit is strict enough that growth matters. A fourth person who needs agent capabilities moves the team into paid licensing. Buyers should therefore forecast the number of actual ticket-working agents rather than the total employee population.

Free is also useful as a low-risk way to understand Jira Service Management's request model and administration approach before paying. However, a buyer that already knows it needs Assets, custom branding, higher automation or more advanced controls should evaluate Standard during the trial rather than designing a process around Free-only boundaries.

Standard: $20 per agent per month

Standard currently costs $20 per agent per month on Atlassian's monthly pricing view. It is the first tier most established IT teams should evaluate because it expands both service-management depth and platform capacity without the Premium price jump.

Standard adds asset and configuration management, broader Rovo capabilities, custom-branded help-center options, unlimited email notifications, audit logs, multi-region data-residency options and 3,000 automation steps per user per month.

The included Assets allowance is currently 5,000 objects per organization for Service Collection Standard. For teams with a small CMDB covering endpoints, applications, owners and a manageable set of relationships, 5,000 objects may be enough. For organizations importing discovery data or modeling a large infrastructure estate, it may not be.

Standard also gives paid users Rovo allowances. The current plan comparison lists 250 Rovo credits and 1,000 indexed objects per user per month. AI usage therefore has a measurable capacity model rather than being an unlimited feature simply because Rovo appears in the plan.

Premium: $51.42 per agent per month

Premium currently costs $51.42 per agent per month on monthly billing. The difference from Standard is $31.42 per agent every month, so a ten-agent team pays $314.20 more per month before any usage charges or taxes.

The upgrade is designed around advanced operations and ITSM. Premium includes the virtual service agent, advanced AIOps, more advanced incident and problem capabilities, change management, deployment gating, real-time incident monitoring and deeper Assets functionality.

Premium also raises automation capacity to 6,500 steps per user per month and the included Assets allowance to 50,000 objects. Its Rovo allowance rises to 700 credits and 2,500 indexed objects per user per month.

This plan is easiest to justify when the team will actually use those features. If Premium replaces a separate incident-alerting product, virtual-agent tool, CMDB add-on or change workflow system, the higher license cost may be offset elsewhere. If the organization only needs more ticketing seats, Premium is difficult to justify on price alone.

Enterprise: annual, sales-assisted pricing

Enterprise does not have one universal public per-agent number. Atlassian sells the plan through annual pricing and sales assistance, and annual Service Collection pricing is tiered by user count.

Enterprise adds capabilities aimed at large organizations: Atlassian Analytics and Data Lake, advanced administration and security, Atlassian Guard Standard, support for multiple identity providers, higher automation allowances, status-page capabilities and multi-site scale up to the published limit.

The current Service Collection comparison lists 9,500 automation steps per user per month, 1,500 Rovo credits and 6,250 indexed objects per user per month. The Assets allowance rises to 500,000 objects.

Enterprise procurement should focus on quote normalization. Ask Atlassian to separate base agents, included collection products, Guard entitlements, Assets capacity, AI usage, support, implementation, Marketplace apps and renewal assumptions. A quote with a lower first-year price can still have a higher long-term cost if discounts expire or usage grows.

Annual pricing is tiered, not one flat per-agent rate

Atlassian states that annual Service Collection subscriptions are billed by the tier most closely matching the user count. Depending on the number of agents, annual subscriptions may provide better value than monthly billing.

That means it is inaccurate to multiply the monthly Standard or Premium rate by twelve and present the result as the official annual price for every team size. The annual calculator or a current sales quote should be used for the exact agent count.

This distinction matters for comparison articles. Freshdesk, Zendesk and Zoho Desk commonly advertise a fixed per-agent monthly equivalent when billed annually, while Atlassian's annual structure can vary by tier. Buyers should compare total annual spend for the same headcount rather than comparing two labels that use different billing mechanics.

Agents versus customers

Only agents require paid seats. Customers are requesters who use the portal or supported request channels and do not perform agent work. This can make JSM attractive for internal service because thousands of employees can submit requests while only the service team is licensed.

Do not confuse a stakeholder who occasionally needs to approve or collaborate with a full agent. During procurement, map every role to the permissions it needs. Over-licensing occasional participants can inflate cost, while under-licensing people who actually work tickets can create workflow and compliance problems.

14-day free trial

Atlassian currently offers a 14-day free trial of Service Collection without requiring payment information. Atlassian also states that trial extensions may be available up to a maximum of 30 days.

A useful JSM trial should be more than a product tour. Create representative request types, one approval flow, at least one SLA, several automation rules, an Assets schema if relevant and an incident workflow. Invite both agents and requesters so the evaluation covers administration and user experience.

Premium buyers should explicitly test any capability that justifies the upgrade, especially virtual service agent, AIOps, change workflows and deployment gating. A feature should not be part of the business case unless the team has validated how it fits its process and data.

Assets allowances and overage cost

Current Atlassian licensing lists 5,000 included Assets objects on Standard, 50,000 on Premium and 500,000 on Enterprise for Jira Service Management or Service Collection.

Extra Assets usage is currently priced from $0.02 per object per month after the included allowance, with volume discounts available through prepaid usage packs. Atlassian has also been moving Assets billing into its centralized usage-based billing model, so timing and billing mechanics can differ for existing and new subscriptions.

Assets counts stored objects, not monthly transactions. An object can represent a laptop, application, service, employee device, cloud resource or other configuration item. Relationships can create a powerful operational model, but importing everything from discovery systems without a data-governance plan can consume allowance quickly.

Before selecting a plan, estimate the current object count, expected discovery growth and whether stale objects will be removed. The right Assets model is a service-management design decision and a cost-control decision at the same time.

Virtual service agent usage

The virtual service agent is included in Premium and Enterprise. Atlassian currently includes 1,000 assisted conversations per month or 12,000 per year.

Usage above that allowance starts at $0.30 per assisted conversation per month, with volume discounts. Atlassian counts assisted conversations based on the virtual agent matching an intent, including conversations that may later escalate to a human agent.

This definition matters for budgeting. A buyer should not estimate cost only from fully resolved conversations. Use actual or forecasted service volumes, likely intent-match rates and escalation patterns to create a range for monthly consumption.

Set usage alerts and spending controls where available. AI automation can be valuable, but a predictable budget requires monitoring both effectiveness and the meter that drives the invoice.

Rovo usage limits

Rovo capabilities are available across paid tiers with plan-specific usage. Standard currently lists 250 Rovo credits plus 1,000 indexed objects per user per month; Premium lists 700 credits plus 2,500 indexed objects; Enterprise lists 1,500 credits plus 6,250 indexed objects.

AI usage should therefore be evaluated like any other capacity resource. Identify which workflows consume credits, how indexing volume relates to knowledge sources and what happens when the organization reaches its allowance.

Teams should also confirm data-governance settings for AI, especially where service requests can contain employee, customer or operational information. Pricing and governance are separate checks and both belong in procurement.

Automation limits

Free includes 1,250 automation steps per subscription per month. Standard includes 3,000 steps per user per month, Premium 6,500 and Enterprise 9,500.

Automation-heavy teams should estimate rule execution volume. A simple routing rule applied to every ticket may be inexpensive, while multi-step rules triggered across several projects can consume far more capacity than the ticket count suggests.

Build critical rules first, measure actual execution volume during the trial and remove duplicate automation. This improves both cost predictability and maintainability.

Customer Service Management is included in the Collection

Atlassian's current Collection billing documentation states that Service Collection includes Jira Service Management and Customer Service Management under one price. Buyers do not need to purchase those included collection apps separately simply to access the Collection entitlement.

This broadens the value story for organizations that want both internal service and customer-service capabilities. It also makes comparisons with single-purpose help desks less direct because the JSM subscription now represents a broader bundle.

Teams should still verify exactly which capabilities they will deploy and whether existing systems will be retired. Paying for a broad bundle only creates savings if the organization actually consolidates overlapping tools or uses the additional functionality.

Marketplace apps can add substantial cost

The Atlassian Marketplace is a major strength because it lets organizations extend JSM with monitoring, reporting, workflow, CRM, security and specialist ITSM functionality.

It is also a cost layer. Marketplace vendors can use separate seat, site or usage pricing, and some apps may require licenses for a broader user population than the JSM agent count.

Before signing, build a list of mandatory Marketplace apps and price them at the same scale as the core subscription. Also review vendor security, data access and renewal terms. A low-cost core plan can become expensive if the operating model depends on several paid extensions.

Atlassian Guard and identity costs

Some enterprise identity and security functions are associated with Atlassian Guard outside plans that include the entitlement. Enterprise Service Collection includes Guard Standard in the current package, while lower tiers may require separate evaluation depending on the identity controls required.

If SAML, SCIM, identity-provider architecture, advanced access controls or organization-wide security policies are mandatory, confirm the exact Guard requirement before comparing JSM with a competitor that bundles similar controls differently.

Security features are often selected late in procurement, but they can materially alter total cost. Include the identity team in the pricing review rather than treating these capabilities as optional after deployment.

Monthly Maximum Quantity Billing

Atlassian's cloud licensing documentation states that monthly subscriptions including Jira Service Management use Maximum Quantity Billing. The invoice is based on the highest number of assigned seats during the billing cycle.

If a team temporarily adds agents and later removes them before the month ends, the removed seats do not generate a mid-cycle credit. They remain available for reassignment until the next billing cycle.

This makes seat governance important. Use a controlled process for temporary agents, contractors and role changes, and schedule license reviews before the next billing period rather than assuming mid-month cleanup will reverse charges.

True-cost scenario: three-agent team

A team with three agents can remain on Free at $0 subscription cost if Free's feature and capacity limits are sufficient. Customers are unlimited, so the number of employees or external requesters does not by itself create agent charges.

The cost can still be higher than zero if the organization purchases Marketplace apps, consulting, implementation services or other Atlassian products. Free describes the Service Collection subscription, not every possible cost in an Atlassian environment.

True-cost scenario: ten agents on Standard

At the current monthly list price, ten Standard agents cost 10 × $20 = $200 per month before taxes, Marketplace apps or usage charges.

That scenario includes a 5,000-object Assets allowance and 3,000 automation steps per user per month. If the team stays inside those capacities, the base license is relatively easy to forecast.

If the same organization requires a large CMDB, separate Guard entitlement or paid Marketplace extensions, add those costs explicitly rather than burying them in an assumed percentage overhead.

True-cost scenario: ten agents on Premium

Ten Premium agents at the current monthly list price cost 10 × $51.42 = $514.20 per month before taxes and extras.

The base difference from ten Standard agents is $314.20 per month. Premium includes a 50,000-object Assets allowance and 1,000 virtual-service-agent assisted conversations per month, along with advanced AIOps, change, incident and deployment capabilities.

The upgrade makes financial sense when the team uses those capabilities enough to replace other software, reduce manual work or support an operational requirement that Standard cannot meet. Otherwise the additional seat cost is substantial.

True-cost scenario: twenty-five agents

At monthly list rates, twenty-five Standard agents would be $500 per month, while twenty-five Premium agents would be $1,285.50 per month. The difference is $785.50 per month before usage, taxes or add-ons.

At this scale, annual tier pricing may change the economics, so the monthly arithmetic should be treated as a baseline comparison rather than an annual quote. Use Atlassian's calculator or a sales proposal for the exact annual commitment.

Implementation and migration cost

Atlassian publishes product pricing but implementation effort varies widely. A simple migration from an email inbox or lightweight help desk can be small, while a mature ITSM rollout may involve service design, field mapping, workflow redesign, Assets import, integrations, identity configuration and user training.

Decide whether internal administrators, an Atlassian solution partner or a consulting team will own implementation. Professional-services cost may exceed several months of software spend, especially when the project includes CMDB design or complex enterprise migration.

Migration should also include a cleanup plan. Carrying years of unused fields, workflows and asset records into JSM can create complexity without business value.

Support and reliability considerations

Support depth, uptime commitments and escalation options increase across tiers. Buyers should match support requirements to business criticality rather than selecting Premium or Enterprise only because those plans sound safer.

If the service desk supports revenue-critical operations or regulated services, document response requirements, escalation contacts, uptime commitments and disaster-recovery expectations. These requirements can justify a higher tier even when feature usage alone does not.

Cancellation and refund rules

Atlassian cloud subscriptions can be cancelled. Under current cloud licensing, a cancelled subscription generally terminates at the end of the current billing cycle, and there is no automatic credit simply for cancelling before the cycle ends.

Refunds for monthly cloud subscriptions are available within the first paid month after the trial period. New annual cloud subscriptions can be refunded within 30 days of first purchase. Cloud renewals and upgrades are generally not refundable under the standard policy.

Usage-based subscriptions and extra usage have separate refund restrictions. This is another reason to monitor Assets and AI consumption rather than assuming all charges can be reversed under the core-subscription refund window.

Taxes and regional pricing

Taxes can be applied based on billing location and exemption status. Regional pricing and currency presentation can also differ from the U.S. monthly numbers used in this guide.

This article keeps all numeric comparisons in U.S. dollars and does not convert currencies. International buyers should use Atlassian's local billing experience and validate tax treatment with their finance team.

Which plan should a small IT team choose?

Use Free if three agents are enough and the team does not need paid-plan Assets, scale or governance. It is a credible way to formalize requests without adding a software subscription.

Move to Standard when the team grows past three agents or needs Assets, more automation, broader AI, stronger administration or branding. For many small and midsize IT organizations, Standard is the most balanced tier.

Which plan should a mature ITSM team choose?

Premium is the logical evaluation tier when advanced incident operations, AIOps, virtual service agent, change management, deployment gating or much larger Assets capacity are central requirements.

Do not buy Premium simply because the organization is larger. A thirty-agent team with straightforward request management may still be well served by Standard; a ten-agent SRE-led service team may need Premium because its operational workflows are sophisticated.

When does Enterprise make sense?

Enterprise makes sense when the buying requirement includes organization-scale analytics, multiple sites, advanced identity or governance, large Assets capacity and enterprise support or commercial terms.

The purchase should be quote-driven. Normalize multi-year pricing, renewal increases, support, Guard, usage, implementation and Marketplace apps so the organization can compare Enterprise with ServiceNow, Freshservice or other large-scale ITSM options on total cost rather than only license price.

Pricing alternatives context

Zendesk's general customer-service pricing starts at $19 per agent per month paid yearly for Support Team, while its employee-service offering starts higher. Freshdesk Growth is currently $19 per agent per month billed annually. Zoho Desk's Express tier is $7 per user per month billed annually, and Help Scout now offers a Free plan plus paid tiers.

Those numbers are not perfectly comparable with JSM because billing periods and product scopes differ. JSM is deeper in ITSM, change and asset workflows than most customer-support tools, while simpler help desks may cost less and require less administration.

The most useful comparison is therefore operational: identify the capabilities the team genuinely needs, then price the least expensive plan at each vendor that satisfies those requirements.

Pricing methodology

Toollers rechecked Atlassian's current Service Collection pricing, Assets licensing, Premium feature comparison, cloud billing and refund rules on October 9, 2026. The guide uses current public U.S. monthly prices and does not infer a single annual per-agent rate because Atlassian annual subscriptions are tiered by user count.

Continue reading about Jira Service Management

• Jira Service Management tool profile
• Jira Service Management Review: Features, Pricing, Pros and Cons
• Jira Service Management Alternatives 2026: 4 Options by Use Case