Close

Atlassian Usage-Based Offering Terms

Effective starting: October 1, 2026

These Usage-Based Offering Terms (these “Terms”) supplement the Atlassian Customer Agreement, or another agreement entered between Customer and Atlassian governing Customer’s use of Atlassian Products (the “Agreement”) and apply to Cloud Products and features that are billed based on usage (“Usage-Based Offerings”). Usage-Based Offerings may include automations and AI Offerings, for example. These Terms control in the event of a conflict with the Agreement. Capitalized terms used and not defined in these Terms have the meanings given to them in the Agreement.

1. Meters, Allowances and Consumption.

1.1 Meters. Usage-Based Offerings are organized by meter (“Meter”). Each Meter tracks Customer’s usage of a particular Usage-Based Offering(s) at the Atlassian organization level and is denoted in units such as credits, objects or resolutions (“Consumption Units”). 

1.2. Allowances and Packs. By ordering certain Cloud Products, Customer receives a particular allowance of Consumption Units (an “Allowance”). For most meters, these included Allowances refresh monthly (the “Allowance Period”). Customer may also purchase standalone packs of Consumption Units, which are paid in advance (“Packs”). Packs may contribute directly to Customer’s existing Allowance over the same Allowance Period or be consumable over a longer period.

1.3. Consumption; Responsibility.

(a) Consumption. Customer consumes Consumption Units for a given Meter by using Usage-Based Offerings that draw from that Meter. The rate of consumption is specified in the Documentation and varies by Usage-Based Offering. Consumption occurs in the following order:  first the Allowance; next any Pack; and finally, where enabled, Extra Usage (defined below).

(b) Updating Consumption Rates. Atlassian may update the rate at which each Usage-Based Offering consumes Consumption Units. Such updates will apply from the effective date of the change onward.

(c) Responsibility. Customer is responsible for its use of Usage-Based Offerings, including use due to actions of Users, Agents, and Third-Party Products and due to configurations (for instance, a scheduled automation run). 

1.4. Expiration. Any unused portion of an Allowance or Pack expires at the end of the relevant period and does not roll over. Atlassian does not provide refunds or credits in this event.

1.5. No Monetary Value. Allowances and Packs apply only to the associated Usage-Based Offering(s). They have no monetary value and may be transferred only in connection with an authorized assignment under the Agreement.

2. Monitoring and Extra Usage.

2.1.  Monitoring; Notifications. Customer may monitor its usage by Meter through its Cloud Products’ administration experience. As described in the Documentation, Atlassian will notify Customer when its usage reaches certain thresholds during an Allowance Period. 

2.2.  Extra Usage; Reaching a Limit

(a) Extra Usage. By default, usage above Customer’s Allowance and any applicable Pack is enabled (“Extra Usage”). Customer may update this default and set limits on Extra Usage at any time. Where Extra Usage occurs, Customer must pay Atlassian for the Extra Usage, which Atlassian will invoice in arrears at its then-current rates unless otherwise specified in an applicable Order. Atlassian may impose reasonable limits on the permitted amount of Extra Usage.  Extra Usage is disabled for free plans.

(b) Reaching a Limit. Where Customer reaches a limit on consumption (for instance, by consuming its Allowance, disabling Extra Usage and not purchasing a Pack), Atlassian may limit access to the corresponding Usage-Based Offering(s) until the next Allowance Period. The Documentation describes how this limitation applies to each Usage-Based Offering. 

3. No Return Policy.

Any return policy in the Agreement does not apply to Packs or Extra Usage. 

How might these terms apply to a customer’s usage?

To illustrate, here’s an example that assumes that the customer (Customer) has 20 Confluence users – and no other Atlassian products or users – and receives 10 Rovo credits per user

Meter. Customer’s interactions with Rovo are tracked by the Rovo credits Meter.

Consumption Units. Rovo credits are a type of Consumption Unit

Allowance. Customer’s Allowance is 200 Rovo credits per month. 

Allowance Period.  Month 1, Month 2 and Month 3 below are each an Allowance Period.

Month

Customer Action

Credits Consumed

Credits Included

Extra Usage

Notes

1

Customer Action

-

Credits Consumed

195

Credits Included

200

Extra Usage

-

Notes

5 unused credits expire at month end

2

Customer Action

-

Credits Consumed

250

Credits Included

200

Extra Usage

50 Credits

Notes

Extra Usage invoiced in arrears, as described below

3

Customer Action

Buys 100 credit Pack

Credits Consumed

300

Credits Included

200 (Allowance) + 100 (Pack)

Extra Usage

-

Notes

The Pack, paid in advance, covers the 100 additional credits. Extra Usage is not drawn.


Related content

Product-specific terms

Advisory Services

Data Processing Addendum

Data Transfer Impact Assessment

Stay informed

Subscribe to receive notifications from us about updates to our legal terms (including our legal policies) and our list of sub-processors.