Preparing for Atlassian’s December 3rd Rovo and Automation Usage Pricing

What Rovo and Automation customers need to know before usage-based billing begins

Beginning December 3rd, 2026, Atlassian will introduce usage-based billing for several metered capabilities, including Rovo credits and Automation steps.

Organizations will continue to receive included monthly allowances, but usage beyond those allowances may result in additional charges.

The bigger change is not simply the possibility of overage fees. It is how Atlassian measures usage.

Atlassian will measure automation usage by each individual step a rule executes, rather than by completed rule runs. Rovo will consume credits based on the type and complexity of each AI activity. That means Atlassian customers should start looking at actual usage now, before the new billing model takes effect.

What Changes on December 3rd?

The practical result: Automation and AI usage are becoming both technical and financial management considerations.

What Is Changing for Atlassian Automation?

Under the new model, Atlassian measures Automation usage by the number of steps executed. A step can include:

• A trigger
• A condition
• An action
• A branch
• A loop

For example, a rule that detects a new work item, checks its priority, assigns it to someone, and sends a notification could consume four Automation steps each time it runs.

4 steps × 20,000 executions = 80,000 Automation steps

That is why simply counting the number of automation rules in your environment will not tell you much about future consumption. The better calculation is how often the rule runs × how many steps it executes.

Complex rules with several branches, conditions, loops, or actions can consume substantially more than simple rules, especially when they run frequently.

Automation Allowances Are Pooled

Atlassian’s new model pools Automation allowances at the organization level across eligible products. Current documented monthly allowances include:

For example, 100 Jira Premium users plus 100 Confluence Standard users would provide a combined allowance of 85,000 Automation steps per month.

Atlassian currently lists additional Automation usage at $0.50 per 1,000 steps beyond the included allowance. Enterprise customers should pay close attention because environments that previously operated with effectively unlimited Automation may now need to actively monitor consumption.

What Is Changing for Rovo?

Rovo uses a separate meter: Rovo credits. Eligible Atlassian subscriptions include monthly Rovo credit allowances, pooled across the organization.

Not every Rovo interaction consumes credits in the same way. Some capabilities, including certain search, definition, and summary functions, may not consume credits. Other AI interactions consume a fixed or variable amount depending on the feature and complexity of the request.

Examples of usage that may consume credits include:

• Rovo Chat interactions
• Rovo Agents
• Advanced reasoning capabilities
• Jira Coding Agent
• Certain Teamwork Graph interactions

Atlassian currently lists additional Rovo usage at $0.01 per credit, or $10 per 1,000 credits.

Your user count determines the size of your included pool. User behavior determines how quickly you consume it.

What Happens When You Reach Your Limit?

Admins must decide what happens when included usage is exhausted. Depending on the capability and configuration, organizations may choose to:

• Allow pay-as-you-go additional usage
• Set spending limits
• Purchase additional usage capacity
• Optimize activity to stay within the included allowance
• Disable extra usage

If an organization reaches its Automation allowance and turns off additional usage, some automated processes may stop running until capacity becomes available again.

Organizations need to manage two risks: unexpected spending and unexpected interruption.

What Atlassian Admins Should Do Now

1. Review Current Usage

Use Atlassian Administration’s platform usage tools to understand current consumption, included allowances, forecasted usage, high-consumption users and automations, and the Rovo capabilities consuming the most credits. Look for trends over time rather than relying on a single week of activity.

2. Identify High-Volume Automations

Prioritize rules that run frequently, contain many steps, use branches or loops, operate across large volumes of work items, run on schedules, or support high-volume service and integration workflows.

3. Clean Up Unnecessary Automation

Review your automations to confirm you still need them, identify duplicate rules, and replace scheduled rules with more efficient event-driven triggers where possible. The goal is not simply to reduce automation costs. The goal is to ensure every automation you pay for delivers value.

4. Establish Rovo Governance

Determine which teams and agents are driving usage, which features consume the most credits, what spending thresholds are acceptable, and which AI workflows produce measurable business value.

Estimate Your Automation Costs Before December 3rd

To help organizations translate today’s activity into tomorrow’s step consumption, ReleaseTEAM offers a free tool: Automation Step Cost Calculator for Jira & Confluence. It can help estimate whether current Automation usage is likely to remain within the included allowance or create additional costs, and identify high-volume automations that deserve closer analysis.

Helpful videos:

For Automation Calculator details: Atlassian Automation Pricing Changes: Calculate Your Costs

For a broader explanation of changes: Atlassian Rovo and Automation Pricing Change Overview 2026

Focus on Value, Not Just Usage

Usage-based pricing naturally draws attention to cost, but cost alone should not determine how organizations use Automation or Rovo. A workflow that adds a small monthly charge but eliminates hours of repetitive work may be a very good investment.

Are we spending our Automation steps and Rovo credits on work that creates measurable value?

That requires visibility, governance, and periodic optimization.

How ReleaseTEAM Can Help

ReleaseTEAM can help organizations prepare for the December 3rd change by:

• Reviewing current Automation usage
• Identifying high-volume or inefficient rules
• Estimating future step consumption
• Reviewing Rovo usage and governance
• Evaluating licensing and allowance options
• Helping optimize automations without sacrificing business outcomes

The goal is simple: understand what you are using, what it may cost, and where optimization makes sense before usage-based billing begins.

Ready to Prepare? Contact ReleaseTEAM.

If you are unsure how Atlassian’s new Rovo and Automation usage model will affect your organization, contact ReleaseTEAM. Our Atlassian experts can help you review your current usage, identify potential cost drivers, optimize high-volume automations, and build a practical plan before December 3rd, 2026.

Understand your usage before it becomes an invoice. Contact ReleaseTEAM to get started.

Source note: Pricing and allowance figures reflect Atlassian information referenced for this article as of September 24th, 2026, and may change.