Atlassian FY26: your self-hosted Jira has an expiry date

Atlassian's stock jumped more than 30% on August 6, and the reason is a story about where your project data is allowed to live. Atlassian FY26 results show cloud revenue growing 31% while the company guides Data Center revenue down about 17% next year. If you run Jira or Confluence on your own servers, that guidance is a countdown clock with a published end date.

What actually happened

Per the 8-K filed with the results, Q4 FY26 revenue was $1,766 million, up 28%. Cloud revenue was $1,213 million, up 31%. Data Center was $462 million, up 21%. Full-year revenue reached $6,572 million, up 26%, with remaining performance obligations of $4,817 million — up 44%. GAAP operating margin swung to 12% from −2% a year earlier.

Then the guidance. For FY27, Atlassian targets total revenue growth of about 13% — half of FY26's rate — with cloud at about 25.5% and Data Center declining roughly 17%. On AI, the company reported Rovo-assisted actions up over 50% quarter over quarter.

The two numbers only reconcile one way: the self-hosted line is shrinking on purpose. Atlassian announced in September 2025 that Jira, Confluence, and Jira Service Management Data Center reach end of life on March 28, 2029. New customers lost the ability to buy Data Center on March 30, 2026. Existing customers stop getting new licenses March 30, 2028. At end of life, those environments go read-only — view your history, but no creating or editing.

Why a vendor's end-of-life date matters for your business

A cloud-only roadmap is a pricing decision wearing a technical costume. The AI features — Rovo, the agent surfaces, the search across your workspace — are cloud features. Every year you stay self-hosted, the gap between what you run and what the vendor sells gets wider, and the migration gets more expensive, not less.

Three years sounds like a lot. It isn't, if your Jira has ten years of custom workflows, Marketplace apps that may not have cloud equivalents, and integrations nobody has documented. We have done these migrations. The engineering is manageable; the archaeology is what takes the quarters.

Do two things now. Export your data on a schedule you control — issues, attachments, and audit history, into storage you own, not a one-time migration dump. And inventory your Marketplace apps against cloud availability before you plan anything else. That list is where migrations die.

Sources: Atlassian 8-K, Atlassian Community, SiliconANGLE.