Atlassian Introduces Metered Pricing for Rovo AI and Automation

Atlassian moves AI and automation to consumption-based billing

Atlassian will begin metering usage of its Rovo AI platform and Automation workflows on December 3, 2026, introducing monthly allowances and overage charges that turn both tools into variable operating expenses for enterprise IT organizations.

The company announced the pricing change in a September 1 update, according to TechRepublic, which first reported the details. Organizations will receive monthly allocations of Rovo credits and Automation steps based on their product tier, with excess usage billed automatically unless administrators configure spending caps.

How the new metering works

Rovo credits track AI interactions that tap into Atlassian's Teamwork Graph context layer. Activities that consume credits include Rovo Chat, AI agents, the Jira Coding Agent, and certain graph operations. Rovo Search, content summaries, chart insights, and definitions currently fall outside the metered pool.

Atlassian prices additional Rovo credits at $0.01 each, or $10 per thousand. Credit allowances are pooled at the organization level, reset monthly, and do not roll over unused capacity.

Automation pricing shifts from unlimited execution on Enterprise plans to a step-based model. Each trigger, condition, action, branch, and loop counts as one step, meaning a single workflow can consume multiple units per run. Extra Automation steps cost $0.50 per thousand.

Complex workflows can hit both meters simultaneously. Standard automation logic draws from the step pool, while any Rovo-powered actions within the same flow consume AI credits separately. This dual metering requires administrators to forecast the full execution path rather than simply counting rule runs or prompt volume.

Administrative controls and operational risks

Organization and billing administrators can configure spending limits or disable overage charges entirely through Atlassian Administration settings. The platform sends alerts when usage reaches 80 percent and 100 percent of the included allowance.

Disabling overages introduces workflow continuity risk. When an organization exhausts its Automation allowance, new flows will not trigger until capacity resets or additional steps are purchased. Workflows already in progress can complete, but any triggering events that occur during the pause are lost—Atlassian does not queue missed events for replay.

Rovo behaves similarly under a hard cap, blocking new credit-consuming interactions while allowing in-flight work to finish. Organizations anticipating consistent overage can purchase prepaid usage packs to avoid interruptions.

Why it matters

The shift to metered AI and automation pricing reflects a broader industry trend as vendors move away from flat-rate enterprise licensing. Google recently introduced pay-as-you-go Gemini Enterprise pricing with similar spending controls, signaling that variable AI costs are becoming a standard budget line item for IT finance teams.

For Atlassian customers, the December 3 deadline creates an immediate planning requirement. Administrators need to establish current consumption baselines, determine which workflows justify additional spending, and decide whether to allow automatic overages or enforce hard caps. AI agent workloads in particular can produce unpredictable usage spikes, making cost forecasting more difficult than traditional software licensing.

Organizations should prioritize identifying mission-critical automation flows whose interruption would create operational risk, then ensure those workloads have adequate capacity or overage protection before the new pricing takes effect.

TechRepublic first reported the pricing changes and implementation timeline.