{"id":11090,"date":"2026-09-15T14:53:05","date_gmt":"2026-09-15T14:53:05","guid":{"rendered":"https:\/\/titanapps.io\/blog\/?p=11090"},"modified":"2026-09-15T15:10:36","modified_gmt":"2026-09-15T15:10:36","slug":"atlassian-usage-based-pricing-explained","status":"publish","type":"post","link":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained","title":{"rendered":"Atlassian Usage-Based Pricing Explained"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">On September 1, 2026, Atlassian announced an expanded usage-based pricing model for its Cloud apps. Rovo credits, Automation steps, and AI agent resolutions will become billable for the first time. Assets and Bitbucket already bill on usage for some customers, and their terms change too. This article explains how each meter works, when the changes go live, and how usage is calculated. It also provides some optimization tips and possible courses of action to consider.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Atlassian Usage-Based Pricing in Brief<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it is.<\/strong> On September 1, 2026, Atlassian expanded usage-based pricing to five metered capabilities: Rovo credits, Automation steps, Assets objects, Bitbucket usage, and Customer Service Management AI agent resolutions. The first three become billable for the first time.<\/li>\n\n\n\n<li><strong>When it starts.<\/strong> Usage shows in Atlassian Administration under Platform usage. Billing for most meters begins December 3, 2026. Assets and Bitbucket are already billed on usage.<\/li>\n\n\n\n<li><strong>What stays the same.<\/strong> Usage-based pricing adds to seat-based pricing rather than replacing it, and applies to Atlassian Cloud only.<\/li>\n\n\n\n<li><strong>How allowances work.<\/strong> Paid plans include a monthly allowance sized by plan tier and seat count. Free plans get a fixed allowance per subscription and no Rovo credits. Allowances pool organization-wide, except Bitbucket until October 26, and unused capacity does not carry over.<\/li>\n\n\n\n<li><strong>The biggest change is automation.<\/strong> Jira, Confluence, Jira Service Management, and other Cloud apps now count individual automation steps instead of rule runs. You&#8217;re charged for a step even if your rule is misconfigured or finds nothing to act on. Extra steps cost $0.50 per 1,000, and Enterprise plans no longer include unlimited automation.<\/li>\n\n\n\n<li><strong>What you can do before December 3.<\/strong> Measure your current consumption against the new meters. Admins can set a monthly extra-usage limit, turn off extra usage per meter, or add a usage pack.<\/li>\n\n\n\n<li><strong>How to optimize your metered features usage.<\/strong> Audit your automation rules, clear obsolete Assets objects, and use free Rovo Search, summaries, and definitions when you don&#8217;t need Chat.<\/li>\n\n\n\n<li><strong>One way to save automation steps.<\/strong> Some Marketplace apps run their own triggers instead of Jira Automation. For instance, <a href=\"https:\/\/marketplace.atlassian.com\/apps\/1216451\/smart-checklists-for-jira\">Smart Checklist for Jira<\/a> imports checklist templates on work item creation, transition, or update.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How Atlassian Pricing Works: Brief Recap<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The key factors influencing Atlassian Cloud bills are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Pricing tier<\/strong>. For instance, Jira and many other Atlassian products have a similar pricing structure, including Free, Standard, Premium, and Enterprise plans. More expensive plans include more features and higher usage allowances.<\/li>\n\n\n\n<li><strong>Billing cycle<\/strong>: monthly or annual. Annual billing usually costs less per seat, but not always. User tiers differ between monthly and annual, so some teams may even pay more on annual.<\/li>\n\n\n\n<li><strong>Number of users.<\/strong> Organizations are billed per user, or per agent for service apps. The per-user rate drops at high user counts, but not smoothly. Atlassian sells in tiers, so crossing a boundary can raise your per-seat cost. Annual plans follow a similar logic, but are billed per user tier.\u00a0<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Additional factors include eligibility for <a href=\"https:\/\/www.atlassian.com\/licensing\/purchase-licensing#does-atlassian-offer-any-discounts\">discounts<\/a> and whether you buy Atlassian products on a standalone basis or as <a href=\"https:\/\/www.atlassian.com\/collections\">collections<\/a> \u2013 the latter offer more favorable bundle pricing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a detailed description of how this system works for Jira, one of the key Atlassian apps, see our<a href=\"https:\/\/titanapps.io\/blog\/jira-pricing\"> Jira pricing guide<\/a>.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Is Atlassian Usage-Based Pricing?<\/h2>\n\n\n\n<section class=\"note\" style=\"background: #fefae9\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Definition<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>Atlassian usage-based pricing is a billing layer that Atlassian added on top of existing Cloud subscriptions. It meters five capabilities: Rovo credits, Automation steps, Assets objects, Bitbucket usage, and Customer Service Management AI agent resolutions. For most meters, you pay extra only once your usage goes beyond the included monthly allowance. Billing for most meters begins December 3, 2026.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<p class=\"wp-block-paragraph\">Note that the <a href=\"https:\/\/www.atlassian.com\/licensing\/future-pricing\/cloud\/list\/pricing-tables\">Cloud price increase on October 13, 2026, <\/a>is a separate change to list prices.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why Is Atlassian Introducing Usage-Based Pricing?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Atlassian&#8217;s stated reason is that seat count no longer tracks the value software delivers. That holds up from the technical point of view. An AI agent resolving a ticket and a multi-step automation flow both consume compute, which varies per interaction. Two organizations on the same plan, with the same headcount, can consume very differently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Atlassian frames the change as giving you more flexibility. You don\u2019t pay a fixed price for features you may never need, instead, you use certain capabilities within limits and, in case you really need more, pay extra. Note, however, that this flexibility comes at a cost: you have to audit, optimize, and monitor your consumption of metered features to put them to best use. Otherwise, you risk wasting your budget or disrupting your workflows when you hit limits without realizing it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How Does Atlassian Usage-Based Pricing Work?<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Most plans include a <strong>monthly allowance.<\/strong> Rovo credits and Automation steps scale with plan tier and seat count. Assets allowances are set per site by plan and edition, then pooled. The usage beyond the allowance is called<strong> extra usage.<\/strong><\/li>\n\n\n\n<li>Atlassian shows your <strong>usage in Atlassian Administration<\/strong>, under Platform usage.\u00a0<\/li>\n\n\n\n<li>Your <strong>allowance refreshes every month and doesn&#8217;t carry over,<\/strong> unused capacity resets.<\/li>\n\n\n\n<li>Your organization and billing <strong>admins get notifications when you reach 80% and 100% of your monthly allowance.<\/strong><\/li>\n\n\n\n<li><strong>You can enable or disable extra usage.<\/strong> It is enabled by default, so nothing stops when you hit your allowance and the overage lands on your next bill. You can turn that off if you would rather pause features than pay. You can also add capacity with a <a href=\"https:\/\/support.atlassian.com\/subscriptions-and-billing\/docs\/manage-usage-packs\/\">usage pack<\/a> or a plan upgrade.\u00a0<\/li>\n\n\n\n<li>Extra usage can be curbed. Organization admins or billing admins can <strong>set a monthly extra-usage limit<\/strong> to keep expenses in check.<\/li>\n\n\n\n<li>Atlassian also has <strong>system limits per meter<\/strong>, like 3 million Assets objects per site or 250,000 CSM AI agent resolutions a month. Reaching one pauses extra usage until your allowance resets or you add capacity.\u00a0<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">The Five Meters at a Glance<\/h3>\n\n\n\n<table id=\"tablepress-118\" class=\"tablepress tablepress-id-118\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Meter<\/th><th class=\"column-2\">What it measures<\/th><th class=\"column-3\">Allowance<\/th><th class=\"column-4\">When will you be billed for usage above allowance<\/th><th class=\"column-5\">Rates<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Rovo credits<\/td><td class=\"column-2\">AI interactions and enriched Teamwork Graph API and tool calls<\/td><td class=\"column-3\">Pooled org-wide; scales with app, edition, and seat count<\/td><td class=\"column-4\">From December 3, 2026<\/td><td class=\"column-5\">$0.01 per credit ($10 per 1,000) - extra usage<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Automation steps<\/td><td class=\"column-2\">Any trigger, condition, action, branch, and loop that runs<\/td><td class=\"column-3\">Pooled org-wide across all apps; counts steps, not rule runs<\/td><td class=\"column-4\">From December 3, 2026<\/td><td class=\"column-5\">$0.50 per 1,000 steps - extra usage<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Assets objects<\/td><td class=\"column-2\">Objects currently stored in your schemas (except system ones)<\/td><td class=\"column-3\">Pooled org-wide; a live count, capped at 3 million objects per site<\/td><td class=\"column-4\">Existing annual customers: billed now. Existing monthly and new customers: from December 3, 2026.<\/td><td class=\"column-5\">0.02 per object per month for the first 100,000 overage objects, $0.01 above that.<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Bitbucket meters<\/td><td class=\"column-2\">Build minutes, Git LFS storage, Packages storage and network transfer<\/td><td class=\"column-3\">Per workspace today, moving to org-wide pooling for monthly plans on October 26, 2026<\/td><td class=\"column-4\">Already billed on monthly plans; annual plans from December 3, 2026<\/td><td class=\"column-5\">$10 per 1,000 build minutes; $10 per 100 GB LFS; Packages at $0.35\/GB storage, $0.70\/GB network<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">CSM AI agent resolutions<\/td><td class=\"column-2\">Customer requests your AI agent resolves without human escalation<\/td><td class=\"column-3\">No included allowance. Usage-based billing defaults to a 25,000-resolution monthly cap you can adjust.<\/td><td class=\"column-4\">From December 3, 2026, starting with the first resolution<\/td><td class=\"column-5\">$1.00 per resolution<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-118 from cache -->\n\n\n\n<h3 class=\"wp-block-heading\">Atlassian Usage-Based Pricing Implementation Timeline<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Atlassian announced usage-based pricing on September 1, 2026. The meters are already running. Billing for most of them starts later. Here are the dates that matter:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"770\" height=\"1024\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-770x1024.png\" alt=\"Timeline of Atlassian usage-based pricing dates, from the September 1, 2026 announcement to extra usage billing on December 3.\" class=\"wp-image-11091\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-770x1024.png 770w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-226x300.png 226w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-768x1021.png 768w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-1155x1536.png 1155w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-18x24.png 18w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-27x36.png 27w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7-36x48.png 36w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-7.png 1540w\" sizes=\"auto, (max-width: 770px) 100vw, 770px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What&#8217;s New in Atlassian&#8217;s Usage-Based Pricing<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Automation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The automation rule runs allowance is replaced with an automation steps allowance. One automation rule can include multiple automation steps (triggers, conditions, loops, etc.). Thus, bundling multiple actions into complex rules is no longer a viable allowance-saving strategy. Let\u2019s consider Jira Cloud as an example to see how the allowance changed:<\/li>\n<\/ul>\n\n\n\n<table id=\"tablepress-119\" class=\"tablepress tablepress-id-119\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Plans<\/th><th class=\"column-2\"><a href=\"https:\/\/web.archive.org\/web\/20260304120512\/https:\/\/www.atlassian.com\/software\/jira\/pricing\">Old allowance<\/a><\/th><th class=\"column-3\"><a href=\"https:\/\/www.atlassian.com\/software\/jira\/pricing\">New allowance<\/a><\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Free<\/td><td class=\"column-2\">100 rule runs per month<\/td><td class=\"column-3\">150 automation steps per subscription per month<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Standard<\/td><td class=\"column-2\">1,700 rule runs per month<\/td><td class=\"column-3\">400 automation steps per user per month<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Premium<\/td><td class=\"column-2\">1,000 rule runs per user per month<\/td><td class=\"column-3\">750 automation steps per user per month<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Enterprise<\/td><td class=\"column-2\">Unlimited<\/td><td class=\"column-3\">1,000 automation steps per user per month<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-119 from cache -->\n\n\n\n<ul class=\"wp-block-list\">\n<li>As the table above suggests, Enterprise Plans lose their unlimited automation runs.<\/li>\n\n\n\n<li>Previously, an automation rule (flow) had to run successfully, i.e., perform at least one action, to count as a run. Now, automation steps are consumed even if a rule is misconfigured, throws errors, or finds nothing to act on.<\/li>\n\n\n\n<li>Before the update, each Atlassian app (Jira, JSM, Confluence, JPD) had its own separate monthly limit. Now the allowance is pooled at the organization level.<\/li>\n\n\n\n<li>Automation usage beyond the allowance becomes billable after December 3, 2026.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Rovo (AI)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Extra usage was an explicit opt-in -> Extra usage is enabled by default.<\/li>\n\n\n\n<li>Previously, Atlassian didn&#8217;t bill for extra usage above your allowance. Starting December 3, extra usage billing takes effect.<\/li>\n\n\n\n<li>The billable-action model changed on August 31, 2026. Previously, Rovo Chat and Rovo Agents cost 10 credits per request, and Deep Research cost 100. Now requests fall into three tiers: Free, Basic, or Premium, where credits scale with reasoning steps, search volume, tools invoked, and the model used.\u00a0<\/li>\n\n\n\n<li>Also, Rovo MCP \/ Teamwork Graph CLI calls now cost credits when returning enriched context, like summarizing a team&#8217;s recent work across Jira, Confluence, Bitbucket, and connected external tools.<\/li>\n\n\n\n<li>Service Collection got 10x more Rovo credits (250 for Standard, 700 for Premium, 1,500 for Enterprise), and now matches Teamwork Collection.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Bitbucket<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Monthly plans.<\/strong> Your allowances move from the workspace to the organization on October 26, 2026. Teams running a single workspace see no practical difference.\u00a0<\/li>\n\n\n\n<li><strong>Annual plans.<\/strong> On December 3, 2026, annual subscriptions will align with monthly ones. Until now, going over your build minutes or Git LFS storage on an annual plan cost you nothing, because you could not buy more. From that date, overage is charged at the published rates. Packages, the artifact management service, is also available to annual customers, and it is metered too.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Assets<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Assets is now available on all paid Jira, JSM, and Service Collection plans, as well as on Teamwork Collection sites.<\/li>\n\n\n\n<li>Before, a multi-site organization needed separate add-on purchases per site. Now allowances are pooled organization-wide.<\/li>\n\n\n\n<li>A new hard per-site cap now exists: 3 million objects.<\/li>\n\n\n\n<li>Atlassian implements extra usage billing via prepaid packs or postpaid metering<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">CSM AI resolutions<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Previously, CSM AI agents were free to use. It is still the case as of September 2026, but starting December 3, 2026, AI resolutions will be billed at $1 each.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How is Usage Calculated?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Automation<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Automation usage measurement unit:<\/strong> an automation step. Each trigger, condition, action, branch, and loop execution across Jira, Confluence, and other Cloud apps counts as one step.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>When do automation steps get charged?<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An automation step does what it was supposed to<\/li>\n\n\n\n<li><strong>An automation step runs but doesn&#8217;t change anything<\/strong><\/li>\n\n\n\n<li>Something in your setup, like a misconfigured rule, causes an error<\/li>\n\n\n\n<li>An automation step was stopped partway through<\/li>\n\n\n\n<li><strong>A trigger checks for something to act on and finds nothing<\/strong><\/li>\n<\/ul>\n\n\n\n<section class=\"note\" style=\"background: #fefae9\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Note<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>To capture every requirement, teams build automation rules that create a subtask per item. Each trigger, condition, action, and branch that runs counts against your automation steps allowance. Boards also fill up with subtasks, which can be overwhelming. <a href=\"https:\/\/marketplace.atlassian.com\/apps\/1216451\/smart-checklists-for-jira\">Smart Checklist for Jira by TitanApps<\/a> keeps those details inside the work item instead. It can <strong>import a checklist template when a work item is created, transitioned, or updated<\/strong>, and you can add conditions on top. These <strong>triggers run in the app, not through Jira Automation<\/strong>, so they do not use automation steps. For setup details, see <a href=\"https:\/\/railsware.atlassian.net\/wiki\/spaces\/CHK\/pages\/1294532651\/Set+a+Template+as+Default#Advanced-Conditions\">Advanced Conditions<\/a>.<\/p>\n<p>Note that Smart Checklist also offers <a href=\"https:\/\/railsware.atlassian.net\/wiki\/spaces\/CHK\/overview#Automation-and-integration-%F0%9F%9A%80\">Jira Automation actions<\/a> if you need them. Those run inside a rule and do count as steps.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<section class=\"banner-block\">\n  <div class=\"banner-block__info\">\n    <h3 class=\"banner-block__title\">Add checklists to your Jira tasks<\/h3>\n    <ul class=\"banner-list\">            <li class=\"banner-list__item\">Add and edit items<\/li>\n                      <li class=\"banner-list__item\">Make recurring templates<\/li>\n                      <li class=\"banner-list__item\">Automate them with your conditions<\/li>\n                      <li class=\"banner-list__item\">Tag colleagues, add deadlines<\/li>\n                      <li class=\"banner-list__item\">View a progress bar<\/li>\n          <\/ul>    <a href=\"https:\/\/marketplace.atlassian.com\/apps\/1216451\/smart-checklist-for-jira-pro?tab=overview&#038;hosting=cloud\" target=\"_blank\" class=\"banner-block__link btn btn-orange\" >Try it free<\/a>\n  <\/div>\n  <div class=\"banner-block__image\">\n    <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/10\/Ui-for-promo-banner.svg\" alt=\"\" width=\"420\" height=\"330\">\n  <\/div>\n<\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What doesn&#8217;t count as an automation step?<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>System and synthetic steps that Atlassian runs on your behalf<\/li>\n\n\n\n<li>Runs that get throttled before any step executes<\/li>\n\n\n\n<li>Errors on Atlassian&#8217;s side, as opposed to problems in your own setup<\/li>\n\n\n\n<li>AI steps like Use Rovo, Use agent, or Use Jira Coding agent, which bill to Rovo credits instead<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Note that a misconfigured rule of yours costs a step every time it runs \u2013 a failure in Atlassian&#8217;s own infrastructure does not.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/support.atlassian.com\/cloud-automation\/docs\/how-is-my-usage-calculated\/\"><strong>Monthly automation steps allowance<\/strong><\/a><\/p>\n\n\n\n<table id=\"tablepress-120\" class=\"tablepress tablepress-id-120\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">App<\/th><th class=\"column-2\">Free (per subscription)<\/th><th class=\"column-3\">Standard (per user)<\/th><th class=\"column-4\">Premium (per user)<\/th><th class=\"column-5\">Enterprise (per user)<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Jira<\/td><td class=\"column-2\">150<\/td><td class=\"column-3\">400<\/td><td class=\"column-4\">750<\/td><td class=\"column-5\">1,000<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Confluence<\/td><td class=\"column-2\">50<\/td><td class=\"column-3\">100<\/td><td class=\"column-4\">250<\/td><td class=\"column-5\">500<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Teamwork Collection<\/td><td class=\"column-2\">200<\/td><td class=\"column-3\">2,500<\/td><td class=\"column-4\">5,000<\/td><td class=\"column-5\">7,500<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">JSM \/ Service Collection<\/td><td class=\"column-2\">1,250<\/td><td class=\"column-3\">3,000<\/td><td class=\"column-4\">6,500<\/td><td class=\"column-5\">9,500<\/td>\n<\/tr>\n<tr class=\"row-6\">\n\t<td class=\"column-1\">Jira Product Discovery<\/td><td class=\"column-2\">100<\/td><td class=\"column-3\">300<\/td><td class=\"column-4\">500<\/td><td class=\"column-5\">750<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-120 from cache -->\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How to calculate your Automation steps allowance<\/strong><\/p>\n\n\n\n<section class=\"note\" style=\"background: #4484bf\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Example<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>An organization has 100 Jira Premium users and 50 Confluence Standard users. Its total monthly automation steps allowance is (100 users * 750 steps\/user) + (50 users * 100 steps\/user) = 80,000 steps.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What happens when you reach your automation steps allowance limit?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With extra usage enabled, starting from December 3, 2026, Atlassian will charge you $0.50 per 1,000 extra steps on your next invoice. If not, rules stop running until your allowance resets.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Find more details in <a href=\"https:\/\/support.atlassian.com\/cloud-automation\/docs\/how-is-my-usage-calculated\/\">How is your automation usage calculated<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Rovo Usage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Rovo usage measurement unit:<\/strong> Rovo credit. An AI interaction and an enriched Teamwork Graph API call consume credits. With enriched TWG API and tool calls, Rovo relies on context from across your Atlassian and external apps to satisfy complex queries.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>When do Rovo credits get charged?<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You ask a basic question in Rovo Chat&#8217;s Quick Answer mode or run a basic Agent, at a flat 10 credits per event<\/li>\n\n\n\n<li>You use Think Deeper mode, Jira Coding Agent, Confluence Slides, or another Premium AI feature. The number of credits varies based on complexity<\/li>\n\n\n\n<li>You make an enriched Teamwork Graph API or tool call, like through the Teamwork Graph CLI or Rovo MCP. Typically, that costs 1 to 10 credits per call<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Which interactions do not consume Rovo Credits?<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Rovo Search in Atlassian apps<\/li>\n\n\n\n<li>Summaries<\/li>\n\n\n\n<li>Definitions<\/li>\n\n\n\n<li>Installing Teamwork Graph CLI and Atlassian Rovo MCP<\/li>\n\n\n\n<li>Single product context request, e.g., looking up a Confluence page\u2019s content.<\/li>\n\n\n\n<li>Write operations, e.g., updating a Jira work item<\/li>\n<\/ul>\n\n\n\n<section class=\"note\" style=\"background: #fefae9\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Note<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>This credit model took effect on August 31, 2026.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Rovo credit allowance, measured in credits per user per month<\/strong><\/p>\n\n\n\n<table id=\"tablepress-121\" class=\"tablepress tablepress-id-121\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">App<\/th><th class=\"column-2\">Standard<\/th><th class=\"column-3\">Premium<\/th><th class=\"column-4\">Enterprise<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Jira<\/td><td class=\"column-2\">25<\/td><td class=\"column-3\">70<\/td><td class=\"column-4\">150<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Confluence<\/td><td class=\"column-2\">25<\/td><td class=\"column-3\">70<\/td><td class=\"column-4\">150<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Service Collection<\/td><td class=\"column-2\">250<\/td><td class=\"column-3\">700<\/td><td class=\"column-4\">1,500<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">Teamwork Collection<\/td><td class=\"column-2\">250<\/td><td class=\"column-3\">700<\/td><td class=\"column-4\">1,500<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-121 from cache -->\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How to calculate your<\/strong> <strong>Rovo credit allowance<\/strong><\/p>\n\n\n\n<section class=\"note\" style=\"background: #4484bf\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Example<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>For an organization with 100 Jira Premium users and 50 Confluence Standard users, the total monthly Rovo credit allowance is (100 users * 70 credits\/user) + (50 users * 25 credits\/user) = 8,250 credits.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What happens when you reach your Rovo credits allowance limit?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Extra usage is enabled by default for Rovo credits, so you keep using Rovo up to any admin-specified limit, and Atlassian bills you $0.01 per credit on your next invoice. If you turn extra usage off, new credit-consuming AI features and enriched Teamwork Graph calls pause until your allowance resets. Free features, like Rovo Search, summaries, or definitions, keep working either way.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For more information, see <a href=\"https:\/\/support.atlassian.com\/rovo\/docs\/rovo-usage-limits\/\">How Rovo credits work<\/a> in Atlassian documentation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Assets<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What Is Assets?<\/strong><\/p>\n\n\n\n<section class=\"note\" style=\"background: #fefae9\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Definition<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>Assets is Atlassian&#8217;s feature for tracking anything that matters to your business, like services, employees, vendors, contracts, locations, and equipment, and connecting it to the work you do. Assets is included with Jira, Jira Service Management\/Service Collection, and Teamwork Collection paid plans.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Assets usage measurement unit:<\/strong> Assets object. Everything you track \u2013 a laptop, server, contract, etc. \u2013 is stored as an object<strong>.<\/strong> Each object carries attributes that describe it, like an owner, a status, or a renewal date. References link objects to each other, like a vendor to the service it supplies.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How is Assets usage calculated?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Assets works differently from Automation and Rovo. <strong>Your usage is the total number of objects across all sites in your organization<\/strong> (excluding system schemas). You change it by adjusting how many objects you keep. Deleted objects and sandbox objects don\u2019t count. The system limit is 3 million objects per site. For other technical limits, see <a href=\"https:\/\/support.atlassian.com\/assets\/docs\/increase-the-usage-limit-for-assets\/\">Manage Assets usage and limits<\/a>.<\/p>\n\n\n\n<section class=\"note\" style=\"background: #fefae9\">\n  <div class=\"note-heading\">\n    <img loading=\"lazy\" decoding=\"async\" width=\"44\" height=\"44\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png\" class=\"note-heading__image\" alt=\"\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note.png 44w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-24x24.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2024\/08\/note-36x36.png 36w\" sizes=\"auto, (max-width: 44px) 100vw, 44px\" \/>    <span class=\"note__label\">Note<\/span>\n  <\/div>\n      <div class=\"note__text\">\n        <p>System schemas are used by other features to store information, like Services. Note that Atlassian&#8217;s <a href=\"https:\/\/support.atlassian.com\/assets\/docs\/what-is-feature-usage-and-how-it-works\/\">support page on object usage<\/a> mentions system schemas in general as excluded from usage, and <a href=\"https:\/\/www.atlassian.com\/licensing\/assets#assets-objects-what-counts\">Pricing FAQ<\/a> describes a narrower exclusion, so check your actual count in Platform usage.<\/p>\n    <\/div>\n  <\/section>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Assets object allowance, measured in objects per organization<\/strong><\/p>\n\n\n\n<table id=\"tablepress-122\" class=\"tablepress tablepress-id-122 tbody-has-connected-cells\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Plan<\/th><th class=\"column-2\">Standard<\/th><th class=\"column-3\">Premium<\/th><th class=\"column-4\">Enterprise*<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Jira<\/td><td class=\"column-2\">1,000<\/td><td class=\"column-3\">1,000<\/td><td class=\"column-4\">1,000<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Jira Service Management \/ Service Collection<\/td><td class=\"column-2\">5,000<\/td><td class=\"column-3\">50,000<\/td><td class=\"column-4\">500,000<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Teamwork Collection<\/td><td class=\"column-2\">5,000<\/td><td class=\"column-3\">5,000<\/td><td class=\"column-4\">5,000<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td colspan=\"4\" class=\"column-1\">*For an Enterprise organization, allowances do not accumulate across sites. An allowance is available per subscription, not per site.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-122 from cache -->\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What happens when you reach your Assets allowance limit?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you go over your allowance with extra usage enabled, you keep adding objects without interruption. Atlassian bills you $0.02 per object per month, dropping to $0.01 for overage objects beyond 100,000. If extra usage is off, you can&#8217;t add new objects unless you buy an object pack.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Assets billing dates depend on your plan. Existing annual customers keep billing as before. Existing monthly customers and anyone who started using Assets after September 1, 2026 begin on December 3, 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">More details in <a href=\"https:\/\/support.atlassian.com\/assets\/docs\/what-is-feature-usage-and-how-it-works\/\">How Assets object usage works<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Bitbucket<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Bitbucket usage measurement units:<\/strong>&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build minutes \u2013 CI\/CD pipeline execution time.<\/li>\n\n\n\n<li>Gigabytes of Git Large File Storage (LFS). Large files sit in storage parallel to your code, with lightweight references in the repository. Useful for teams working with video and other large media.<\/li>\n\n\n\n<li>Gigabytes of Bitbucket Packages storage and network usage to publish, manage, and consume artifacts (read more in <a href=\"https:\/\/support.atlassian.com\/bitbucket-cloud\/docs\/set-up-and-use-packages\/\">Set up and use packages<\/a>)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Bitbucket allowance, measured per workspace*<\/strong><\/p>\n\n\n\n<table id=\"tablepress-123\" class=\"tablepress tablepress-id-123\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Plan<\/th><th class=\"column-2\">Build Minutes (per month)<\/th><th class=\"column-3\">Git LFS Storage<\/th><th class=\"column-4\">Packages: Storage limit<\/th><th class=\"column-5\">Packages: Network Transfer<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Free<\/td><td class=\"column-2\">50<\/td><td class=\"column-3\">1 GB<\/td><td class=\"column-4\">-<\/td><td class=\"column-5\">-<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">Standard<\/td><td class=\"column-2\">2,500<\/td><td class=\"column-3\">5 GB<\/td><td class=\"column-4\">1GB<\/td><td class=\"column-5\">5GB<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">Premium<\/td><td class=\"column-2\">3,500<\/td><td class=\"column-3\">10 GB<\/td><td class=\"column-4\">2GB<\/td><td class=\"column-5\">7GB<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-123 from cache -->\n\n\n\n<p class=\"wp-block-paragraph\">*Monthly plans move from workspace-level to organization-level allowances on October 26, 2026. Annual plans start working like monthly ones on December 3.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What happens when you reach your Bitbucket allowance limit?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you go over your allowance on Standard or Premium, Atlassian bills you $10 per 1,000 extra build minutes that month. Storage overage recurs every month you hold the data: $10 per 100 GB of extra LFS, $0.35 per GB for Packages storage, and $0.70 per GB of network transfer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a detailed description of how Bitbucket usage is metered, check out <a href=\"https:\/\/support.atlassian.com\/bitbucket-cloud\/docs\/manage-your-plan-and-billing\/\">Manage your plan and billing<\/a> in the Bitbucket Cloud documentation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Customer Service Management<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer Service Management (CSM) usage measurement unit:<\/strong> CSM AI agent resolution. One conversation resolved without human involvement equals one resolution. Not available on the Free plan.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>When do CSM AI agent resolutions get charged?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your agent answers the customer&#8217;s question in full, and the conversation never passes to a human on your team. Also, Atlassian&#8217;s LLM judge rates the conversation as resolved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>CSM AI agent resolution allowance<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Unlike every other meter mentioned above, <strong>CSM has no included allowance<\/strong>. It doesn\u2019t matter until December 3, 2026 \u2013 after that date, you will be billed at $1.00 per resolution, starting with your first one. You can choose usage-based billing, resolution packs, or a combination of both.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With <strong>usage-based billing<\/strong>, you pay for what you used the previous month. The default usage-based billing limit is 25,000 resolutions a month. You can adjust it in Atlassian Administration, with a hard system ceiling of 250,000.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With resolution packs, you buy resolutions in advance. On monthly plans, they become that month&#8217;s allowance. On annual plans, the total is divided evenly across twelve months.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Resolution pack pricing for annual plans<\/strong><\/p>\n\n\n\n<table id=\"tablepress-124\" class=\"tablepress tablepress-id-124\">\n<thead>\n<tr class=\"row-1\">\n\t<th class=\"column-1\">Pack Volume<\/th><th class=\"column-2\">Discount<\/th><th class=\"column-3\">Net Price per Resolution<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"row-striping row-hover\">\n<tr class=\"row-2\">\n\t<td class=\"column-1\">Under 12,000<\/td><td class=\"column-2\">0%<\/td><td class=\"column-3\">$1.00<\/td>\n<\/tr>\n<tr class=\"row-3\">\n\t<td class=\"column-1\">12,000-49,999<\/td><td class=\"column-2\">5%<\/td><td class=\"column-3\">$0.95<\/td>\n<\/tr>\n<tr class=\"row-4\">\n\t<td class=\"column-1\">50,000-199,999<\/td><td class=\"column-2\">10%<\/td><td class=\"column-3\">$0.90<\/td>\n<\/tr>\n<tr class=\"row-5\">\n\t<td class=\"column-1\">200,000+<\/td><td class=\"column-2\">15%<\/td><td class=\"column-3\">$0.85<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<!-- #tablepress-124 from cache -->\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What happens when you reach your AI resolutions limit?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By default, usage-based billing tops up whatever your packs don&#8217;t cover. If you&#8217;d rather cap your spend at your resolution packs, you can disable usage-based billing. When you exhaust your packs and reach the monthly usage-based limit, the agent stops resolving directly. Instead, it tells the customer it&#8217;s raising a request on their behalf and automatically creates a work item using your default form.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For more information, check <a href=\"https:\/\/support.atlassian.com\/customer-service-management\/docs\/manage-usage-for-ai-agent-resolutions\/\">Manage usage for AI agent resolutions.<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Should You Do Before December 3?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1. Assess your metered capabilities consumption<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">There is no pressure to act immediately, if you should act at all. Atlassian gave you a window from September 1 to December 3 to measure your usage and decide what to do. Platform usage in Atlassian Administration shows what you are consuming now. Atlassian&#8217;s <a href=\"https:\/\/www.atlassian.com\/resources\/usage\/calculator\">usage calculator<\/a> estimates what you&#8217;ll likely need based on organization size, plan tier, and expected usage.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Steps 2. Optimize your usage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Even if your assessment shows metered features are unlikely to affect your Atlassian bill, it may be prudent to adjust how you use them.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Audit your automation rules.<\/strong> Automation steps are charged regardless of whether a rule has configuration problems or doesn\u2019t change anything. With the new usage-based pricing, rules that trigger and do nothing cost a step each time. A misconfigured rule that runs its full path costs a step for every step it executes.<\/li>\n\n\n\n<li><strong>Check whether your Atlassian Marketplace apps can do the job natively.<\/strong> Marketplace apps that react to Jira events through their own triggers don&#8217;t run inside an automation flow, so that work sits outside the steps meter. Smart Checklist for Jira, for example, can apply checklist templates on work item creation, transition, or update without Jira Automation.<\/li>\n<\/ul>\n\n\n\n<section class=\"banner-block\">\n  <div class=\"banner-block__info\">\n    <h3 class=\"banner-block__title\">Add checklists to your Jira tasks<\/h3>\n    <ul class=\"banner-list\">            <li class=\"banner-list__item\">Add and edit items<\/li>\n                      <li class=\"banner-list__item\">Make recurring templates<\/li>\n                      <li class=\"banner-list__item\">Automate them with your conditions<\/li>\n                      <li class=\"banner-list__item\">Tag colleagues, add deadlines<\/li>\n                      <li class=\"banner-list__item\">View a progress bar<\/li>\n          <\/ul>    <a href=\"https:\/\/marketplace.atlassian.com\/apps\/1216451\/smart-checklist-for-jira-pro?tab=overview&#038;hosting=cloud\" target=\"_blank\" class=\"banner-block__link btn btn-orange\" >Try it free<\/a>\n  <\/div>\n  <div class=\"banner-block__image\">\n    <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2025\/10\/Ui-for-promo-banner.svg\" alt=\"\" width=\"420\" height=\"330\">\n  <\/div>\n<\/section>\n\n\n\n<ul start=\"3\" class=\"wp-block-list\">\n<li><a href=\"https:\/\/support.atlassian.com\/assets\/docs\/optimize-your-schemas-for-usage\/\"><strong>Optimize your schemas in Assets<\/strong><\/a><strong>. <\/strong>Review your schemas regularly and clear out obsolete assets and duplicates. Linking related objects with references, instead of repeating data across object types, keeps the count down.<\/li>\n\n\n\n<li><strong>Revise your workflows to use Rovo tools cost-effectively.<\/strong> Rovo Chat can find you a necessary file, write a summary, or provide a definition, but each message consumes credits. Built-in search, summaries, and definitions, by contrast, are free. See the screenshot below as an example: both paths yield the same result, yet the one on the left, via Chat, costs 10 credits while the other, via Search, costs nothing:<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"549\" src=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-1024x549.png\" alt=\"Side-by-side screenshot of Rovo Chat and Rovo Search in Confluence returning the same product requirements page.\" class=\"wp-image-11092\" srcset=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-1024x549.png 1024w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-300x161.png 300w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-768x411.png 768w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-1536x823.png 1536w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-24x13.png 24w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-36x19.png 36w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8-48x26.png 48w, https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/image-8.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<ul start=\"5\" class=\"wp-block-list\">\n<li><strong>Test CSM AI agents in the dedicated test panel or through evaluations, not live channels.<\/strong> Testing there costs nothing. Testing in a live channel is charged like a real customer conversation.\u00a0<\/li>\n\n\n\n<li><strong>Know what your sandbox costs. <\/strong>Rovo credits and Automation steps both <a href=\"https:\/\/www.atlassian.com\/licensing\/usage-based-pricing#sandbox-usage\">count sandbox usage against your allowance<\/a>. Assets objects do not.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Consider your strategy<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>If your usage falls well inside the allowance your plans provide<\/strong> for Rovo credits, Automation steps, Assets objects, and Bitbucket, they won\u2019t affect your Atlassian bill after December 3. Customer Service Management, however, has no allowance, and every AI agent resolution will cost $1.00 after that date. Decide whether you need the feature and, if you do, budget for extra expense based on your usage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>If, even with optimized usage, you are likely to reach your limits or go beyond,<\/strong> you have several choices:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Turn on extra usage<\/strong> where you want to pay as you go. You may also want to set admin limits on extra usage as a safeguard. This fits best for teams with small, unpredictable overages and a willingness to extend their Atlassian budget.<\/li>\n\n\n\n<li><strong>Turn off extra usage per meter<\/strong> if your Atlassian budget has a hard cap and pausing metered features is acceptable.<\/li>\n\n\n\n<li><strong>Upgrade to a higher plan tier or a Collection for a permanently larger allowance.<\/strong> Enterprise plans and Collections include substantially higher allowances than standalone apps at the same plan tier. For instance, Teamwork Collection carries five times the Rovo credits and automation steps of Jira and Confluence bought separately, at every tier.\u00a0<\/li>\n\n\n\n<li><strong>Buy prepaid usage packs to fix your cost in advance<\/strong>. Annual usage packs are available now. Monthly usage packs and <a href=\"https:\/\/www.atlassian.com\/licensing\/usage-based-pricing#difference-between-usage-and-committed-packs\">committed packs<\/a> are still coming.\u00a0<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions about Atlassian Usage-Based Pricing&nbsp;<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does usage-based pricing affect Data Center?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Usage-based pricing is scoped to Atlassian Cloud. Atlassian&#8217;s support documentation describes it as a layer on Cloud subscriptions, and its <a href=\"https:\/\/www.atlassian.com\/licensing\/usage-based-pricing#understanding%20usage-based-pricing\">usage-based pricing FAQ<\/a> lists allowances only for Cloud apps and collections such as Jira, Confluence, and Bitbucket. Data Center is not among them.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does usage-based pricing replace seat-based pricing?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Your seat costs and renewal process are unchanged. Usage-based pricing adds a consumption layer on top, covering Rovo credits, Automation steps, Assets objects, Bitbucket meters, and CSM AI agent resolutions. You pay for those only when you go past your included allowance. Customer Service Management has no allowance, so you&#8217;re charged for every AI agent resolution.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I limit usage so it doesn&#8217;t go over?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Extra usage is enabled by default for most organizations, so this is something you turn off rather than turn on. Disabling it stops all extra usage charges for that meter, and the capability pauses once you hit 100% of your allowance. Setting a usage limit instead lets extra usage continue up to a cap you choose. Both settings apply per meter, so you can cap Rovo credits while leaving Automation steps uncapped. You&#8217;ll find them in Atlassian Administration, under Billing or under Insights and then Platform usage. Note that automation events occurring while your flows are stopped won&#8217;t restart when the allowance refreshes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What happens to unused allowance?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It expires. Your included <strong>allowance resets monthly<\/strong>, and any unused portion doesn&#8217;t carry over. Annual plans work the same way here. You get a fresh monthly allowance rather than a year&#8217;s worth to spend as you like. <strong>Usage packs<\/strong> follow the same rule: unused capacity resets at the start of each monthly billing period. <strong>Committed packs<\/strong> (annual only) are the exception. They hold a prepaid balance that depletes as you use it rather than refreshing each month, and anything left expires at the end of the 12-month commitment period. Atlassian lists monthly usage packs and committed packs as coming soon, with availability planned by December 3, 2026.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What uses Rovo Credits?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Rovo credits are consumed by two types of billable events: AI interactions and enriched Teamwork Graph (TWG) calls. Rovo Chat&#8217;s Quick Answer mode and basic Agents cost 10 credits per event. Premium AI features, like Think Deeper mode and the Jira Coding Agent, cost a variable number of credits based on complexity. Atlassian publishes indicative ranges rather than a per-feature rate. To see what a feature actually costs you, run it and check Platform usage. You can also export the usage CSV for a per-feature breakdown. Enriched TWG API and tool calls typically cost 1 to 10 credits per call. You make these calls through the Teamwork Graph CLI or Rovo MCP. Rovo Search, definitions, summaries, chart insights, single-product context lookups, and write operations stay free.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How does Atlassian&#8217;s usage-based pricing work for Confluence?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Confluence uses Rovo credits and Automation steps. The Free plan includes 50 automation steps per month for the entire subscription. Paid plans move to a per-user allowance: 100 on Standard, 250 on Premium, and 500 on Enterprise. Its Rovo credit allowance follows the same rate as Jira: 25 on Standard, 70 on Premium, and 150 on Enterprise. Both allowances pool at the organization level alongside every other eligible app you run. Confluence has the smallest automation allowance of any app. Standard gives 100 steps per user, compared to 400 for Jira.<\/p>\n\n\n\n<section class=\"writer\">\n  <div class=\"writer__image\">\n    <img alt='Anton Mazur' src='https:\/\/secure.gravatar.com\/avatar\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=180&#038;d=identicon&#038;r=g' srcset='https:\/\/secure.gravatar.com\/avatar\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=360&#038;d=identicon&#038;r=g 2x' class='avatar avatar-180 photo' height='180' width='180' \/>  <\/div>\n\n  <div class=\"writer-data\">\n    <span class=\"writer-data__label\">Article by<\/span>\n    <span class=\"writer-data__name\">\n      Anton Mazur    <\/span>\n    <div class=\"writer-data__bio\">\n      Technical Content Writer at TitanApps. I have 5+ years of experience making complex tech topics clear and compelling for business audiences. I&#8217;ve written about custom software, cloud, AI, IoT, and cybersecurity. Before moving into content, I spent years in social research and data analysis &#8211; and that analytical mindset still shapes how I approach every piece I write.    <\/div>\n\n      <\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>On September 1, 2026, Atlassian announced an expanded usage-based pricing model for its Cloud apps. Rovo credits, Automation steps, and AI agent resolutions will become billable for the first time. Assets and Bitbucket already bill on usage for some customers, and their terms change too. This article explains how each meter works, when the changes [&hellip;]<\/p>\n","protected":false},"author":181780141,"featured_media":11115,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1401,1405,1416,1453,1409],"tags":[],"coauthors":[1480],"class_list":["post-11090","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-article","category-atlassian-jira","category-it-engineering","category-procurement","category-smart-checklist"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Atlassian Usage-Based Pricing: How to Control Your Bill<\/title>\n<meta name=\"description\" content=\"Atlassian usage-based pricing meters Rovo, Automation, Assets, Bitbucket, and CSM AI agents. Learn what changed and what you can do about it.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Atlassian Usage-Based Pricing: How to Control Your Bill\" \/>\n<meta property=\"og:description\" content=\"Atlassian usage-based pricing meters Rovo, Automation, Assets, Bitbucket, and CSM AI agents. Learn what changed and what you can do about it.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained\" \/>\n<meta property=\"og:site_name\" content=\"Titanapps\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-15T14:53:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-15T15:10:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/113-Usage-Based-Pricing-Explained.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1440\" \/>\n\t<meta property=\"og:image:height\" content=\"960\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Anton Mazur\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Anton Mazur\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained\"},\"author\":{\"name\":\"Anton Mazur\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/#\\\/schema\\\/person\\\/34727591bf1bcb2447d6df208d8942ad\"},\"headline\":\"Atlassian Usage-Based Pricing Explained\",\"datePublished\":\"2026-09-15T14:53:05+00:00\",\"dateModified\":\"2026-09-15T15:10:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained\"},\"wordCount\":3675,\"image\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/113-Usage-Based-Pricing-Explained.png\",\"articleSection\":[\"Article\",\"Atlassian, Jira\",\"IT\\\/Engineering\",\"Procurement\",\"Smart Checklist\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained\",\"url\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained\",\"name\":\"Atlassian Usage-Based Pricing: How to Control Your Bill\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/113-Usage-Based-Pricing-Explained.png\",\"datePublished\":\"2026-09-15T14:53:05+00:00\",\"dateModified\":\"2026-09-15T15:10:36+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/#\\\/schema\\\/person\\\/34727591bf1bcb2447d6df208d8942ad\"},\"description\":\"Atlassian usage-based pricing meters Rovo, Automation, Assets, Bitbucket, and CSM AI agents. Learn what changed and what you can do about it.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#primaryimage\",\"url\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/113-Usage-Based-Pricing-Explained.png\",\"contentUrl\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/113-Usage-Based-Pricing-Explained.png\",\"width\":1440,\"height\":960,\"caption\":\"Traveler pays a coin at an Atlassian toll gate under a full usage meter, illustrating usage-based pricing.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/atlassian-usage-based-pricing-explained#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Atlassian Usage-Based Pricing Explained\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/\",\"name\":\"Titanapps\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/titanapps.io\\\/blog\\\/#\\\/schema\\\/person\\\/34727591bf1bcb2447d6df208d8942ad\",\"name\":\"Anton Mazur\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=96&d=identicon&r=gdaa8f960952a89d160c7a6f3a74a1664\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=96&d=identicon&r=g\",\"caption\":\"Anton Mazur\"},\"description\":\"Technical Content Writer at TitanApps. I have 5+ years of experience making complex tech topics clear and compelling for business audiences. I've written about custom software, cloud, AI, IoT, and cybersecurity. Before moving into content, I spent years in social research and data analysis - and that analytical mindset still shapes how I approach every piece I write.\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Atlassian Usage-Based Pricing: How to Control Your Bill","description":"Atlassian usage-based pricing meters Rovo, Automation, Assets, Bitbucket, and CSM AI agents. Learn what changed and what you can do about it.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained","og_locale":"en_US","og_type":"article","og_title":"Atlassian Usage-Based Pricing: How to Control Your Bill","og_description":"Atlassian usage-based pricing meters Rovo, Automation, Assets, Bitbucket, and CSM AI agents. Learn what changed and what you can do about it.","og_url":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained","og_site_name":"Titanapps","article_published_time":"2026-09-15T14:53:05+00:00","article_modified_time":"2026-09-15T15:10:36+00:00","og_image":[{"width":1440,"height":960,"url":"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/113-Usage-Based-Pricing-Explained.png","type":"image\/png"}],"author":"Anton Mazur","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Anton Mazur","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#article","isPartOf":{"@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained"},"author":{"name":"Anton Mazur","@id":"https:\/\/titanapps.io\/blog\/#\/schema\/person\/34727591bf1bcb2447d6df208d8942ad"},"headline":"Atlassian Usage-Based Pricing Explained","datePublished":"2026-09-15T14:53:05+00:00","dateModified":"2026-09-15T15:10:36+00:00","mainEntityOfPage":{"@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained"},"wordCount":3675,"image":{"@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#primaryimage"},"thumbnailUrl":"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/113-Usage-Based-Pricing-Explained.png","articleSection":["Article","Atlassian, Jira","IT\/Engineering","Procurement","Smart Checklist"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained","url":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained","name":"Atlassian Usage-Based Pricing: How to Control Your Bill","isPartOf":{"@id":"https:\/\/titanapps.io\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#primaryimage"},"image":{"@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#primaryimage"},"thumbnailUrl":"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/113-Usage-Based-Pricing-Explained.png","datePublished":"2026-09-15T14:53:05+00:00","dateModified":"2026-09-15T15:10:36+00:00","author":{"@id":"https:\/\/titanapps.io\/blog\/#\/schema\/person\/34727591bf1bcb2447d6df208d8942ad"},"description":"Atlassian usage-based pricing meters Rovo, Automation, Assets, Bitbucket, and CSM AI agents. Learn what changed and what you can do about it.","breadcrumb":{"@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#primaryimage","url":"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/113-Usage-Based-Pricing-Explained.png","contentUrl":"https:\/\/titanapps.io\/blog\/wp-content\/uploads\/2026\/09\/113-Usage-Based-Pricing-Explained.png","width":1440,"height":960,"caption":"Traveler pays a coin at an Atlassian toll gate under a full usage meter, illustrating usage-based pricing."},{"@type":"BreadcrumbList","@id":"https:\/\/titanapps.io\/blog\/atlassian-usage-based-pricing-explained#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/titanapps.io\/blog\/"},{"@type":"ListItem","position":2,"name":"Atlassian Usage-Based Pricing Explained"}]},{"@type":"WebSite","@id":"https:\/\/titanapps.io\/blog\/#website","url":"https:\/\/titanapps.io\/blog\/","name":"Titanapps","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/titanapps.io\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/titanapps.io\/blog\/#\/schema\/person\/34727591bf1bcb2447d6df208d8942ad","name":"Anton Mazur","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=96&d=identicon&r=gdaa8f960952a89d160c7a6f3a74a1664","url":"https:\/\/secure.gravatar.com\/avatar\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9f3b067e4a2cd64b0373cb4af497b4c0cdbb09b71351a162fa01bf50803f02a5?s=96&d=identicon&r=g","caption":"Anton Mazur"},"description":"Technical Content Writer at TitanApps. I have 5+ years of experience making complex tech topics clear and compelling for business audiences. I've written about custom software, cloud, AI, IoT, and cybersecurity. Before moving into content, I spent years in social research and data analysis - and that analytical mindset still shapes how I approach every piece I write."}]}},"article_bg":"#D0EACA","_links":{"self":[{"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/posts\/11090","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/users\/181780141"}],"replies":[{"embeddable":true,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/comments?post=11090"}],"version-history":[{"count":17,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/posts\/11090\/revisions"}],"predecessor-version":[{"id":11128,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/posts\/11090\/revisions\/11128"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/media\/11115"}],"wp:attachment":[{"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/media?parent=11090"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/categories?post=11090"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/tags?post=11090"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/titanapps.io\/blog\/wp-json\/wp\/v2\/coauthors?post=11090"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}