Our usage-based model is designed to help organizations of all sizes expand AI adoption with confidence and without disruption. It works alongside your existing subscription by adding a usage layer on top of your subscription for metered capabilities like AI and automation.

That design is built around four principles:

• Substantial allowances: Meaningful usage is built into your plan and available right now for everyday work. Allowances pool at the organization level, so capacity goes where it’s most valuable.
• Uninterrupted operations: Your teams keep the access and value they already rely on, with no risk of being blocked from expanded use. When you need more capacity, you have options to upgrade your plan, pre-pay, or pay as you go.
• Predictable pricing: Pricing is public and transparent, and a platform dashboard shows you where usage is headed based on historical trends, so you can plan for what's next.
• Full governance: Real-time visibility into who is using what, with admin controls to adjust limits at any time.

Usage-based billing takes effect December 3, 2026 for most meters. Timing may vary based on the capability you use and your billing cadence.

To learn more, see the UBP Purchasing and Licensing FAQ.

For purchasing and licensing questions about each meter, see that meter's FAQ:

• Rovo credits FAQ
• Automation steps FAQ
• Assets objects FAQ
• Bitbucket meters FAQ
• Customer Service Management AI agent resolutions FAQ

Here are the key terms you'll see across your usage-based pricing experience:

Your plan and what's included

• Meter: Tracks your organization's use of a specific capability and measures it against your included allowance. For example, the Rovo credits meter tracks how many AI actions your organization consumes.
• Allowance: The amount of usage included in your plan at no extra cost. Allowances pool at the organization level and refresh each monthly billing period.

Going beyond your allowance

• Extra usage: Usage above your included allowance. Extra usage is enabled by default and billed in arrears based on actual consumption. Your admin can set limits or disable it at any time.

Ways to add capacity

• Usage pack: A block of additional capacity purchased in advance at a fixed rate that tops up your monthly allowance. Unused capacity does not roll over to the next month.
• Committed pack: An annual prepaid balance you can draw from flexibly throughout the year. Valid for 12 months and does not roll over.

Rovo credits now measure usage of AI features across Atlassian apps and collections, and enriched Teamwork Graph (TWG) API calls by tools and agents you use.

AI features: Rovo credits are consumed when a user or agent invokes AI to take an intelligent action on their behalf. Embedded AI, like Summaries and Definitions remain free.

• Fixed rate: Basic AI features like Quick Answer mode in Rovo Chat and basic Rovo Agents use 10 credits per invocation.
• Variable rate: Premium AI features like Think Deeper mode in Rovo Chat, Confluence slides, and Jira Coding Agent use a variable number of credits, depending on the compute effort your question requires and the output generated.

Teamwork Graph API: Enriched Teamwork Graph API and tool calls now consume Rovo credits.

• Free: TWG API calls like, installing the Teamwork Graph CLI and Atlassian Rovo MCP, or running commands to look up or update context in any single Atlassian product, remain free.
• Variable rate: Enriched TWG API and tool calls deliver deeper context from across Atlassian and connected external applications that users and agents use. They perform significant computational work on your behalf that goes beyond standard API reads:
  • Multi-source orchestration and graph traversal: Enriched calls can traverse connected Atlassian and third-party systems, such as Slack, GitHub, and Google Drive, across a graph of relationships.
  • Inference, ranking, and synthesis: These calls run backend processes for relationship inference, entity resolution, and relevance scoring to extract meaningful signals from raw data.
  • Permission-aware filtering: Context is dynamically filtered to respect granular, cross-product enterprise access controls before it is returned.
• Examples of enriched TWG APIs include:
  • The "collaborators" API call, which provides insights about collaborators by analyzing common artifacts and interactions between users in an organization.
  • The "context" API call, which aggregates information across multiple Atlassian and connected external systems to deliver the best context around a work item, Confluence page, or user.
• Each enriched TWG API call uses a variable number of credits, depending on the complexity of the request. The vast majority of enriched TWG API calls range from 1-10 credits per call.

To learn more about these and other billable events, visit the Rovo credits documentation.

Please note that the pricing in the documentation applies to all usage and forecasts starting August 31, 2026. Usage before August 31 uses the previous pricing.

Most Atlassian Cloud apps and Collections include allowances for metered capabilities at no extra cost. Use the usage calculator to see your usage needs by meter based on your organization's size and team's estimated usage.

Collections

