Atlassian Raises Jira and Confluence Cloud Prices From 13 October

What happened

Atlassian will raise its Cloud list prices on 13 October 2026, effective at 12:00 a.m. Pacific Time. According to Eficode, a consultancy that advises on Atlassian renewals, the change reaches Jira, Confluence, Jira Service Management, Teamwork Collection, Atlassian Guard, Bitbucket Premium and Jira Product Discovery, along with selected Atlassian Government Cloud products. Schneider IT Management, which summarises Atlassian's own pricing tables, says the new prices apply to new purchases, renewals and upgrades made from that date.

The increase is not one flat rate. Schneider reports that Jira Cloud and Confluence Cloud Standard and Premium plans rise 7 per cent below 5,000 seats and 10 per cent at 5,000 seats and above. Eficode's table lists 8 per cent for Enterprise plans of Jira and Confluence, and 7.5 per cent for Jira Service Management and Service Collection Standard and Premium.

The 200-user example is the figure most buyers will quote. ONES says the Standard bundle moves from $28,500 to $30,500 and the Premium bundle from $55,000 to $59,000 for annual billing. It calls these benchmarks rather than universal prices, and notes that its prices were captured from public sites on 10 September 2026.

Why it matters for businesses that automate work

Automation used to sit quietly inside the subscription. Atlassian's own automation page says it is still built into the existing plan and needs no separate purchase. What changes is the metering. From 3 December 2026, each trigger, condition, action, branch and loop that runs counts as a step, and steps above the pooled monthly allowance are billed at $0.50 per 1,000.

Atlassian's own worked example shows the scale. A team that uses 12,000 steps against a 5,000-step allowance pays for 7,000 extra steps, which comes to an estimated $3.50 a month. The cost is small per rule, but a business with many rules, or rules that loop over large lists, can see the count climb quickly. Some third-party guides have reported different overage rates, so check the figure on Atlassian's own page before you set a budget.

Rovo credits and AI agent resolutions follow their own rules. Rovo credits cover deep AI interactions such as chat and agent work, and Atlassian describes AI agent resolutions as charged separately from Rovo credits and Automation steps. Customer Service Management plans include no allowance for agent resolutions, and Atlassian says each successful resolution is charged from the first one.

What changes in practice

For a renewal, the first step is the date. Quotes generated before 13 October 2026 are honoured until they expire, according to Schneider, so a team that is already planning a renewal should ask for its quote before that date. Anything generated or modified after the date uses the new list prices. A team that plans to add seats or move between plans should decide before 13 October too, because upgrades after the date use the new pricing.

For the automation budget, the practical work is counting. A business should export its rule list, identify which rules run most often, and estimate steps per month for each. Atlassian's pages say the allowance is pooled across the organisation, so one heavy team can use up steps that another team counted on. Atlassian also says that if extra usage is turned off, automated flows pause once the allowance is used up, and they resume when the allowance refreshes or a pack is bought. That pause is the main operational risk. A rule that handles invoices or customer follow-ups can stop without any warning if no one is watching the meter.

Not every business will see a change in the same way. A team on a small seat count with light automation may see only the subscription increase. A large group with heavy automation, Rovo use or Customer Service Management agents may see the usage line become the bigger cost. Automation that runs on manual triggers is not a substitute for a budget review, and a rule that is never used still costs nothing, so the review should focus on the busiest flows first.

What to watch next

• Renewal quotes issued before 13 October 2026, and whether they expire before the renewal date.
• The first December 2026 invoices, which will show Automation step and Rovo usage for the first time for most customers.
• The 5,000-seat threshold, which determines whether a growing organisation moves from the 7 per cent band to the 10 per cent band.
• Whether Atlassian publishes further unit prices for meters that do not yet show one on its public pages.