Atlassian’s New Usage-Based Pricing Model: What You Need to Know
- Gal Fatal
- 2 days ago
- 2 min read
Atlassian is moving beyond a purely seat-based model for selected AI, automation, and platform capabilities. The new approach combines predictable included allowances with usage-based billing when organizations scale beyond those allowances.
Summary
Starting December 3, 2026, Atlassian will activate usage meters for selected capabilities. Organizations will receive included allowances, shared across the organization, while administrators gain tools to monitor consumption, forecast costs, and set limits before additional usage occurs.
Included allowances are designed to cover typical usage and are pooled across the organization.
Organization and billing administrators can set or adjust usage limits at any time.
Atlassian Administration provides usage tracking and cost-forecasting visibility.
Customers have until December 3, 2026 to review patterns and prepare; billing does not begin before then.
Usage meters at a glance
Meter | How it is measured |
|---|---|
Rovo credits | Selected AI features, enriched Teamwork Graph API calls, and usage by tools and agents. Basic interactions use a flat rate; premium interactions vary by consumption. |
Automation steps | Individual automation steps rather than complete flow runs, giving administrators more granular visibility. |
Assets objects | Objects managed in Assets, with administration moving toward a centralized Atlassian experience for applicable users. |
AI agent resolutions | $1.00 per fully resolved Customer Service Management request, with no included allowance. Charges apply only when the AI agent resolves the request end-to-end without escalation. |
What this means for IT and finance teams
The model creates a balance between predictability and flexibility. Included allowances provide a baseline for normal activity, while usage controls help prevent unexpected expansion. At the same time, teams can adopt more AI and automation without redesigning their plans every time demand changes.
The main operational change is that consumption must become part of regular governance. IT leaders should connect usage data with business outcomes, while finance teams should monitor forecasted extra usage and align limits with approved budgets.
Recommended preparation checklist
Open the Platform usage dashboard in Atlassian Administration and review the available meters.
Identify which products, teams, agents, and workflows are generating usage.
Set organization-level and billing-level limits that match your budget and service priorities.
Use Atlassian rate cards, FAQs, and the pricing calculator to model likely extra usage.
Set up notifications so administrators can act before reaching configured limits.
Important considerations
Usage information may take up to a week to populate, so some meters might not appear immediately. Metered capabilities can continue running up to the limits configured by administrators. For customers on a free trial, extra usage applies only after upgrading to a paid Standard, Premium, or Enterprise plan.
Bottom line: Atlassian’s new model is designed to make AI and platform consumption more visible and controllable. Organizations that review usage early, set clear limits, and connect consumption to business value will be best positioned for a smooth transition.
Check this Atlassian usage-based pricing announcement and how to check your usage
Comments