Commercial software intelligenceEvidence checked · 8 September 2026
SkuTrace

Commercial product change, preserved as evidence.

SK-2026-186 · Licensing models & metrics

Atlassian expands usage-based pricing across Rovo, Automation and AI-agent capabilities

Atlassian is retaining seat subscriptions while adding a separate usage-based layer across metered capabilities including Rovo credits, Automation steps and Customer Service Management AI-agent resolutions, with most new billing boundaries starting 3 December 2026.

Expanded metered billing scheduled

Commercial transition

Previous stateBefore the 1 September 2026 expansion, Atlassian had not applied the newly announced cross-product metered-billing model across the named Rovo, Automation and Customer Service Management capabilities.
→
New stateAtlassian keeps seat subscriptions while adding a separate consumption layer for named metered capabilities. Included allowances are pooled at organization level and refresh monthly without rollover; extra usage is enabled by default for most meters unless administrators limit or disable it, while Customer Service Management AI-agent resolutions use a separate per-successful-resolution meter.

Who is affected

Atlassian organizations using metered Rovo, Automation, Assets, Bitbucket or Customer Service Management capabilities whose consumption can exceed included allowances or create usage-based charges.

Action required

Inventory the organization's applicable meters, review included allowances and default extra-usage settings, set usage controls or limits where required, and budget for the stated effective billing boundaries.

Evidence boundary

Atlassian proves the expanded consumption model and states that most new meter billing boundaries begin on 3 December 2026. Assets and Bitbucket have separately stated timing and mechanics; Customer Service Management AI-agent resolutions are a distinct meter. This record does not claim every meter starts billing on the same date or that the future 3 December boundary is already in force.

Timeline

  1. Expanded usage-based pricing announced

    Atlassian described the cross-product meter model, included allowances and usage controls.

  2. Most new meter billing boundaries begin

    Atlassian schedules most newly announced usage-based billing mechanics to take effect.

Official sources