• Teamwork Collection (includes Jira, Confluence, Loom, Rovo): Rovo credits, Automation steps, Assets objects. See pricing.
• Service Collection (includes Jira Service Management, Customer Service Management, Assets, Rovo): Rovo credits, Automation steps, Assets objects. See pricing.

Standalone apps

• Jira: Rovo credits, Automation steps, Assets objects. See pricing.
• Confluence: Rovo credits, Automation steps. See pricing.
• Jira Product Discovery: Automation steps. See pricing.
• Bitbucket: Build minutes, Git LFS storage, Packages storage, Packages network. See pricing

Learn about included allowances here.

Allowances pool at the organization level, so any user or app drawing from the same meter shares the same balance. They refresh each billing period.

When usage occurs, capacity is drawn in this order:

1. Included allowance: Your plan's built-in allowance is consumed first, at no extra cost.
2. Prepaid packs: If you've purchased additional capacity, it's drawn next.
3. Extra usage: Usage beyond your allowance and any prepaid packs. Extra usage is enabled by default and billed in arrears. Your admin can set limits or disable it at any time.

Organization and billing admins can track usage across all meters in Atlassian Administration.

You stay in control. Organization and billing admins receive proactive notifications at 80% and 100% of your included allowance and any limits you set, so there is always time to review and decide next steps before anything changes.

If you want to add capacity:

• Upgrade your plan or move to a Collection: Enterprise plans and Collections include substantially higher allowances than standalone apps at the same plan tier. Best for long-term cost planning and predictability.
• Annual usage packs: Add predictable capacity to your annual agreement. Tops up your available capacity for the monthly billing period and do not roll over to the next month. Your Atlassian account team can help size the pack during procurement or renewal based on your expected usage.
• Monthly usage packs (coming soon): Add capacity as needed to cover short-term increases in usage. Monthly usage packs top up your available capacity for the billing period and do not roll over to the next month.
• Committed packs (coming soon): Purchase an annual prepaid balance your organization can draw from flexibly throughout the year.

If you reach your allowance, what happens next depends on your extra usage settings:

• If extra usage is enabled (default setting): Usage continues without interruption. Any usage beyond your included allowance is charged at the published rate, subject to any usage limit your admin has set.
• If extra usage is disabled or a usage limit is reached: Only the specific meter that has been exhausted pauses (for example, Rovo credits or Automation steps). All other meters continue to operate independently. The paused capability becomes available again when your allowance refreshes or your organization adds capacity through a prepaid or committed pack, when available.

Admins can disable or enable extra usage, set or adjust usage ceilings, and purchase additional capacity directly in Atlassian Administration.

Atlassian Administration gives organization and billing admins visibility, predictability, and control over usage across their organization.

Visibility

• Usage tracking: View consumption across meters and filter by app or time period to understand where usage is happening and how it changes over time.
• Notifications: Organization and billing admins receive alerts (in-product and email) as usage approaches 80% and 100% of an included allowance or any limits you set.

Predictability

• Forecasting: View projected usage for upcoming billing periods based on historical trends.
• Annual usage packs: Add predictable capacity to your annual agreement. Your Atlassian account team can help size the pack during procurement or renewal based on your expected usage.

Control

• Extra usage settings: Enable or disable extra usage by meter.
• Limits and safeguards: Set a usage ceiling for each meter, with the option to apply organization-wide limits. When a limit is reached, only the affected capability pauses, giving admins time to review usage and decide what to do next.

To get started, go to Atlassian Administration, select your organization if you manage more than one, then select Insights → Platform usage.

We're continuing to expand capabilities to help you manage your usage. The following capabilities are planned, with availability varying by meter and product to launch by December 3, 2026:

• Usage data export: Export usage data in human-readable terms (such as users, sites, and organizations) for reporting, reconciliation, and automation.
• Monthly usage packs: Purchase additional capacity as needed to support variable or short-term increases in usage.
• Committed packs: Purchase annual prepaid capacity that your organization can draw from flexibly throughout the year.
• Allocations: Planned controls to manage usage more granularly across groups, users, and agents.

For an overview of usage-based pricing, go to Usage charges and billing.

For details about how each meter works, including what counts toward usage and how allowances are applied, see the meter-specific support documentation:

• Rovo credits
• Automation steps
• Assets objects
• Bitbucket meters
• Customer Service Management AI agent resolutions