Atlassian price increase October 2026 and the end of Data Center
Atlassian price increase October 2026: partners report 7-10% on Jira and Confluence, overages on most meters bill from 3 December, and Data Center ends in 2029.
Atlassian’s October 2026 price increase took effect on 13 October 2026: new list prices for Jira, Confluence, Jira Service Management, Teamwork Collection and several other cloud products apply to monthly bills, annual quotes and renewals from that date, and partners report rises of 7 to 10% on Jira and Confluence. From 3 December 2026, usage above each plan’s allowance is billed for most meters, Rovo credits and automation steps among them. Atlassian stops selling Data Center expansions to existing customers on 30 March 2028, and Data Center, the self-managed edition, turns read-only on 28 March 2029, so a Swiss or EU organisation’s next renewal is the point to decide where Jira and Confluence run next.
This post covers the size of the rise, the cost of metering, the Data Center dates, Atlassian Cloud’s options for Swiss and EU data, self-hosted replacements, and a dated to-do list.
How much is the Atlassian price increase of October 2026?
Atlassian publishes new list prices, not percentages. Partner Adaptavist, in a post of 28 August 2026 updated on 2 September, reports the following:
| Cloud product and plan | Change reported by Adaptavist |
|---|---|
| Jira, Confluence, Teamwork Collection: Standard and Premium | +7-10% |
| Jira, Confluence, Teamwork Collection: Enterprise | +8% |
| Service Collection: Standard and Premium | +7.5% |
| Service Collection: Enterprise | +10% |
| Jira Product Discovery: Standard and Premium | +5% |
| Atlassian Guard: Standard | +3% |
| Atlassian Guard: Premium | +5% |
| Bitbucket Cloud Premium | +10%, 5-user minimum removed |
Seibert Group, another partner, reads the 7-10% range as 7% under 5,000 seats and 10% from 5,000. What binds is the list price on your quote.
Atlassian’s cloud pricing FAQ says: “New prices will go into effect October 13, 2026 PT.” Its list matches the table, with Jira Service Management alongside Service Collection, plus Atlassian Government Cloud.
Monthly subscribers pay the new prices on every bill from 13 October 2026. Annual subscribers pay them at renewals and auto-renewals, on user-tier upgrades and on any quote generated or modified from that date, and a renewal can only be bought within 90 days of the renewal date. A quote generated before 13 October keeps the old price until it expires. An annual quote that a monthly customer requested before 13 October “cannot be extended beyond November 11, 2026 PT.”
What will Rovo credits and automation cost from 3 December 2026?
On 1 September 2026, Tamar Yehoshua, Atlassian’s Chief Product & AI Officer, wrote: “Allowance limits and billing for these meters will go into effect on December 3, 2026.” Her post names three meters: Rovo credits (Rovo Chat, Confluence AI Slides, Jira Coding Agent, Teamwork Graph queries), automation steps, and AI agent resolutions, which Atlassian’s usage-based pricing page files under Customer Service Management. In-line summaries, rewrites and Rovo Search stay free.
Three qualifiers decide what lands on the invoice:
- For most meters. “Billing begins on Dec 3, 2026 for most meters.” Timing can depend on the capability and the billing cadence, and Atlassian will tell each organisation its date.
- Above the allowance only. Charges apply only to usage beyond the allowance in the plan. Allowances are pooled across the organisation and reset monthly.
- On by default. “Extra usage is enabled by default” for most organisations, until a billing admin disables it or sets a limit per meter. Admins are notified at 80% and 100% of the allowance.
Atlassian publishes unit prices for the two main meters. Its Rovo credits page gives the list price at this time as “$0.01 per Rovo credit, or $10 per 1,000 credits”. The monthly allowance per user is 25 credits on Jira or Confluence Standard, 70 on Premium and 150 on Enterprise, and 250, 700 and 1,500 on Service and Teamwork Collection. A Rovo Chat quick answer is a basic event at 10 credits, so a 100-user Jira Standard organisation pools 2,500 credits a month, about 250 quick answers, before extra usage is billed.
For automation, Atlassian’s automation documentation says: “Extra usage is billed at $0.50 per 1,000 additional steps”, charged on the next invoice. The monthly allowance per user is 400 steps on Jira Standard, 750 on Premium and 1,000 on Enterprise, and 100, 250 and 500 on the matching Confluence plans. Every trigger, condition, action, branch and loop counts as a step.
When does Atlassian Data Center reach end of life?
Mike Cannon-Brookes announced on 8 September 2025 that Atlassian is “sunsetting Atlassian Data Center products”. Its end-of-life page sets the dates, each at 23:59 PST:
| Date | What happens |
|---|---|
| 30 March 2026 | Sales of Data Center subscriptions and Marketplace apps to new customers end |
| 30 March 2028 | Existing customers can no longer buy new subscriptions, expansions, upgrades or Data Center Marketplace apps |
| 28 March 2029 | End of life: subscriptions and their Marketplace apps expire and the products become read-only |
The end of life covers Jira Software, Jira Service Management, Confluence, Crowd, the Data Center mobile apps and their Marketplace apps. Bitbucket, Bamboo and Jira Align Data Center are not part of it.
Read-only means: “You will be able to access your data, but you will not be able to add new data or perform new actions.” Fixes for critical vulnerabilities stop on 28 March 2029, and Atlassian strongly advises against keeping a read-only instance connected to the internet. Multi-year extensions beyond 28 March 2029 are sold “by exception only”, extended maintenance is offered to certain customers by exception, and existing enterprise licensing agreements are honoured. For larger customers, Atlassian offers dual licensing so they do not pay for Cloud and Data Center twice during a long migration, and cloud migration trials last for the rest of the Data Center subscription.
For a growing organisation, 30 March 2028 matters more than 2029: after it, a Data Center licence cannot be expanded or upgraded, and no Data Center Marketplace app can be bought. Until the end, an instance also needs patching. On 5 October 2026 Atlassian published CVE-2026-21589, which it rates Critical (CVSS 4.0 score 9.3): unauthenticated arbitrary file access in eight self-managed products, including Jira Software, Jira Service Management and Confluence, in all versions before the fixed releases. Atlassian says its cloud products were already patched.
Can Jira and Confluence data stay in Switzerland on Atlassian Cloud?
For stored content, yes. Atlassian’s data residency offers a Switzerland location (the Zurich region) and an EU location (Frankfurt and Dublin) for Jira, Jira Service Management, Jira Product Discovery, Loom and Confluence on Standard, Premium and Enterprise.
The same page lists what residency does not pin:
- User account information: names, email addresses and avatars, held in a global identity service.
- Logs and analytics, and AI data for Jira, Confluence and Jira Service Management.
- Transient and cached data, for up to 30 days, and some Marketplace and integration data.
Zurich has gaps of its own: “The Atlassian Data Lake is not available for this location”, so some Atlassian Analytics charts and dashboards do not work for data pinned there, and Opsgenie and Assets reports in Jira Service Management are affected.
With its fiscal 2026 fourth-quarter results on 6 August 2026, Atlassian reported the general availability of Isolated Cloud, an Atlassian-managed offering in a dedicated AWS VPC for a single customer. Its FAQ explains that storing content in a residency region does not meet the definition of data sovereignty in many countries: “In short, Atlassian Isolated Cloud doesn’t support data sovereignty.”
Residency settles where content is stored, not which law the provider answers to. Atlassian Corporation has been a Delaware-incorporated holding company since its redomiciliation to the United States, which took effect on 30 September 2022. See data residency, the CLOUD Act, and Microsoft 365 data residency in Switzerland for the same question asked of another US provider.
For many organisations, Atlassian Cloud with Zurich residency is a reasonable place to land, as a documented choice with these exclusions written down.
Which self-hosted tools can replace Jira and Confluence?
- Plane for issues, cycles, modules, boards and roadmaps. The Community Edition is AGPL-3.0. Its Jira importer comes with the free tier of the Commercial Edition, and OIDC and SAML sign-in need a paid plan.
- OpenProject (GPL-3.0) where Jira serves a project office rather than a development team: work packages, Gantt charts, and time and cost tracking.
- Outline or BookStack for Confluence. Outline is source-available under the Business Source License 1.1, not open source. BookStack is MIT-licensed, in one edition with SAML2, OIDC and LDAP included. It has no Confluence importer, so exported spaces are loaded through its REST API into its four-level page tree.
- Zammad (AGPL-3.0, single sign-on included) where Jira Service Management runs an email and web helpdesk.
- GitLab Community Edition (MIT) where code, pipelines and issues should sit together.
Complex workflows, JQL filters and Marketplace app data do not map one to one, and Confluence macros have no direct equivalent. Jira automation rules are rebuilt in n8n where they are still needed. The full side-by-side is on our Jira alternative page.
What to do, and by when
Starting does not mean leaving. An inventory and a named fallback for each tool give you a position at the next renewal, and answer the auditor’s question about vendor lock-in.
- By 11 November 2026: if you are a monthly customer holding an annual quote requested before 13 October, pay it before it expires.
- Before 1 December 2026, if you export Confluence Cloud: XML site and space export reaches end of life that day. It keeps working, but Atlassian will no longer “fix bugs, accept support tickets, or provide SLAs” for it. Move scheduled backups and archive jobs to CSV export, the supported alternative, and check that your archive or migration tooling reads it; Atlassian suggests keeping one final XML export until the CSV workflow is validated. CSV cannot be imported into Data Center, whose site restore accepts only XML.
- Before 3 December 2026: in Atlassian Administration, review usage per meter, disable extra usage or set a limit where needed, and check the billing start date Atlassian gives your organisation.
- At your next renewal on or after 13 October 2026: remove inactive and duplicate accounts before the quote is generated, above all if that takes you below a user tier or below 5,000 seats, the point from which Seibert reads the 10% rate as applying. Record what data residency covers and excludes for your organisation.
- By June 2027: inventory the Jira projects, Confluence spaces, Marketplace apps and automation rules still in use, name a target for each (Atlassian Cloud or a self-hosted tool) and run one pilot project. Atlassian’s end-of-life page says customers buying Cloud Enterprise by June 2027 “may be eligible for a 10-20% discount” in the first year, so Data Center customers need the comparison ready by then.
- Before 30 March 2028, if you run Data Center: buy any expansions, upgrades or Data Center Marketplace apps you will need until you leave.
- Before 28 March 2029: be off Data Center or hold a written exception from Atlassian, with any read-only instance off the internet.
- Throughout, if DORA or FINMA outsourcing rules apply to you: keep a documented, tested exit plan for Jira and Confluence where they support critical or important functions (DORA) or significant functions (FINMA).
How Pilae fits
Pilae deploys Plane or OpenProject, with Outline or BookStack as the wiki, on your premises on the machines you choose, or on dedicated machines in Pilae Cloud in Zurich or the EU, with sign-on through your directory. The app database, files, backups and logs stay in the region named in the contract (residency), and backups are encrypted before they leave, under keys you hold (CLOUD Act and your data location).
The move is a migration with a fixed scope and price agreed in writing: an inventory, a staging import, a pilot, a parallel run and a cutover with a rollback. On Plane, the original Jira key is stored on each imported issue, so a search for an old key from a commit, wiki page or email still finds it, and Jira can stay readable until the subscription ends. Afterwards the Pilae Agent plans each upgrade for your approval and backups run daily; on the Enterprise plan, an engineer also restores them every month. An exit plan gives you a tested fallback without leaving Atlassian. Our plans and prices are on the pricing page. Talk to an engineer.
Prices, dates and terms in this post are as of 13 October 2026 and taken from Atlassian’s pages, except the percentages, which are partners’ figures. Check the cloud pricing FAQ and the Data Center end-of-life page before a renewal.