Atlassian’s AI and automation tools are about to become variable operating costs. In a Sept. 1, 2026, update, the company confirmed that beginning Dec. 3 it will enforce monthly allowances and charge for excess Rovo credits and Automation steps.
The change affects organizations using Atlassian AI and workflow automation at scale. Extra usage is enabled by default, but organization and billing admins can cap spending, disable overages, or purchase additional capacity.
Before Dec. 3, IT teams need to establish usage baselines and decide which workloads warrant additional spending. AI-agent workloads can make enterprise costs difficult to forecast, particularly when consumption varies sharply between workflows.
Rovo credits and Automation steps become separate cost meters
Rovo credits measure AI activity and access to enriched Teamwork Graph context, with consumption depending on the complexity of the interaction. Rovo Chat, agents, the Jira Coding Agent, and some Teamwork Graph activity can consume credits, while Rovo Search, summaries, chart insights, and definitions remain outside the meter under the current Rovo usage rules.
Allowances vary by product and plan, are pooled at the organization level, and reset each month without carrying unused capacity forward. Atlassian lists extra Rovo usage at $0.01 per credit, or $10 per 1,000 credits.
Automation is measured by executed steps rather than completed rule runs. Triggers, conditions, actions, branches, and loops can each count as a step, so a multi-stage workflow can consume several units each time it runs.
Extra Automation usage costs $0.50 per 1,000 steps, and Enterprise plans will move from unlimited Automation to pooled monthly allowances under Atlassian’s updated Automation pricing model.
A single workflow can hit both meters: standard triggers, conditions, and actions consume Automation steps, while Rovo-powered actions draw from the separate Rovo credit pool. Admins therefore need to forecast the full workflow rather than count only rule executions or AI prompts.
Organizations are also putting more budget behind AI agents, adding another variable to IT and finance planning as agent use expands.
Spending controls can also interrupt workflows
Admins who do not want automatic overage charges should review their settings before Dec. 3. Organization and billing admins can set monthly usage limits or disable extra usage in Atlassian Administration.
Atlassian sends notifications when consumption reaches 80% and 100% of an included allowance. The broader move toward centralized controls for enterprise AI agents also puts usage monitoring alongside access and governance as an administrative task.
Turning off overages creates an operational trade-off. If an organization exhausts its Automation allowance, new flows stop until capacity resets or more is added; flows already running can finish, but triggering events missed during the pause are not queued for later replay.
Rovo also stops new credit-consuming interactions when its allowance is exhausted and extra usage is disabled, although work already in progress can finish. Organizations expecting steady overages can buy prepaid usage packs instead.
Before Dec. 3, admins should baseline consumption, set an overage policy, and identify the AI and automation workflows whose interruption would create the greatest operational risk.
Read more: Usage-based AI pricing is spreading beyond Atlassian, with Google adding pay-as-you-go Gemini Enterprise pricing and spending caps for organizations managing variable agent workloads.
Let us teach you How to Talk to AI for free! Try our six-minute course at The Neuron Academy and learn a few simple ways to write better prompts and get more useful results from AI, or browse our other AI course for free for seven days. Check out all the lessons here →