Atlassian Q1 FY27: Six Quarters of Cloud Growth and What the Rovo Bundle Hides

Atlassian told investors to expect cloud revenue growth of about 28.5% in fiscal Q1 2027, down from 31% the quarter before. Its own full-year guide implies about 24.6% for the remaining three quarters. Atlassian earnings in Q1 FY27 land after the close on 5 November 2026, and the question worth asking is not whether Rovo is popular. It is whether bundling AI into the price has made seat growth impossible to see.

The short answer

Bundling Rovo has not visibly propped up Atlassian seat growth, because Atlassian publishes no seat count and no Rovo revenue. What the record shows is cloud growth lifted by Data Center migrations and price, with seat expansion described every quarter as "stable" or "strong". Tonight's letter can settle part of that, not all of it.

The six-quarter Atlassian cloud growth record

Start with the numbers Atlassian reports under audit-grade disclosure, because everything else in this post is interpretation. Cloud revenue is the subscription revenue from Jira, Confluence and the rest of the catalogue when Atlassian hosts it. It is now about 69% of total revenue.

The table below takes cloud revenue from each quarterly press release filed with the SEC. The sixth row is the company's own guide, not a result. We added one computed column: the dollar increase over the previous quarter, which strips out the flattering effect of percentage growth on a moving base.

Cloud revenue from Atlassian press releases for each quarter, Form 8-K exhibit 99.1. The Q1 FY27 row is our arithmetic: Q1 FY26 cloud revenue of $997.7M multiplied by the 28.5% guide. Seat language is quoted or paraphrased from the shareholder letter for the same quarter.

The dollar adds tell a flatter story

Percentage growth jumped from 26% to 31%. The dollar increase per quarter did not move the same way. Atlassian added $70.0M, $69.3M and $65.4M of quarterly cloud revenue in the first three quarters of FY26, then $81.0M in Q4.

The guide implies about $68.6M in Q1 FY27. That is back to the FY26 run rate, not a new plateau. In our view the Q4 FY26 quarter looks like a step, not a slope, until a second quarter repeats it.

What the letters credit: seat expansion, not Rovo

Atlassian is unusually consistent about what it says drives cloud revenue. Read the five letters in sequence and one phrase recurs: paid seat expansion within existing customers. It is the first driver named in Q1 FY26, Q3 FY26 and Q4 FY26.

The Q4 FY26 letter goes furthest. It describes cloud growth as "fueled by strong seat expansion in core Jira and Confluence". It also notes, in the Data Center section, "muted seat expansion as Data Center customers actively prepare their shift to Cloud". Seats are leaving one bucket and arriving in the other.

Rovo gets usage metrics, never revenue

Rovo is Atlassian's AI layer: search, chat and agents that read across Jira, Confluence and connected tools. The letters report it with engagement numbers. In Q1 FY26, Atlassian said it passed 3.5 million monthly active users of its AI capabilities, up 50% quarter on quarter.

By Q4 FY26 the claims had shifted to coverage and intensity. The letter says over 80% of Fortune 500 companies use Rovo and that Rovo-assisted actions grew over 50% quarter on quarter. Q3 FY26 added that AI credit usage was growing more than 20% month on month.

None of these is a dollar figure. That is a choice, and we think it is the right one for Atlassian and the wrong one for anyone trying to value the bundle. Disclosure practices across the sector are compared in the ranking of how software companies disclose AI revenue.

The 2x claim needs a control group

The most quoted line is that Rovo adopters grow their ARR more than 2x faster than non-adopters. It appears in both the Q3 and Q4 FY26 letters. It is also the weakest piece of evidence in the set.

Customers who switch on a new feature are, almost by definition, the engaged and growing ones. A 2x gap between adopters and everyone else would appear even if Rovo caused nothing. Atlassian does not publish a matched comparison, so treat the figure as a description of who adopts, not proof of what adoption does.

How the Atlassian Rovo pricing bundle works

Rovo reached general availability in October 2024 as a paid add-on. TechTarget reported the price at $24 per user per month below 100 users and $20 at 375 users, with volume discounts beyond that.

In April 2025, Atlassian reversed course. Rovo would be included in Premium and Enterprise cloud plans within weeks and in Standard later that year, according to TechTarget. Forrester analyst Julie Mohr told the publication that customers had struggled to prove a business case for the extra cost.

Credits and collections carry the monetisation

Bundling did not make Rovo free. It moved the meter. Atlassian's pricing FAQ says subscriptions come with a monthly allowance of metered capabilities, such as Rovo credits, with the option to buy more capacity at usage-based prices.

The bigger lever is the tier above. The Q3 FY26 letter calls Service Collection and Teamwork Collection "our primary AI monetization motion". The Q4 FY26 letter says customers upgrade to Teamwork Collection for additional Rovo credits. That is the mechanism: AI is included, more AI costs a bigger bundle.

We would make the same call in Atlassian's position. Selling AI as a $20 add-on to buyers who could not justify it was losing deals. Folding it into the base and charging for heavy use through tiers is the model examined in the comparison of AI bundling against metering.

Bundles justify price rises. Atlassian raised cloud prices by 5% to 18% by tier in October 2024, TechTarget reported. It changed list prices again on 13 October 2026. On Atlassian's own cloud pricing pages, Jira Standard for up to 100 users moves from $9.05 to $9.70 per user per month, about 7.2%.

Confluence Standard moves from $6.70 to $7.15, about 6.7%. Jira Premium rises about 7.1%. Those changes take effect two weeks after Q1 FY27 closed, so they do not touch tonight's numbers. They will touch every quarter after it, as renewals reprice.

Atlassian cloud growth minus migrations

