Jira asset management pricing: Assets and apps

Compare included Assets allowances, object overages and Marketplace user tiers. Use worked examples and a five-step checklist to estimate your cost.

Reviewed 2026-10-18

Jira asset management is priced in one of two ways. With Atlassian Assets, your plan includes an object allowance and you pay $0.02 per object per month above it (as listed on 18 October 2026). With a Marketplace app, you pay per user at your whole Jira site's user tier, even if only the IT team uses it. So every estimate starts with two counts: records and users.

Native Assets: included objects and extra usage

Assets is included in paid Jira plans and paid Service Collection plans. A paid Jira site does not need Jira Service Management (JSM) to use it.

Included allowances:

• Jira Free: Assets not included.
• Jira Standard, Premium and Enterprise: 1,000 objects per organization.
• Teamwork Collection Standard, Premium and Enterprise: 5,000 objects per organization.
• JSM or Service Collection Free: Assets not included.
• JSM or Service Collection Standard: 5,000 objects per organization.
• JSM or Service Collection Premium: 50,000 objects per organization.
• JSM or Service Collection Enterprise: 500,000 objects per organization.

Jira's pricing page says Assets objects are available to Standard and Premium single-site customers, with rollout to additional customers in progress. The licensing FAQ labels Jira and Teamwork Collection allowances as single-site, with rollout to multi-site organizations in the next calendar year. Check eligibility before relying on an allowance.

Allowances pool across subscriptions at organization level: JSM Premium (50,000) plus Jira Standard (1,000) gives 51,000.

One object means one tracked thing, however you create it. A laptop, vendor or person stored as an object each counts toward usage. Attributes and references do not count separately, and schemas are free. Deleting an object lowers the count immediately.

Above the allowance, the list rate is $0.02 per object per month, with volume discounts for prepaid packs. Extra-usage billing starts on 3 December 2026 for new Assets customers after 1 September 2026 and for existing monthly customers.

If extra usage is off when you reach the allowance, new-object creation pauses, including imports and automation that add objects. Existing objects stay usable. See the Assets licensing FAQ for allowances, pooling and usage rules.

The subscription underneath

The object charge comes on top of the subscription. These are the monthly-billing prices Atlassian displayed on 18 October 2026, in USD. Prices vary by user count and billing cycle, so get your figure from the pricing page rather than multiplying these rates.

Jira pricing:

• Free: $0, for 10 users.
• Standard: $8.48 per user per month.
• Premium: $15.56 per user per month.
• Enterprise: annual billing; contact sales.

Service Collection pricing:

• Free: 3 agents; Assets not included.
• Standard: $21.50 per agent per month.
• Premium: $55.28 per agent per month.
• Enterprise: annual billing; contact sales.

Service Collection includes Jira Service Management, Customer Service Management, Assets and Rovo. Agents are licensed; customers who submit requests are free. Keep those groups separate when estimating the subscription: requester numbers are not agent numbers.

If you already pay for an eligible plan, its allowance is already yours. Separate what you pay today from any new object or app charge.

Worked examples: the object meter only

These examples use the list rate, before volume discounts. They exclude subscription charges and show the monthly object charge once extra-usage billing applies.

• Jira Standard with 1,600 objects: subtract the 1,000-object allowance, leaving 600 extra objects. At $0.02 each, that is about $12 per month.
• Service Collection Standard with 8,000 objects: subtract 5,000, leaving 3,000 extra objects. At $0.02 each, that is about $60 per month.
• The same organization adding Jira Standard: the allowances pool to 6,000 objects. With 8,000 objects, 2,000 are extra, costing about $40 per month.

The last example shows pooling, not the total financial effect of adding a subscription. The underlying Jira subscription has its own cost, which must be included in that decision.

Marketplace apps: count the site's users

A paid Atlassian Marketplace app licence must match the host product's user tier, even when only some users use the app. An inventory managed by a small IT team can therefore require an app licence covering the whole Jira user tier.

When Jira and JSM share a site, the higher user tier applies. Cloud app licences match the host tier automatically, according to Atlassian's Marketplace licensing rules.

For this model, cost scales with headcount rather than asset count. Check the app listing's pricing tab for the applicable per-user tiers. A quote based only on the people managing inventory will miss the site's licensing requirement.

AssetPilot's pricing model

AssetPilot is made by Plugins Factory, the publisher of this page. It is free for Jira sites with up to 10 users. Above that it is priced per Jira user, with one edition and every feature included. Version 0.1 handles up to 5,000 assets per Jira site. See the AssetPilot page for availability.

Which model costs less for you

Use these rules of thumb to choose which calculation to investigate first:

• Many records and few users: compare the per-user app quote with Assets object overages, while checking the app's asset limit.
• Many users and few records: check whether your records fit inside an existing Assets allowance before adding a site-wide app charge.
• An existing paid Jira or JSM / Service Collection subscription: count its included allowance, including any organization-level pooling.

Neither count decides it alone. Compare the real app tier with the object charge and any plan change each option needs.

Estimate your cost in five steps

1. Count records by type. Include locations, vendors and people if you store them as objects, alongside equipment and other tracked things. Use the asset inventory CSV template to prepare the count.
2. Check your current plan, rollout eligibility and included allowance. Account for subscriptions that pool at organization level.
3. Subtract the allowance from your object count. If the result is positive, multiply it by $0.02 for the monthly object estimate at the list rate, before volume discounts. Check when billing applies.
4. Check the app user tier. Use the whole site's applicable tier, including the higher tier when Jira and JSM share a site, and obtain the listing's price.
5. Add recurring growth to both estimates. Revisit expected object additions and changes to the site's user tier, then include the relevant subscription costs.

Start with your inventory count and current subscription before requesting a quote. For plan eligibility and capabilities, read does Jira have asset management?; for the broader choice of approaches, see Jira asset management.