Atlassian Meters Rovo Credits and Automation Steps Dec. 3

Your Jira automations and Rovo agents are about to get a price tag. From December 3, 2026, Atlassian Rovo credits and automation steps used beyond your plan's monthly allowance are billed, and extra usage is on by default. Pick a spending cap and a bill owner before then, or the default picks for you.

What Atlassian changed on December 3

Atlassian's Rovo usage limits page and automation usage page both put extra usage billing at December 3, 2026. Admins can switch it off at any time, and billing runs up to an admin-defined spending cap.

| Meter | Extra usage price | | --- | --- | | Rovo credits | $0.01 per credit ($10 per 1,000) | | Automation steps | $0.50 per 1,000 steps |

Each paid plan includes a monthly allowance per user. Allowances are pooled across the organization, reset on your billing date and do not roll over.

| Plan | Jira Rovo credits | Confluence Rovo credits | Jira steps | Confluence steps | | --- | --- | --- | --- | --- | | Standard | 25 | 25 | 400 | 100 | | Premium | 70 | 70 | 750 | 250 | | Enterprise | 150 | 150 | 1,000 | 500 |

Enterprise plans no longer have unlimited automation, and the Service and Teamwork Collections have larger allowances, so check your own plan.

What burns Atlassian Rovo credits

A basic billable event, such as a Rovo Chat Quick Answer or a basic agent without model selection, costs 10 credits. Premium features like Think Deeper, the Jira Coding Agent and agents with model selection cost a variable amount. Atlassian publishes no fixed rate for them, so measure real usage instead of forecasting from a feature list.

Rovo Search inside Atlassian apps is free, as are write operations and single-product lookups. Cross-product queries and unified search cost credits, mostly 1 to 10 each, so an outside assistant querying your Atlassian data through MCP can spend your allowance.

What burns automation steps

A step is one executed part of a flow: a trigger, condition, action, branch or loop. Trigger, check priority, assign user, send notification is 4 steps. A condition that evaluates to false still counts, so a noisy trigger costs money even when nothing happens. Aborted and throttled runs are not charged.

Agentic steps (Use Rovo, Use agent, Use Jira Coding agent) bill as Rovo credits instead of steps.

What happens when you hit the limit

Leave extra usage on with no cap and you get a surprise invoice. Turn it off and flows stop at the allowance: events are not queued, so nothing is replayed. A cap sits between the two, but one set too low behaves like off, because metered features may be limited once the limit is reached.

Set a cap and pick a bill owner before December 3

1. Read your current usage

Organization admins can open Atlassian Administration, then Usage, then Meters, and select Rovo credits or automation steps. Use Export data for a CSV covering up to 3 months or 1 million usage events.

2. Estimate the overage

# Rough monthly overage estimate. Replace the inputs with numbers
# from Atlassian Administration > Usage > Meters.
CREDIT_PRICE = 0.01        # USD per Rovo credit
STEP_PRICE = 0.50 / 1000   # USD per automation step

def overage(used: int, allowance: int, unit_price: float) -> float:
    return max(0, used - allowance) * unit_price

# Example: 40 Jira Standard users, 25 credits and 400 steps each
users = 40
credit_allowance = users * 25   # 1,000 credits
step_allowance = users * 400    # 16,000 steps

credits_used = 3_000  # <your monthly Rovo credits>
steps_used = 40_000   # <your monthly automation steps>

print(f'Rovo credits: ${overage(credits_used, credit_allowance, CREDIT_PRICE):.2f}')
print(f'Automation steps: ${overage(steps_used, step_allowance, STEP_PRICE):.2f}')

With the example numbers this prints $20.00 for credits and $12.00 for steps. Add your Confluence allowances to the totals, since both meters are pooled across the organization.

3. Set the limit

In Atlassian Administration, go to Billing, then Subscriptions, and select the meter. From the dropdown next to Get more usage, choose Enable extra usage (a payment method must be on file), then Update extra usage limit, set the amount and save, following the extra usage docs. Lowering the limit below usage already incurred locks metered features until reset, and that usage is still billed.

4. Name an owner for the alerts

Organization and billing admins are notified at 80% and 100% of usage. Make sure that is a person or shared inbox who can decide something, not an admin who left in March.

5. List the flows that must not stop

Write down the automations your delivery process depends on, such as SLA escalations and release checklists, and protect them with a higher cap.

Gotchas

• Atlassian's billing page lists prepaid usage packs for both meters. Unused allowance does not roll over, so size them to a normal month.
• Some Atlassian pages still say extra usage above the Rovo allowance is not billed. They predate the December 3 date.

On Monday, export a month of usage, run the estimate, set the cap and name the alert owner: an AI feature without a budget owner gets found by invoice.