The single biggest reason to doubt that seats or Rovo explain the acceleration is a decision Atlassian made in September 2025. It announced the end of life of its Data Center products, with the Q4 FY26 letter putting the date at March 2029. Data Center is the self-hosted version that large regulated customers run on their own servers.

Setting a hard end date converts a slow migration into a scheduled one. Atlassian guided migrations to contribute mid-to-high single digits of cloud revenue growth in FY26. It has guided the same range for FY27.

What is left for seats

Take the FY27 cloud guide of 25.5%. Remove 5 to 9 points for migrations, which is our numeric reading of "mid-to-high single digits". What remains is roughly 16.5% to 20.5% of growth from new customers, seat expansion, cross-sell into collections, and pricing.

Pricing is not zero in that remainder. A list change of about 7% on core Jira and Confluence will not land in full in one year, because annual contracts reprice at renewal and large customers negotiate. Even a partial pass-through takes several points out of the 16.5% to 20.5% band before a single new seat is counted.

That is the core of the "hiding a slowdown" case. Organic seat growth could be running in the low teens and the headline would still read mid-20s. We cannot prove that, because Atlassian does not split the remainder. We can say the headline does not rule it out.

Data Center revenue grew 44% in Q3 FY26 and 21% in Q4 FY26. The Q3 letter attributes the spike to end-of-life revenue recognition, pricing and pull-forward of purchasing. None of that is seat growth. The FY27 guide has Data Center falling about 17%, which is the bill for the pull-forward arriving.

What the Q1 FY27 guide implies for the rest of the year

Atlassian gave two cloud guides in August 2026: about 28.5% for Q1 FY27 and about 25.5% for the full year. Put them together and the arithmetic says something the press release does not.

FY26 cloud revenue was $4,410.6M. Growth of 25.5% puts FY27 at about $5,535M. Subtract the implied Q1 of about $1,282M and the remaining three quarters must total about $4,253M. The same three quarters a year earlier totalled $3,412.9M.

That is implied growth of about 24.6% for Q2 to Q4 FY27, against 31% in the quarter just reported. The company is guiding a deceleration of more than 6 points in a year that also includes a list price increase and scheduled migrations.

Why a beat is the base case

Atlassian guides conservatively. SiliconANGLE noted in August 2026 that the company's cloud guide had been 23% as recently as February. It then delivered 31% for the June quarter. A Q1 FY27 print above 28.5% would be consistent with that habit, not proof of a new trend.

The useful test is the full-year number. If Atlassian raises the 25.5% FY27 cloud guide tonight, the seat story gains weight. If it holds 25.5% after a Q1 beat, the company is telling you the back half is slower than the front. Guidance habits across the sector are tracked in the SaaS earnings guidance scorecard.

Where this argument is weakest

This post was written before the Q1 FY27 letter was public. Every forward statement here is a test, and the letter may answer it directly.

Migration seats are still seats

A Data Center customer moving to cloud brings its users with it. Atlassian can fairly say those users are paid seats, and that Jira usage grows when agents create more work. The Q1 FY26 letter said AI code generation users expand Jira paid seats at a rate about 5% higher. If coding agents are generating tickets, AI is adding seats, not subtracting them.

The migration range is a guide, not a result

"Mid-to-high single digits" is Atlassian's expectation, not a disclosed outcome. The realised contribution could sit at the low end. If migrations added 5 points rather than 9, the non-migration remainder of FY27 growth is about 20%, which is a healthy number for a company of this size.

NRR is still above 120%

The Q2 FY26 letter reported cloud net revenue retention of 120%+, up for a third consecutive quarter. Net revenue retention measures how much a cohort of customers spends this year against last, after churn. A company hiding a seat slowdown would not usually see that line rising. The contrary view deserves credit: the data Atlassian publishes is more consistent with steady seats than with collapsing ones.

Our position is narrower than "Atlassian is hiding a slowdown". It is that bundling, migrations and price make the seat story unfalsifiable from outside, and that the burden of proof sits with the company.

Five lines to read in the Q1 FY27 letter

Skip the Rovo engagement figures on the first pass. They will be large and they will be up. Read these instead, in this order.

The fourth row matters most. "Stable seat expansion with higher ARPU" means price and tier mix are doing more of the work. ARPU, or average revenue per user, rises when customers pay more per seat. In Q3 FY26 Atlassian listed higher ARPU alongside seats as a cloud driver. Watch whether it climbs the list.

What AI bundling teaches SaaS pricing teams

Atlassian's choice is now the default playbook. Include the AI, meter heavy use with credits, and route serious users into a higher tier. It solves the buyer's problem of justifying a separate AI line item, which was the problem Forrester's Mohr described in April 2025.

It creates a reporting problem in exchange. Once AI is inside the seat price, no one outside the company can tell whether AI is selling seats or seats are carrying AI. The same blur affects every vendor moving to included credits, from HubSpot to Salesforce, and it is examined across the sector in the review of how productivity software discloses seats.

If you run a SaaS business and bundle AI, report three numbers internally from day one: seat growth, price and mix effect, and credit overage revenue. The vendors that cannot separate them will struggle to defend a price rise at renewal. The pressure behind that is covered in the analysis of seat compression in SaaS pricing.

If you buy Atlassian, the October 2026 list change is about 7% on Jira and Confluence Standard and Premium. Combined with Data Center end of life, the leverage in your next renewal is shifting toward the vendor. The renewal mechanics are set out in the guide to grandfathered pricing at renewal.

Frequently asked questions

Where to start

Open the Q1 FY27 letter tonight and search it for two strings: "25.5" and "migrations". Whether the full-year cloud guide moves, and how the company now sizes migrations, tells you more about seat health than any Rovo statistic in the deck.

If you own a Jira or Confluence renewal in the next 12 months, ask your account team in writing which price applies, which Rovo credit allowance applies, and what happens to both if you stay on your current tier.

Related reading