Atlassian Is Changing How You Pay for Usage: What You Need to Know

Key Takeaways

• Atlassian is expanding usage-based pricing on December 3, 2026. Existing subscriptions remain, but certain AI, automation, Assets, service management, and Bitbucket capabilities will now include metered usage.
• Extra usage is enabled by default. Organizations that exceed their included allowances may incur additional charges unless administrators disable overages or establish usage limits.
• Admins should start monitoring consumption now. Atlassian’s Platform usage dashboard can help teams establish baselines, identify high-usage teams, forecast future consumption, and avoid unexpected costs.
• Occasional and sustained overages require different strategies. Usage packs or pay-as-you-go pricing may make sense for temporary spikes, while consistently high usage may justify a broader licensing change.
• Heavy Rovo users should evaluate Teamwork Collection. It provides 10x more Rovo credits per user than standalone Jira or Confluence plans at the corresponding tier, potentially making it more economical as AI adoption grows.

Atlassian announced a significant expansion of its usage-based pricing model on September 1, 2026.  Beginning December 3, 2026, most affected capabilities will have allowances included with your existing subscription, but organizations that exceed those allowances may incur additional charges.  For Atlassian customers, this doesn’t mean everything is suddenly moving from seat-based licensing to consumption pricing.  Your existing subscriptions remain in place.  What’s changing is that certain AI, automation, service management, Assets, and Bitbucket capabilities will have a usage layer on top of the subscription.  That makes the next three months important.  Atlassian administrators should understand what is being metered, review how much their organization is actually consuming, and decide how they want to handle occasional versus sustained usage above their included allowances.

What is Atlassian Changing?

Atlassian’s new model introduces meters that track consumption of specific capabilities.  Your subscription includes an allowance, and those allowances are pooled at the organization level and refreshed each billing period.

The affected areas include:

For most meters, the new billing model takes effect December 3, 2026, although Atlassian notes that timing can vary based on the capability and billing cadence.  One important point is that Atlassian isn’t waiting until December to give administrators visibility. Organizations can review usage through Atlassian Administration → Insights → Platform usage, including current consumption and historical trends.  Admins will also receive notifications when usage approaches 80% and 100% of an allowance or configured limit.

What Happens When You Exceed Your Atlassian Allowance?

This is where Atlassian customers need to pay attention.  Extra usage is enabled by default. If your organization exceeds its included allowance, usage can continue, and the additional consumption will be billed in arrears at the applicable rate. Administrators can instead disable extra usage or establish limits.  If extra usage is disabled and the allowance is exhausted, the affected metered capability pauses until the allowance refreshes or additional capacity is added.  Other meters continue operating.

Atlassian applies capacity in this order: your included allowance is consumed first, followed by any prepaid usage packs, and then extra usage.  This gives customers several ways to approach the change depending on how predictable their usage is.

Going Over Once? Usage Packs May Make Sense

Not every organization that exceeds its allowance needs to change its Atlassian licensing.  Maybe a development team has a particularly automation-heavy month.  Perhaps a new Rovo rollout temporarily drives higher AI consumption, or a business initiative creates a short-term increase in usage.

For those situations, Atlassian is introducing usage packs, which allow customers to purchase additional capacity without making a broader change to their subscription.  Usage packs are currently available for Rovo credits, Customer Service Management AI resolutions, and Automation steps.  Monthly packs provide additional allowance for a billing period, but unused capacity does not roll over. Atlassian is also planning committed packs that provide an annual prepaid balance that can be consumed more flexibly throughout the year.

For Rovo specifically, the current extra-usage list price is $0.01 per credit, or $10 per 1,000 credits.  Prepaid packs are also available, with volume discounts possible for annual commitments.

That means occasional overages don’t necessarily require a major licensing change.  If your usage spikes once or twice, paying for extra usage or purchasing a usage pack may be the simplest answer.  But if you’re consistently approaching or exceeding your allowance, the calculation changes.

Heavy Rovo Users Should Look Closely at Teamwork Collection

Rovo is likely to be one of the areas where customers notice this change most.  Rovo credits measure usage of many AI-powered capabilities, including Rovo Chat, agents, Confluence Slides, Jira Coding Agent, and enriched Teamwork Graph interactions. Some embedded AI functionality, including summaries, definitions, and Rovo Search in Atlassian apps, remains free.  The amount of Rovo capacity included with your subscription varies considerably depending on what you own.

That’s 10x the Rovo credit allowance per user at the corresponding plan level.  This is where organizations should look beyond the immediate question of, “How much will our Rovo overage cost?”

If Rovo is becoming part of how employees work every day, repeatedly purchasing additional credits may not be the best long-term answer. Moving to Teamwork Collection could provide substantially more Rovo capacity while also changing the economics of the broader Atlassian environment.

Teamwork Collection includes Jira, Confluence, Loom and Rovo under a single subscription.  Depending on the tier, it also provides increased automation allowances and other capabilities.  Also, Premium and Enterprise include Atlassian Guard Standard for free.

For organizations already licensing several of these products separately, the right comparison isn’t simply:

Rovo overage cost vs. Teamwork Collection cost.

It should be:

Current Jira + Confluence + Loom + other relevant Atlassian costs + expected usage charges vs. Teamwork Collection.

That can produce a very different answer.

What Atlassian Admins Should Do Before December 3rd, 2026

Don’t wait for the first unexpected usage bill.  Between now and December 3rd, administrators should use Atlassian’s Platform usage dashboard to establish a baseline for Rovo, automation, Assets, and other applicable meters.  Look at which users and teams are driving consumption and whether usage appears to be occasional, seasonal, or steadily increasing.  Then decide how you want Atlassian to behave when an allowance is reached.  Atlassian allows admins to enable or disable extra usage and establish ceilings. Forecasting tools can also project usage based on historical trends.  From there, the financial decision becomes much easier:

SPK Can Help Your Atlassian Cloud License Costs

Your team shouldn’t have to restrict useful automation or AI simply because you’re worried about an unexpected bill.  Instead, understand your consumption and select the licensing model that matches how your teams actually work.

SPK and Associates can help Atlassian customers review their current licenses, analyze expected usage, establish appropriate usage controls, and compare the cost of pay-as-you-go usage, usage packs, plan upgrades, and Teamwork Collection.  With the December 3 deadline approaching, now is a good time to run that analysis.  In particular, if your organization is already using Rovo heavily or expects AI adoption to grow over the next year, the 10x Rovo allowance available through Teamwork Collection deserves a closer look.  Contact our team for a review of your current utilization and learn how we can help.