Jira Assets object limits and pricing in 2026
Assets now comes with an object allowance on every paid Jira, Teamwork Collection and Service Collection plan, and anything over it is billed. This page sets out what each plan includes, what counts, what extra objects cost and where to find your own numbers.
Last checked against Atlassian's published pages on . Atlassian does change these things, so check the sources at the bottom before you budget on them.
Objects included with each plan
| Plan | Objects included |
|---|---|
| Jira Standard, Premium or Enterprise | 1,000 |
| Teamwork Collection | 5,000 |
| Service Collection or Jira Service Management Standard | 5,000 |
| Service Collection or Jira Service Management Premium | 50,000 |
| Service Collection or Jira Service Management Enterprise | 500,000 |
Service Collection and Jira Service Management share the same numbers. The Jira and Teamwork Collection allowances became generally available on 1 September 2026 for single-site organisations on Standard and Premium. Atlassian says multi-site organisations will follow next year.
How allowances add up
Allowances are pooled across your organisation's subscriptions rather than tied to one product. Jira Service Management Premium (50,000) plus Jira Standard (1,000) gives you 51,000.
Every schema on a site draws from that one number. Schemas themselves are free, so spreading data across more of them doesn't change anything. If your organisation has more than one site, Atlassian asks you to talk to your account team for now.
What extra objects cost
The list price is $0.02 per object per month over the allowance. You can pay for what you used at the end of each billing cycle, or buy prepaid object packs up front. Bigger packs get volume discounts.
Some examples at list price:
| Setup | Included | Objects | Extra a month |
|---|---|---|---|
| Jira Premium on its own | 1,000 | 12,000 | $220 |
| Service Collection Standard and Jira | 6,000 | 40,000 | $680 |
| Service Collection Premium and Jira | 51,000 | 200,000 | $2,980 |
When billing starts
- Monthly plans: 3 December 2026.
- New Assets customers who bought after 1 September 2026: 3 December 2026.
- Annual plans: nothing changes. Extra objects were already billed by tier, and still are.
What counts as an object
Every object in a schema counts once, however it got there: typed in by hand, imported from CSV, JSON or LDAP, created by Assets Discovery or another sync, added through the REST API or made by an automation rule. Attributes and references don't add anything.
These don't count:
- Business Portfolio and Software Registry objects in Atlassian's system schemas
- Data held in Data Manager, because it isn't in a schema
- Copies in sandboxes and backups
- Deleted objects, from the moment they're deleted
What happens when you reach the allowance
There's no hard cap. When you reach the allowance, extra usage switches on automatically and objects keep being created, at $0.02 each. You can set a limit on extra usage, and Atlassian sends alerts at 80% and 100% of the allowance and of any limit you set.
If you switch extra usage off and haven't bought a pack, Assets stops adding objects. Manual creation, imports and syncs that would add objects (Discovery included) and automation rules that create them all pause. Everything already in Assets keeps working.
Checking your own numbers
- For the organisation total, go to Atlassian Administration › Insights › Platform usage › Assets objects. The count there is close to real time.
- For counts by schema, open App usage in Assets settings.
- The usage forecast looks back 90 days, so a big one-off import will skew it for a while.
- When you delete objects, the count drops that day. The dashboard catches up within about 15 minutes.
Work out your bill
Put in your object count and plans. It adds up the allowances and prices everything above them.
At the list price of $0.02 per object per month. Prepaid object packs cost less per object.
Bringing the count down
Some of this is quick. Most of it takes longer than anyone budgets for, which is why we're building an app for it.
- Start with the biggest object types. The per-schema counts tell you where to look, and it's usually a handful of object types that matter.
- Check what your imports create. Discovery and importer apps can create an object for every software version, network adapter or short-lived virtual machine they see. Narrowing what an import creates is often the biggest single saving.
- Untangle overlapping feeds. If two sources describe the same laptop, you pay for it twice. Pick one source for each object type, or match records on serial number, MAC address or hostname and merge them.
- Remove dead objects carefully. Export them first, along with the work items they're linked to. Deleting takes an object off the count straight away, and getting one back later is much harder.
- Give each object type an owner. Counts creep back up when nobody is responsible for them.
Sources
- Atlassian, Assets licensing and usage
- Atlassian Support, Manage your bill for extra objects for Assets