AI features in Customer Service Management will also be charged separately.<\/p>\n\n\n\n
These changes do not mean that subscription prices will automatically increase. Extra charges will apply only to usage above the included limits when the option for additional usage is enabled. Keep in mind, however, that additional usage is enabled by default. Unless an administrator turns it off or sets a spending limit, overage charges will be applied automatically.<\/p>\n\n\n\n
What is changing?<\/strong><\/strong><\/h2>\n\n\n\nUntil now, the use of many Atlassian features has mainly been limited by the limits included in a product, plan, or subscription. The new model also measures the use of specific resources, called meters<\/em>.<\/p>\n\n\n\nEach meter measures a different type of activity, such as the number of credits used by AI features or the number of steps performed by the automation system.<\/p>\n\n\n\n
In practice, this means that two payment models will work together:<\/p>\n\n\n\n
\n- Fixed subscription fee<\/strong> \u2013 the organization will continue to pay for its selected plan and number of users according to the terms of its agreement.<\/li>\n\n\n\n
- Charges for excess usage<\/strong> \u2013 if the organization uses more than the included limit and has additional usage enabled, it will pay for the extra units.<\/li>\n<\/ul>\n\n\n\n
Available limits are combined at the organization level for each meter. This means that usage can be shared between eligible applications and subscriptions.<\/p>\n\n\n\n
(source: Atlassian Support \u2013 How usage-based pricing works<\/a>)<\/p>\n\n\n\nWho will be affected by the new charges?<\/strong><\/strong><\/h2>\n\n\n\nThe changes apply to organizations using selected Atlassian Cloud products. The exact scope depends on the application, plan, and type of usage.<\/p>\n\n\n\n
The main areas include:<\/p>\n\n\n\n
\n- Jira and Confluence, as well as Teamwork Collection and Service Collection \u2013 including Rovo credits and automation steps.<\/li>\n\n\n\n
- Jira Service Management and Customer Service Management \u2013 depending on the plan, this may include Assets objects and successful resolutions handled by an AI agent.<\/li>\n\n\n\n
- Bitbucket Cloud \u2013 including build minutes, Git LFS storage, package storage, and package network transfer.<\/li>\n<\/ul>\n\n\n\n
It is important to understand the difference between types of storage. Not all Atlassian storage automatically becomes chargeable when a limit is exceeded.<\/p>\n\n\n\n
For example, Jira and Confluence have their own standard storage limits. Exceeding these limits may require an organization to change its plan or delete data, rather than pay for every additional unit. In Bitbucket, however, some resources, such as Git LFS and package storage, are included in the new usage-based pricing model.<\/p>\n\n\n\n
For this reason, organizations should check which products and meters they use before estimating the impact on their costs.<\/p>\n\n\n\n
(sources: Atlassian \u2013 Usage-Based Pricing<\/a> and Atlassian Support \u2013 Track storage and move data across apps<\/a>)<\/p>\n\n\n\nWhich resources will be charged for?<\/strong><\/strong><\/h2>\n\n\n\nRovo AI credits<\/strong><\/strong><\/h3>\n\n\n\nRovo credits are units that measure the use of selected AI features and additional context from Teamwork Graph.<\/p>\n\n\n\n
Credits are used by features such as Rovo Chat, AI agents, Jira Coding Agent, and selected Teamwork Graph queries. Rovo Search, definitions, and summaries are free.<\/p>\n\n\n\n
The price for additional usage is $0.01 per credit ($10 per 1,000 credits).<\/p>\n\n\n\n
When the included limit is reached:<\/p>\n\n\n\n
\n- Additional usage is enabled \u2013 the features continue to work, and charges apply according to the price list and spending limit.<\/li>\n\n\n\n
- Additional usage is disabled \u2013 features that require paid credits are paused until the limit is renewed or more resources are purchased.<\/li>\n<\/ul>\n\n\n\n
(source: Atlassian Support \u2013 How Rovo credits work<\/a>)<\/p>\n\n\n\nAutomation steps<\/strong><\/strong><\/h3>\n\n\n\nThe new model measures individual steps performed by an automation rule, rather than only counting how many times the rule runs.<\/p>\n\n\n\n
A step can include a trigger, condition, action, branch, or loop. This means that a single run of a complex rule can take many steps. In some situations, a step is counted even if it does not change any data.<\/p>\n\n\n\n
The price for additional usage is $0.50 per 1,000 steps.<\/strong><\/p>\n\n\n\nFor example, if an organization exceeds its monthly limit by 100,000 steps, the additional charge will be $50.<\/p>\n\n\n\n
It is important to note that actions using Rovo agents are charged separately in Rovo credits. Therefore, the number of rule executions, automation steps, and AI credits should not be treated as the same thing. <\/p>\n\n\n\n
(source: Atlassian Support \u2013 How is your automation usage calculated?<\/a>)<\/p>\n\n\n\nResolutions handled by an AI agent<\/strong><\/strong><\/h3>\n\n\n\nIn Customer Service Management, a separate meter is used for AI agent resolutions.<\/p>\n\n\n\n
A resolution is counted when an AI agent solves a customer request on its own, without transferring the conversation to a human employee, and the system marks the issue as resolved.<\/p>\n\n\n\n
According to the current documentation, there is no standard free allowance for these resolutions included in the subscription. The base price is $1 per resolution, while larger packs may offer a lower per-unit price.<\/p>\n\n\n\n
This is a separate type of charge, independent of Rovo credits and automation steps.<\/p>\n\n\n\n
(source: Atlassian Support \u2013 Manage usage for AI agent resolutions<\/a>)<\/p>\n\n\n\nBitbucket and Assets resources<\/strong><\/strong><\/h3>\n\n\n\nThe changes also cover selected Bitbucket Cloud resources, including build minutes, Git LFS, package storage and package network transfer.<\/p>\n\n\n\n
For Assets, the meter measures the number of objects.<\/p>\n\n\n\n
Limits and prices depend on the specific resource and plan. Organizations should check the official price list rather than assuming the same rate applies to every product. <\/p>\n\n\n\n
(source: Atlassian \u2013 Usage-Based Pricing<\/a>)<\/p>\n\n\n\nHow will the changes affect an organization’s costs?<\/strong><\/strong><\/h2>\n\n\n\nAdditional costs will depend on resource usage and the limits included in the plan. Organizations that stay within their limits will not pay extra charges.<\/p>\n\n\n\n
The greatest risk applies to organizations that use AI agents and automation heavily.<\/p>\n\n\n\n
The following table shows example costs for two meters:<\/p>\n\n\n\n
Each meter measures a different type of activity, such as the number of credits used by AI features or the number of steps performed by the automation system.<\/p>\n\n\n\n
In practice, this means that two payment models will work together:<\/p>\n\n\n\n
- \n
- Fixed subscription fee<\/strong> \u2013 the organization will continue to pay for its selected plan and number of users according to the terms of its agreement.<\/li>\n\n\n\n
- Charges for excess usage<\/strong> \u2013 if the organization uses more than the included limit and has additional usage enabled, it will pay for the extra units.<\/li>\n<\/ul>\n\n\n\n
Available limits are combined at the organization level for each meter. This means that usage can be shared between eligible applications and subscriptions.<\/p>\n\n\n\n
(source: Atlassian Support \u2013 How usage-based pricing works<\/a>)<\/p>\n\n\n\n
Who will be affected by the new charges?<\/strong><\/strong><\/h2>\n\n\n\n
The changes apply to organizations using selected Atlassian Cloud products. The exact scope depends on the application, plan, and type of usage.<\/p>\n\n\n\n
The main areas include:<\/p>\n\n\n\n
- \n
- Jira and Confluence, as well as Teamwork Collection and Service Collection \u2013 including Rovo credits and automation steps.<\/li>\n\n\n\n
- Jira Service Management and Customer Service Management \u2013 depending on the plan, this may include Assets objects and successful resolutions handled by an AI agent.<\/li>\n\n\n\n
- Bitbucket Cloud \u2013 including build minutes, Git LFS storage, package storage, and package network transfer.<\/li>\n<\/ul>\n\n\n\n
It is important to understand the difference between types of storage. Not all Atlassian storage automatically becomes chargeable when a limit is exceeded.<\/p>\n\n\n\n
For example, Jira and Confluence have their own standard storage limits. Exceeding these limits may require an organization to change its plan or delete data, rather than pay for every additional unit. In Bitbucket, however, some resources, such as Git LFS and package storage, are included in the new usage-based pricing model.<\/p>\n\n\n\n
For this reason, organizations should check which products and meters they use before estimating the impact on their costs.<\/p>\n\n\n\n
(sources: Atlassian \u2013 Usage-Based Pricing<\/a> and Atlassian Support \u2013 Track storage and move data across apps<\/a>)<\/p>\n\n\n\n
Which resources will be charged for?<\/strong><\/strong><\/h2>\n\n\n\n
Rovo AI credits<\/strong><\/strong><\/h3>\n\n\n\n
Rovo credits are units that measure the use of selected AI features and additional context from Teamwork Graph.<\/p>\n\n\n\n
Credits are used by features such as Rovo Chat, AI agents, Jira Coding Agent, and selected Teamwork Graph queries. Rovo Search, definitions, and summaries are free.<\/p>\n\n\n\n
The price for additional usage is $0.01 per credit ($10 per 1,000 credits).<\/p>\n\n\n\n
When the included limit is reached:<\/p>\n\n\n\n
- \n
- Additional usage is enabled \u2013 the features continue to work, and charges apply according to the price list and spending limit.<\/li>\n\n\n\n
- Additional usage is disabled \u2013 features that require paid credits are paused until the limit is renewed or more resources are purchased.<\/li>\n<\/ul>\n\n\n\n
(source: Atlassian Support \u2013 How Rovo credits work<\/a>)<\/p>\n\n\n\n
Automation steps<\/strong><\/strong><\/h3>\n\n\n\n
The new model measures individual steps performed by an automation rule, rather than only counting how many times the rule runs.<\/p>\n\n\n\n
A step can include a trigger, condition, action, branch, or loop. This means that a single run of a complex rule can take many steps. In some situations, a step is counted even if it does not change any data.<\/p>\n\n\n\n
The price for additional usage is $0.50 per 1,000 steps.<\/strong><\/p>\n\n\n\n
For example, if an organization exceeds its monthly limit by 100,000 steps, the additional charge will be $50.<\/p>\n\n\n\n
It is important to note that actions using Rovo agents are charged separately in Rovo credits. Therefore, the number of rule executions, automation steps, and AI credits should not be treated as the same thing. <\/p>\n\n\n\n
(source: Atlassian Support \u2013 How is your automation usage calculated?<\/a>)<\/p>\n\n\n\n
Resolutions handled by an AI agent<\/strong><\/strong><\/h3>\n\n\n\n
In Customer Service Management, a separate meter is used for AI agent resolutions.<\/p>\n\n\n\n
A resolution is counted when an AI agent solves a customer request on its own, without transferring the conversation to a human employee, and the system marks the issue as resolved.<\/p>\n\n\n\n
According to the current documentation, there is no standard free allowance for these resolutions included in the subscription. The base price is $1 per resolution, while larger packs may offer a lower per-unit price.<\/p>\n\n\n\n
This is a separate type of charge, independent of Rovo credits and automation steps.<\/p>\n\n\n\n
(source: Atlassian Support \u2013 Manage usage for AI agent resolutions<\/a>)<\/p>\n\n\n\n
Bitbucket and Assets resources<\/strong><\/strong><\/h3>\n\n\n\n
The changes also cover selected Bitbucket Cloud resources, including build minutes, Git LFS, package storage and package network transfer.<\/p>\n\n\n\n
For Assets, the meter measures the number of objects.<\/p>\n\n\n\n
Limits and prices depend on the specific resource and plan. Organizations should check the official price list rather than assuming the same rate applies to every product. <\/p>\n\n\n\n
(source: Atlassian \u2013 Usage-Based Pricing<\/a>)<\/p>\n\n\n\n
How will the changes affect an organization’s costs?<\/strong><\/strong><\/h2>\n\n\n\n
Additional costs will depend on resource usage and the limits included in the plan. Organizations that stay within their limits will not pay extra charges.<\/p>\n\n\n\n
The greatest risk applies to organizations that use AI agents and automation heavily.<\/p>\n\n\n\n
The following table shows example costs for two meters:<\/p>\n\n\n\n
- Charges for excess usage<\/strong> \u2013 if the organization uses more than the included limit and has additional usage enabled, it will pay for the extra units.<\/li>\n<\/ul>\n\n\n\n
![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2026\/04\/Blog-Atlassian-Desktop_.jpg\")
\n <\/picture>\n