Atlassian will raise Cloud list prices for Jira, Confluence and several related products on Oct. 13, 2026 PT. The update applies to new purchases, renewals and upgrades of existing subscriptions, according to Atlassian’s Future Cloud list pricing FAQ.
Products covered by the price update
Atlassian’s FAQ lists the following Cloud products and plans as covered by the Oct. 13 update:
Teamwork Collection: Standard, Premium and Enterprise plans
Jira: Standard, Premium and Enterprise plans
Confluence: Standard, Premium and Enterprise plans
Jira Service Management / Service Collection: Standard, Premium and Enterprise plans
Atlassian Guard: Standard and Premium plans
Bitbucket: Premium plans
Jira Product Discovery: Standard and Premium plans
Atlassian Government Cloud: Jira, Confluence, Jira Service Management / Service Collection and Atlassian Guard Premium
Atlassian also says it is updating the USD to JPY currency exchange rate for all Cloud Apps and Data Center transactions.
No single percentage applies
Atlassian’s pricing tables show increases that vary by product, plan, billing cadence and user tier. The Jira and Confluence rates below are USD list prices for the first monthly user band and do not include taxes, discounts, Marketplace apps or usage-based charges.
Product and plan
Current monthly list price
New monthly list price
Calculated change
Jira Cloud Standard, 1-100 users
USD 9.05 per user
USD 9.70 per user
About 7.2%
Jira Cloud Premium, 1-100 users
USD 18.30 per user
USD 19.60 per user
About 7.1%
Confluence Cloud Standard, 1-100 users
USD 6.70 per user
USD 7.15 per user
About 6.7%
Confluence Cloud Premium, 1-100 users
USD 13.20 per user
USD 14.10 per user
About 6.8%
The approximate percentages above are calculated from Atlassian’s listed current and new USD prices, not stated as a universal increase. For annual 100-user tiers, Jira Cloud Standard moves from USD 9,050 to USD 9,700, while Confluence Cloud Standard moves from USD 6,700 to USD 7,200.
Billing cadence changes the impact
Annual and monthly subscriptions do not calculate the same way. Atlassian says annual pricing uses a fixed user-tier model, while monthly pricing uses progressive per-user rates.
That distinction matters for renewals. Atlassian gives an example in which Jira Standard with 480 users is billed at the 500-user annual tier. Under the new table, that tier is USD 39,000. If the account grows to 565 users, it moves to the 600-user tier at USD 46,000, with only the prorated difference charged for the remainder of the term.
For customers near tier boundaries, inactive user cleanup can affect the renewal total when it changes the tier. For monthly customers, the invoice is more sensitive to each user band because different portions of the user count are priced at different per-user rates.
Existing quotes and renewals
Atlassian says quotes generated before Oct. 13 will be honoured under prior pricing until the quote expires. Quotes generated on or after Oct. 13 will use the new prices.
Existing monthly subscribers will see bills on or after Oct. 13 reflect new pricing. Existing annual subscribers will also see new pricing on quotes modified on or after that date. Annual auto-renew bills on or after Oct. 13 also use the new price unless an open quote was created before the date and remains valid, according to Atlassian.
Monthly customers can request an annual quote before Oct. 13 to receive existing pricing, Atlassian says. Payment must be received before the quote expires, and the quote cannot be extended beyond Nov. 11, 2026 PT.
Marketplace apps and usage meters are separate
Atlassian says Marketplace Partner app pricing is not changing directly as a result of the Oct. 13 update, though Marketplace partners can change their own pricing separately.
The Oct. 13 change is also separate from Atlassian’s usage-based pricing system. Atlassian’s usage page says usage-based billing takes effect Dec. 3, 2026 for most meters. The meters include Rovo credits, automation steps, Assets objects, Bitbucket meters and Customer Service Management AI agent resolutions, depending on the product.
What customers should review before Oct. 13
The checks most likely to change the invoice are:
whether a renewal or annual quote already exists before Oct. 13;
whether monthly sites should move to annual billing before the cutoff;
whether inactive users can be removed before annual tier calculations;
whether multiple Standard or Premium sites should be reviewed against Enterprise or Collection pricing; and
whether Dec. 3 usage meters need separate budget controls.
Atlassian recommends customers compare current invoices with the new pricing tables in My Atlassian or Atlassian Administration.
Get new small business insights by email
Practical ideas and useful articles to help you make better business decisions.
Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us
