UBP FAQs

Usage-based pricing is a pricing model that aligns what you pay with the value you get, and it works alongside your existing subscription. Atlassian subscriptions come with a monthly included allowance of metered capabilities, like Rovo credits, Automation steps, and Assets objects. When your team needs more, you can purchase additional capacity, upgrade your plan to unlock higher allowances or continue usage with pay as you go.

Here's how usage-based pricing works at Atlassian:

• Your plan already includes allowances for metered capabilities at no extra cost

• Allowances pool at the org level and are shared across all users, not split per person or per app

• You have full visibility and control in Atlassian Administration to monitor usage, set limits, and forecast costs

The way teams work is changing. AI resolves support tickets, automation handles multi-step workflows, and intelligent features surface the right information before you even ask. No two organizations adopt these capabilities the same way, and usage-based pricing is built for exactly that. Instead of a fixed price for capacity you may never use, you receive included allowances so you can manage your own pace of adoption and growth. When your team needs more, you can purchase additional capacity, upgrade your plan to unlock higher allowances or continue with extra usage, paid as you go.

No. Your existing subscription and renewal process are unchanged. Usage-based pricing adds a consumption layer on top of your plan. You continue paying for seats as before, and usage-based charges apply only if you consume metered capabilities beyond your included allowance.

Usage-based pricing applies to specific capabilities that scale in value with how much your organization uses them. Atlassian tracks this usage through meters, each measuring a distinct unit of consumption:

Billing begins on Dec 3, 2026 for most meters. The timing can depend on the capability you use and your billing cadence.

You’ll hear more from us about the date that applies to your organization.

Plans for the following cloud apps and collections include monthly usage allowances for select meters at no extra cost:

• Jira

• Confluence

• Teamwork Collection

• Service Collection

• Strategy Collection

• Bitbucket

How it works:

• Pooled at organization level. Your total allowance is shared across all users and subscriptions in your organization, not by app or by person.

• Refreshes monthly. Allowances reset at the start of each billing cycle, unused allowance does not carry over.

• Most customers won't exceed their allowance. Allowances are calibrated for typical usage patterns.

Learn more about allowances: Usage charges and billing.

Each capability is measured differently:

Each meter has its own separate allowance and is tracked and billed independently. Meter usage only counts against the corresponding meter type and is billed accordingly. Using more of one metered capability doesn't affect your allowance for another meter. For example, using Automation does not consume Rovo credits, except for any AI-powered steps in the flow.  In that case, the action uses Rovo credits, not Automation steps, so you won't be double-counted.

Your monthly allowances from all subscriptions contribute to a single, shared pool per meter at the organization-level (not split per user, project, or app). All usage across your sites counts towards the same pool at the organization level, and all of your users draw from it.

A few things to know:

• Allowances refresh monthly, regardless of whether you're on a monthly or annual plan. Annual customers don't get a lump-sum yearly allowance, they receive a new monthly allowance instead.

• Unused allowances don't roll over month-to-month.

• Higher tiers and collections add more per-user allowance to the pool.

For specific allowances by plan, refer to “Does my existing plan already include usage allowances?”.

It depends on the meter:

• Rovo credits: Yes, AI interactions in sandbox consume credits from your allowance.

• Automation steps: Yes, steps running in sandbox count toward your allowance.

• Assets objects: No, sandbox usage doesn't count toward your allowance.

• Bitbucket: Not applicable.

• CSM AI agent resolutions: Not applicable (sandbox environments are not currently supported).

Select plans include allowances so you can try metered capabilities out:

Allowances reset monthly, regardless of billing cycle. Capabilities that were paused due to reaching your usage limit become available again.

 By meter:

• Rovo credits: Yes. AI interactions and insights retrievals from Teamwork Graph in the sandbox consume credits from your allowance.

• Automation steps: Yes. Steps running in the sandbox count toward your allowance.

• Assets objects: No. Sandbox usage doesn't count toward your allowance.

