Atlassian is expanding its usage-based pricing model to better align the cost of AI and other high-value platform capabilities with how organizations actually use them.

Announced September 1, 2026, the expanded model introduces usage meters for capabilities including: Rovo credits, Automation steps, Assets objects, AI agent resolutions, and Bitbucket usage. (For most meters, usage-based billing will begin December 3, 2026.)

For organizations using Atlassian Cloud, now is the time to understand what is changing, how your teams are using these capabilities, and what options are available as usage grows.

What Is Usage-Based Pricing?

Traditionally, much of Atlassian Cloud pricing has been based on the number of users or seats in a subscription. As AI and automation become increasingly integrated into everyday workflows, Atlassian says seat count alone does not fully represent the value or consumption of these capabilities.

The expanded usage-based pricing model adds a usage layer alongside existing subscriptions. Eligible plans include allowances for certain capabilities, giving teams room to use AI, automation, and other platform functionality without paying separately for every interaction.

When usage exceeds an included allowance, organizations have options to increase capacity through plan upgrades, prepaid usage, or additional usage charges. Atlassian has also introduced tools designed to give administrators greater visibility into consumption, costs, and projected usage.

What’s Changing?

The expanded model covers several areas of the Atlassian platform. The specific meter depends on the products and capabilities an organization uses.

Rovo Credits

AI interactions that consume Rovo credits will be measured against an included allowance. These include deeper AI interactions such as Rovo Chat, AI-powered agents, Jira Coding Agent, and Teamwork Graph queries.

Some capabilities, including Rovo Search and certain inline AI features, remain free.

Automation Steps

Atlassian is moving from measuring automation by flow runs to measuring individual execution steps.

That means a simple automation and a complex automation will no longer consume the same amount of usage simply because they are each one flow. Triggers, conditions, actions, branches, and other executed steps are measured individually. This change provides more visibility into how much automation an organization is actually using and can make it especially important to review heavily automated workflows.

Assets Objects

Assets usage is expanding to additional Atlassian customers and collections.

Usage is based on the number of unique asset records stored during the billing period. These can include items such as laptops, servers, configuration items, and software licenses. For organizations using Assets as part of IT asset management or service management, understanding the number and type of objects being maintained will become increasingly important.

AI Agent Resolutions

Atlassian is also introducing an outcome-based meter for AI agent resolutions in Customer Service Management.

Rather than charging simply because an AI agent is used, the meter is based on successful autonomous resolutions. In other words, the customer pays when the AI agent completes the request without human escalation. This represents a shift toward measuring the outcome delivered rather than simply measuring activity.

Bitbucket Usage

Bitbucket usage-based meters include areas such as build minutes, Git LFS storage, and Packages storage and network usage.

Atlassian is also moving monthly allowances from the workspace level to the organization level, providing greater flexibility in how available usage is shared across an organization.

What Does This Mean for Your Organization?

The change does not mean that every Atlassian customer will immediately receive an additional bill. Most paid Cloud plans include usage allowances, and Atlassian has built tools into Atlassian Administration to help organizations monitor consumption, forecast future usage, establish limits, and receive alerts as usage approaches those limits.

The goal is to give organizations time to understand their usage and make informed decisions before additional usage charges take effect. Atlassian’s public usage-based pricing resources provide a three-month period to explore, estimate usage, and plan before most meters begin billing on December 3.

Why Usage Monitoring Matters

For organizations that are already making significant use of AI, automation, Assets, or other metered capabilities, understanding current usage will be an important part of managing the Atlassian environment.

A few questions are worth asking now:

• Which Atlassian capabilities are our teams using most heavily?
• How much Rovo or automation usage are we currently consuming?
• Are our automation workflows unnecessarily complex or inefficient?
• How many Assets objects are we maintaining?
• What does our current usage suggest about future demand?
• Would a plan upgrade or collection provide better value as usage grows?
• Are we taking advantage of the capabilities already included in our subscription?

The answers can help organizations make decisions based on actual usage rather than assumptions.

Usage-Based Pricing Is Also an Opportunity to Optimize

While pricing changes naturally bring questions about cost, usage visibility can also create an opportunity to take a closer look at how Atlassian is being used.

For example, an organization approaching its Automation allowance could simply plan for additional usage. But it could also review its workflows and identify opportunities to eliminate unnecessary steps, consolidate processes, or redesign inefficient automations. Similarly, increasing Rovo usage is not necessarily a problem. If AI is helping employees resolve requests faster, automate repetitive work, or improve productivity, increased usage may reflect increased value.

