What changed on 13 October
Atlassian's new cloud list prices took effect on 13 October 2026, Pacific Time. Atlassian published the change on a dedicated future pricing page with an FAQ and full old and new pricing tables, which is to its credit: every figure in this article can be checked against the vendor's own numbers rather than a reseller's summary.
The rise covers almost the whole cloud catalogue. Atlassian lists the following as affected:
- Jira: Standard, Premium and Enterprise.
- Confluence: Standard, Premium and Enterprise.
- Jira Service Management and Service Collection: Standard, Premium and Enterprise.
- Teamwork Collection: Standard, Premium and Enterprise.
- Atlassian Guard: Standard and Premium.
- Bitbucket: Premium only.
- Jira Product Discovery: Standard and Premium.
- Atlassian Government Cloud: Jira, Confluence, Jira Service Management and Service Collection, and Guard Premium.
Free plans are not on the list, and Atlassian's FAQ describes no change to them. Data Center list prices are not part of this change either; the only Data Center item mentioned is a separate yen to dollar exchange rate update that applies to both cloud and Data Center transactions.
What Atlassian did not change
Third-party Marketplace app prices are not changing as a direct result of this update, although Atlassian notes that partners can change their own prices at any time. The percentages for Academic, Social Impact, Classroom and Open Source discounts stay the same, so eligible organisations pay the same discount on a higher list price.
How it reaches your bill
The mechanics differ by billing cycle, and they are the part most worth getting right.
| Situation | Price you pay |
|---|---|
| Monthly bill dated on or after 13 October | New price |
| Annual quote created or modified on or after 13 October | New price |
| Annual auto-renewal billed on or after 13 October | New price |
| Open quote created before 13 October | Old price, until the quote's stated expiry |
| Monthly customer who requested an annual quote before 13 October | Old price, if paid before the quote expires and no later than 11 November 2026 |
| Change of user tier, plan or new product on or after 13 October | New price |
The last row is the one that catches growing teams. Crossing into a higher user tier, upgrading from Standard to Premium or adding a product from today is priced at the new list, even for a customer whose existing subscription is still running on an old-price annual term.
The new prices, from Atlassian's own tables
Atlassian publishes its future pricing tables by product and user tier. The figures below are monthly list prices in US dollars per user, or per agent for Service Collection, for the smallest tier of each plan. They are taken directly from Atlassian's tables; the percentages are our arithmetic.
| Product and plan | Tier | Old | New | Change |
|---|---|---|---|---|
| Jira Standard | 1 to 100 users | $9.05 | $9.70 | +7.2% |
| Jira Premium | 1 to 100 users | $18.30 | $19.60 | +7.1% |
| Confluence Standard | 1 to 100 users | $6.70 | $7.15 | +6.7% |
| Confluence Premium | 1 to 100 users | $13.20 | $14.10 | +6.8% |
| Service Collection Standard | Up to 15 agents | $25.00 | $26.90 | +7.6% |
| Service Collection Premium | 1 to 15 agents | $57.30 | $61.60 | +7.5% |
| Bitbucket Premium | 6 to 100 users | $7.25 | $8.00 | +10.3% |
| Bitbucket Standard | Up to 100 users | $3.65 | $3.65 | None |
| Jira Product Discovery Standard | Up to 25 users | $10.00 | $10.50 | +5.0% |
| Jira Product Discovery Premium | Up to 25 users | $25.00 | $26.25 | +5.0% |
| Teamwork Collection Standard | Up to 100 users | $15.00 | $15.00 | None |
| Teamwork Collection Premium | Up to 100 users | $29.00 | $29.00 | None |
The headline percentages hide the tier detail
Reseller Eficode's summary, which is the version most buyers will have seen, gives the rises as 7% to 10% for Jira, Confluence and Teamwork Collection Standard and Premium. Atlassian's tables show the picture is less tidy than that, in both directions.
- Confluence's smallest tiers rise by less than 7%. Standard goes up 6.7% and Premium 6.8% for teams of up to 100.
- Teamwork Collection's entry tier does not move at all at Standard or Premium, but its 250-user Standard tier rises from $12.75 to $14.40, which is 12.9%, above the headline range.
- Large Jira tiers rise more than small ones. Jira Standard at 101 to 250 users rises 7.2%, from $7.65 to $8.20, but at 7,501 to 10,000 users it rises 10.4%, from $4.80 to $5.30.
Eficode itself notes that its figures are summaries and that Atlassian's tables contain tier-specific exceptions. The practical lesson is that the only number that matters is the one for your tier, and it takes two minutes to look up. Our Jira pricing, Confluence pricing and Jira Service Management pricing pages set out the plan structure around these numbers.
Bitbucket loses its smallest Premium tier
Bitbucket Premium rises 10.3% at 6 to 100 users, and the old one to five user Premium tier, listed at $36.25, is removed. Eficode describes this as the loss of the five-user minimum tier. Standard is unchanged. For a small engineering team on Premium for its merge checks and deployment controls, the question of whether Premium earns its place now comes up at renewal; our Bitbucket pricing page and Bitbucket alternatives are the starting points, and GitHub vs GitLab covers the two obvious destinations.
The reseller summary, by product
Atlassian's FAQ does not state percentage increases; it lists affected products and publishes tables. The most widely circulated percentage summary comes from Eficode, an Atlassian partner, published on 7 September. It is a reseller's reading of Atlassian's tables, not an Atlassian statement, and we reproduce it as such.
| Product | Plan | Increase (Eficode summary) |
|---|---|---|
| Jira, Confluence, Teamwork Collection | Standard and Premium | 7% to 10% |
| Jira, Confluence, Teamwork Collection | Enterprise | 8% |
| Jira Service Management, Service Collection | Standard and Premium | 7.5% |
| Jira Service Management, Service Collection | Enterprise | 10% |
| Bitbucket | Premium | 10% |
| Jira Product Discovery | Standard and Premium | 5% |
| Atlassian Guard | Standard | 3% |
| Atlassian Guard | Premium | 5% |
Where we could check the summary against Atlassian's monthly tables, it mostly holds. Service Collection Standard and Premium rise 7.6% and 7.5% at the smallest tier. Jira Product Discovery rises exactly 5% at every tier we checked. Guard Standard rises from $4.20 to $4.35 per user at 250 users, which is about 3.6%, while its 10-user tier stays at $30. The exceptions are the ones listed above: Confluence's small tiers come in under 7%, and some Teamwork Collection tiers sit outside the range in each direction.
Enterprise figures could not be checked
Enterprise pricing is quoted rather than listed, so the 8% and 10% Enterprise figures rest on Eficode's summary alone. We have not been able to verify them against a published Atlassian price. An Enterprise customer should treat them as a guide to what the renewal quote is likely to show and compare the quote line by line against the previous one.
What it costs a real team
Percentages are easier to shrug off than invoices. The examples below use Atlassian's list prices for teams inside the smallest tier, monthly billing, before tax and before any partner discount.
| Team | Old per month | New per month | Extra per year |
|---|---|---|---|
| 50 users, Jira Standard | $452.50 | $485.00 | $390 |
| 100 users, Jira Standard and Confluence Standard | $1,575.00 | $1,685.00 | $1,320 |
| 100 users, Jira Premium and Confluence Premium | $3,150.00 | $3,370.00 | $2,640 |
| 15 agents, Service Collection Standard | $375.00 | $403.50 | $342 |
| 15 agents, Service Collection Premium | $859.50 | $924.00 | $774 |
For most teams this is a rise to budget for rather than a reason to migrate. A 100-person engineering organisation on Jira and Confluence Standard pays $1,320 more a year, which is less than the cost of a week of anyone's time spent moving tools. That is worth saying plainly, because price rise coverage tends to imply that switching is the answer, and for a 7% increase on a tool a team uses all day it usually is not.
Where it does add up
The exceptions are large organisations in the higher Jira tiers, where the percentage is closer to 10%, and teams that stack several products. A team paying for Jira, Confluence, Jira Service Management and Bitbucket Premium feels each rise separately. Those are the buyers for whom a consolidation review, whether into Teamwork Collection or out of a product they barely use, is worth the effort.
The rise arrives with the meter
This change is separate from Atlassian's usage-based billing, which starts charging for Rovo credits, automation steps and AI agent resolutions on 3 December 2026. We covered the allowances and overage rates in Atlassian's usage-based pricing from 3 December. The two are unrelated in mechanism, but they arrive within eight weeks of each other, and a finance team comparing a January invoice against a September one will see both at once. It is worth separating them in your own budget so that the metered part, which you can influence, is not hidden inside the list price rise, which you cannot.
It also fits a pattern we tracked through the year in AI tier bundling and legacy plan retirements: vendors raising the base price of the seat while adding AI features, then metering the AI separately.
What to do now that the deadline has passed
The cheapest option, locking an annual quote at the old price, closed for monthly customers on 12 October. That still leaves useful moves.
If you requested an annual quote before 13 October: pay it
Monthly customers who asked for an annual quote before today keep the old price only if payment is received before the quote expires, and Atlassian says these quotes cannot be extended beyond 11 November 2026. Find the quote, check its expiry date and get it through procurement now. A purchase order stuck in approval on 12 November is a purchase order at the new price.
If you are on an annual plan: use the renewal quote
Annual customers receive a renewal quote 90 days before expiry, and quotes created before 13 October are honoured until their stated expiry. If you received one before today, check whether it is still valid and whether paying early is worth it. If your renewal falls later, the quote you receive will be at new prices.
Clean up users before the next quote
Eficode's most useful advice is the least glamorous: remove former employees, dormant and duplicate accounts and finished contractors before the renewal is quoted. Because Atlassian prices in tiers, dropping below a tier boundary can save more than the rise costs. A Jira site with 104 billed users of whom 10 have left is paying for a tier it does not need.
Hold off on tier and plan changes you do not need
Any change of user tier, plan or product from today is priced at the new list. That does not mean delaying a necessary upgrade, but it does mean an upgrade to Premium made because it seemed like a good idea is now 7% more expensive than it was last week.
Check the Marketplace bill separately
Marketplace partner apps are not changing price as a result of this update, but many are priced against your Atlassian user tier, and partners can set their own prices at any time. Audit which apps are still used before the renewal, since an unused app costs the same whether or not Atlassian raised its own price.
Is it a reason to switch?
For most teams, no. A rise of around 7% on tools that sit at the centre of how a team works is rarely worth a migration on its own. But it is a reasonable moment to check whether each Atlassian product is still the right one, because the same review that justifies the renewal will also find any product being paid for out of habit.
Jira
For engineering teams frustrated with Jira's weight, Linear is the usual alternative to evaluate; Jira vs Linear sets out the trade-offs. Teams that use Jira mainly for task tracking rather than software delivery should look at Asana vs Jira, ClickUp vs Jira and Jira vs monday.com, and Microsoft-centred shops at Azure DevOps vs Jira. The full field is in Jira alternatives.
Confluence
Confluence's small-tier rise is the gentlest in the catalogue, at under 7%. The usual comparison is Confluence vs Notion, and Confluence alternatives covers dedicated wikis. The case for staying is strongest where Confluence is tightly linked to Jira; the case for moving is strongest where it is used as a document store nobody searches.
Jira Service Management
Service desks priced per agent feel percentage rises more sharply, because agent seats cost several times a Jira seat. Freshservice vs Jira Service Management is the like-for-like mid-market comparison, and Jira Service Management vs ServiceNow matters for larger IT organisations. JSM alternatives lists the rest.
Bitbucket and Jira Product Discovery
Bitbucket Premium carries the largest percentage rise at small team sizes and the loss of its smallest tier, which makes it the product most worth reviewing on price alone. Jira Product Discovery's 5% is modest; teams weighing it against standalone product management tools can start with Aha! vs Productboard.
Questions people ask
- When did Atlassian cloud prices increase?
On 13 October 2026, Pacific Time. Monthly bills dated on or after that date, and annual quotes and auto-renewals created or billed on or after it, use the new list prices.
- How much did Jira go up in October 2026?
Jira Standard for 1 to 100 users went from $9.05 to $9.70 per user per month, a 7.2% rise. Jira Premium for 1 to 100 users went from $18.30 to $19.60, 7.1%. Larger tiers rise by up to about 10%, for example Standard at 7,501 to 10,000 users went from $4.80 to $5.30.
- How much did Confluence and Jira Service Management go up?
Confluence Standard for up to 100 users went from $6.70 to $7.15 per user (6.7%) and Premium from $13.20 to $14.10 (6.8%). Service Collection Standard for up to 15 agents went from $25.00 to $26.90 per agent (7.6%) and Premium from $57.30 to $61.60 (7.5%). Reseller Eficode summarises JSM and Service Collection Enterprise as rising 10%.
- Can I still lock in the old Atlassian price?
Only if you already have a quote. Monthly customers had to request an annual quote before 13 October 2026 and must pay before it expires, no later than 11 November 2026. Quotes created before 13 October are honoured until their stated expiry. New quotes, plan changes and tier changes from 13 October use the new prices.
- Is the October price rise the same as Atlassian usage-based pricing?
No. The 13 October change raises subscription list prices. Usage-based billing for Rovo credits, automation steps and AI agent resolutions is a separate change that starts on 3 December 2026; see our guide to the December metering.
- Are Atlassian free plans, Data Center or Marketplace apps affected?
Free plans are not among the affected plans listed by Atlassian. Data Center list prices are not part of this change, though a separate yen to dollar exchange rate update applies to cloud and Data Center transactions. Marketplace partner app prices are not changing as a direct result, but partners can change their own prices at any time.
Sources
Every price, limit and date above was checked against these pages on the day shown. Where a figure has since moved, the vendor’s own page is the authority and this one is a snapshot.
- 1Future Cloud list price update: FAQs · AtlassianThe 13 October PT effective date, affected products, billing rules and the 11 November quote limit.Checked
- 2Future Cloud list pricing tables · AtlassianOld and new monthly per-user prices by product and tier, the source of every dollar figure here.Checked
- 3Atlassian Cloud prices are changing in October 2026: What to review before your next renewal · EficodeReseller summary of percentage rises by product and plan, including the Enterprise figures Atlassian does not list.Checked