• Bitbucket: Not applicable (Bitbucket doesn't use sandbox environments).

• Customer Service Management AI agent resolutions: Not applicable (sandbox environments are not currently supported).

AI and automation consume the same compute resources whether they run in sandbox or production. Measuring all usage in one place gives you a complete picture of your organization's consumption, with no hidden costs in either environment.

How to monitor and control sandbox usage:

• Use the Platform usage dashboard to monitor your total usage. Please note that sandbox and production usage aren't currently shown separately.

• Set and adjust usage limits to cap any additional usage spend, covering both sandbox and production activity.

• Where possible, use lower-cost testing approaches (for example, switching to auto mode for Rovo agents during testing).

Your work is safe. Nothing is lost, deleted, or stops working without warning. What happens at the limit depends on the meter:

Atlassian Administration is the single, centralized place to monitor and manage usage and usage-based billing across all your meters.

Monitoring and managing usage
To monitor and manage usage, access your Platform usage dashboard. 
Go to Atlassian Administration, select Insights and Platform usage. From here, your organization and billing admins can:

• Monitor, manage, and forecast usage and allowances at the organization level for Rovo credits, Automation steps, Assets objects, Bitbucket meters, and Customer Service Management AI agent resolutions.

• Access forecasting, notifications, and usage controls.

• Set and adjust extra usage limits as needed.

• Filter usage data by app or user (organization admins only). User-level filtering is only available for Rovo credits.
   

Viewing and managing billing
To view and manage your usage-based billing, go to Atlassian Administration and select Billing. From this view, your organization and billing admins can:

• View and manage subscriptions and all meters as separate entries, like Rovo credits.

• Forecast estimated bill cost for the next month.

• Disable extra usage per meter or keep it enabled and set usage limits per meter to cap spending.

• Purchase usage packs/committed packs, like Rovo credits usage packs/Rovo credits committed packs.

• View invoices and cost-to-date.

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. 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.

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

Allowances are consumed in the following order:

1. Plan allowance: Your included monthly allowance is used first.

2. Usage packs: Any pre-purchased usage packs are used next.

3. Committed packs: Any committed packs are used next, if purchased.

4. Extra usage: Extra usage applies last. It is enabled by default for most customers, so applicable charges may apply after included allowances and purchased capacity are used.

Yes, for most organizations. Extra usage is enabled by default, allowing usage to continue after your included allowance and any applicable purchased capacity are used. Billing admins can review and manage extra-usage settings in Atlassian Administration.

Extra usage is billed at our published rates.

Your billing or organization admin can turn off extra usage at any time from Atlassian Administration.

To disable extra usage, select Billing, and navigate to the meter you'd like to update (e.g. Rovo credits). From there, select disable extra usage. You can also disable extra usage from the Platform usage dashboard under Insights → Platform usage.

Once disabled, your organization will continue to use its included monthly allowance at no additional cost. If your teams hit 100% of the allowance, they'll experience a limited product experience for that metered capability until the allowance resets at the start of the next billing period or until you add prepaid capacity. No extra usage charges will apply.

The change takes effect immediately. You won't need to wait for a billing cycle to complete. Once disabled, no further extra usage charges will accrue for that meter.

Extra usage is managed per meter. You can disable extra usage for one meter (e.g. Automation steps) while keeping it enabled for another (e.g. Rovo credits). This gives you granular control over which meter can incur pay as you go charges.

Learn more here: Manage extra usage for a meter.

Usage notifications are sent to your organization and billing admins. They manage your meter usage, subscriptions, and spending.

When you’ll be notified

• 80% of allowance used: An early heads-up, giving you time to adjust access, add a usage pack or committed pack, or set an extra usage limit.

• 80% of usage limit reached: An early heads-up, giving you time to adjust your extra usage limit.

• 100% of allowance used: Confirms you’ve consumed the included allowance for that meter.

• 100% of usage limit reached: Confirms you’ve reached your extra usage limit for that meter.

How you’ll be notified

• Email: Proactive, automated alerts sent to your organization and billing admins when usage exceeds key thresholds.

• Banners in Administration: Shown on the Platform usage page when you reach 80% and 100% of your allowance and any usage limit you set (visible to organization admins only).

• Bell notifications: Available in the notifications section via the bell icon in Atlassian Administration (visible to organization admins only).

These notifications apply per meter and are based on your organization’s pooled allowance, not individual user consumption.

Do end users also receive usage notifications?

Your end users don't receive billing or allowance notifications directly. This is an admin-only experience by design, keeping usage and cost management centralized.

Yes. Atlassian Administration helps organization and billing admins estimate future usage and spend using historical data and planning tools.

• Usage dashboard: View up to 90 days of usage history and estimated monthly usage to see whether you are trending toward an allowance limit.  

• CSV export and published rate cards: Export usage data or model your own scenarios using each meter’s published rates.

• Usage limits: Adjust limits at any time. You are not charged unless usage exceeds your included allowances.

You can also use the usage calculator to estimate costs based on organization size, plan tier, and expected usage for Rovo credits, Assets objects, Automation steps, and Customer Service Management AI agent resolutions. Bitbucket meters will be added later this year.

Note: Usage estimates aren’t binding for either you or Atlassian. The figures shown are intended to provide an estimate of usage allowances and may be subject to change.

If you are unsure which model best fits your expected usage, contact your Atlassian account team or support to review your needs and discuss the appropriate option.

How will I be billed for usage?
Usage-based pricing works alongside your existing seat-based subscription. Your existing subscription costs are not affected.

For most customers, extra usage is enabled by default. You may incur additional charges only after your organization has used its monthly included allowance and any applicable purchased capacity, such as usage packs or committed packs.

How it works:

• Within your allowance → no additional charge. Your plan includes a monthly allowance for each capability, pooled at the organization level.

• Beyond your allowance and purchased capacity → extra usage charges may apply. Extra usage is enabled by default and is billed based on actual consumption at our published pricing.

• Manage usage and spend in Atlassian Administration. Billing admins can monitor usage and manage extra usage settings.

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

For purchasing and licensing questions, see the FAQ for each meter:

• Rovo credits FAQ

• Automation steps FAQ

• Assets objects FAQ

• Bitbucket meters FAQ

• Customer Service Management AI resolutions FAQ

The meters available as of September 1, 2026 are listed here. We’ll update this list as additional usage-based pricing meters become available.

Reference these meter-specific FAQ pages to learn about how usage-based pricing functions for a particular meter:

• Rovo credits FAQ

• Automation steps FAQ

• Assets objects FAQ

• Bitbucket meters FAQ

• Customer Service Management AI resolutions FAQ

We recommend starting in Atlassian Administration, where you can monitor and manage your current usage. Explore the usage management tools and controls available today, and share your experience directly via the feedback button.

For additional resources to help you navigate this change:

• If you don't have a dedicated Customer Success Manager or Account Executive: 
  Start with Atlassian Support or the Atlassian Community for usage and billing questions.

• If you have a dedicated Customer Success Manager or Account Executive: 
  You can reach out for questions about usage-based pricing, allowances, or commercial options.