The more important question is: Are you getting enough value from the Atlassian capabilities you’re using?

Atlassian’s usage-based pricing model is designed around included allowances, the ability to scale when needed, and greater visibility into consumption. Administrators can review usage by application and over time, forecast where usage is headed, and establish controls before teams reach their limits.

Next Steps

You do not need to wait until December to start preparing.

1. Review your current usage

Start by looking at your Atlassian Administration usage information. Identify which meters apply to your environment and how your teams are currently consuming them.

2. Estimate future demand

Consider upcoming projects, increased AI adoption, new automation initiatives, growth in Assets, and other changes that could affect consumption. Atlassian’s usage calculator can help organizations estimate their potential usage and costs.

3. Review your workflows

Use this change as an opportunity to identify inefficient or unnecessarily complex processes. Automation, for example, should be designed to deliver business value, not simply to automate as many steps as possible.

4. Evaluate your options

If your organization expects to exceed an included allowance, compare the available options, including optimizing usage, increasing capacity, upgrading plans, or considering an Atlassian Collection.

5. Make usage part of your ongoing Atlassian strategy

Usage should not be something you review only when a bill arrives. Regular reviews can help organizations identify opportunities to optimize their Atlassian investment and make sure new capabilities are being adopted where they can have the greatest impact.

6. Contact us to walk through the steps together.

There is a lot to review, and you don’t have to navigate it alone. Mumo Systems can walk through the process with you, from reviewing your current usage and estimating future demand to identifying workflow optimization opportunities and evaluating your options. Contact us to schedule a conversation and walk through the steps together.

---

The Bottom Line

Atlassian’s expanded usage-based pricing model reflects a broader shift in how organizations use software. AI and automation are increasingly performing work, not simply providing tools for people to use. That makes understanding consumption, value, and adoption more important than ever.

For most meters, billing begins December 3, 2026, giving organizations time to review their environment, estimate future usage, and put the right controls in place. Atlassian’s usage-based pricing resources provide current information on meters, allowances, pricing, FAQs, and its usage calculator.

View Atlassian’s Usage-Based Pricing Resources

Need Help Making Sense of Your Atlassian Usage?

Understanding usage is only the first step. The bigger opportunity is determining whether your Atlassian environment is configured and optimized to deliver the most value.

Mumo Systems can help you review your Atlassian environment, identify opportunities to optimize automation and workflows, evaluate your current use of Jira Service Management, Assets, Rovo, and other Atlassian capabilities, and develop a practical plan for managing growth.

For example, if your organization is approaching its Automation allowance, we can review your highest-use workflows, identify unnecessary or inefficient automation steps, and recommend ways to streamline those processes before simply adding more capacity.

Want to know what your Atlassian usage could mean for your organization? Contact Mumo Systems for an Atlassian environment and usage review.

FAQs

What is Atlassian’s usage-based pricing?

Atlassian’s usage-based pricing model measures certain capabilities based on how much they are used, rather than solely on the number of users or seats. Eligible Cloud plans include monthly usage allowances, with additional options available if an organization exceeds its included usage.

When does Atlassian’s usage-based pricing take effect?

Atlassian announced the expanded usage-based pricing on September 1, 2026. For most meters, billing for usage beyond included allowances begins December 3, 2026.

Which Atlassian products and features are affected?

The expanded usage-based pricing model includes meters for Rovo credits, Automation steps, Assets objects, AI agent resolutions in Customer Service Management, and several areas of Bitbucket usage. The specific meters and allowances depend on the products and plans an organization uses.

Will Atlassian customers automatically be charged for usage?

Not necessarily. Most paid Cloud plans include monthly usage allowances. Customers can monitor their usage and limits in Atlassian Administration. If usage exceeds an included allowance, organizations can choose options such as optimizing usage, upgrading their plan or collection, purchasing usage packs, or paying for additional usage.

How can I monitor my Atlassian usage?

Atlassian Administration provides visibility into usage, allowances, limits, and cost forecasting. Organizations can also use Atlassian’s usage calculator to estimate future consumption and potential costs. Reviewing usage regularly can help identify potential issues before additional usage charges occur.

Can Mumo Systems help us prepare for Atlassian’s usage-based pricing?

Yes. Mumo Systems can review your Atlassian environment and help identify where usage can be optimized. For example, we can review high-use Jira Automation workflows, evaluate your Assets environment, assess Jira Service Management processes, and help determine whether optimization, additional capacity, or a plan change makes the most sense for your organization.