Markets 8 August 2026 11 min read

Atlassian Jumped 35% on a 13% Revenue Guide (August 2026): Why the Market Priced ARR at 18% Instead — and What the March 2029 Data Center Deadline Did to Both Numbers

Atlassian rose from $110.17 to $149.07 on 7 August after guiding FY27 revenue growth to just 13%. Here's why ARR at 18% and cloud at 25.5% mattered more.

Atlassian Jumped 35% on a 13% Revenue Guide (August 2026): Why the Market Priced ARR at 18% Instead — and What the March 2029 Data Center Deadline Did to Both Numbers

Atlassian closed at $110.17 on Thursday 6 August 2026, reported fourth-quarter results after the bell, and closed at $149.07 on Friday — a gain of about 35% in one session, on a company whose headline guidance for the coming year was roughly 13% revenue growth, down from 26%. That combination is the whole story. In the same guide the company put three different growth rates on the table: total revenue about 13%, subscription ARR about 18%, and cloud revenue about 25.5%. They describe the same business. The gap between them is an accounting timing effect created by the company's own decision, announced in September 2025, to end-of-life its Data Center product in March 2029 — and the market decided which of the three numbers was the business and which was the artefact.

This is a post about how to read a growth rate, not about whether anyone should own the shares. The mechanism generalises well beyond one software company: any business winding down a legacy product line under US revenue-recognition rules will produce a headline number that flatters one year and punishes the next, and the reader's job is to work out which part of the move is economics and which part is calendar.

Key takeaways
  • Atlassian went from $110.17 to $149.07 on 7 August 2026, roughly +35%, after Q4 FY26 beat on every guided line: revenue $1,766m (+28% y/y), cloud revenue $1,213m with growth accelerating to 31%, adjusted EPS $1.87 against roughly $1.50 expected.
  • The FY27 guide contains three growth rates for one company: ~13% total revenue, ~18% subscription ARR, ~25.5% cloud. The company itself said ARR is "a clearer measure of the underlying strength."
  • The wedge is ASC 606. After the September 2025 decision to end-of-life Data Center in March 2029, a higher share of Data Center contract value is recognised upfront, and customers pulled purchases forward. That inflated FY26 and creates the FY27 drag; the company expects total growth to re-accelerate in FY28.
  • The cloud line was attributed to seat expansion in core Jira and Confluence — direct evidence against the 2026 thesis that AI agents shrink per-seat software revenue. Whether it generalises is a separate question.
  • None of this touched a NAS100 position: Nasdaq removed Atlassian from the Nasdaq-100 on 20 April 2026, replaced by SanDisk. The index channel here is read-across, not weight.
  • The same session, Twilio rose about 24% on a usage-based model — the opposite pricing structure, the same direction. See how the rate and risk factors are scoring the currencies behind all of it on the live meter.

What actually happened

Atlassian reported Q4 and full-year fiscal 2026 on 6 August 2026. The quarter beat across the board. Total revenue of $1,766m grew 28% year-on-year. Cloud revenue of $1,213m grew 31% — an acceleration for a second straight quarter, against 26% in each of the first two quarters of FY26 and 29% in the third. Subscription ARR reached $6,606m, up 23%. Remaining performance obligations — contracted revenue not yet recognised — grew 44% to $4,817m, with the current portion up 27%.

Profitability moved more than the top line. GAAP operating margin was 12%, up 14 percentage points from the prior year; non-GAAP operating margin was 36%, up 12 points. GAAP diluted earnings per share of $0.55 replaced a $0.09 loss a year earlier, and adjusted EPS of $1.87 landed against a consensus near $1.50. Free cash flow was $475m, up 32%, absorbing roughly $70m of severance payments from a restructuring the company carried out in its third quarter. Over the full year Atlassian repurchased 19.1m shares for $1.8bn, cutting share count by about 4%.

The enterprise detail underneath was the part that changes a growth model: a record quarter for $1m-plus, $3m-plus and $5m-plus annual-contract-value deals, customers above $3m in ARR growing more than 50% year-on-year and those above $5m growing more than 70%, and 57,334 customers above $10,000 in cloud ARR accounting for over 85% of cloud ARR. All figures are from the company's Q4 FY26 shareholder letter, filed with the SEC.

The tape around it: the S&P 500 closed at a record 7,757.64, up 0.62%, and the Nasdaq Composite rose 1.3% to 26,690.62, in a session where a July payrolls print showing a net loss of 23,000 jobs pushed the market's read of near-term Federal Reserve policy toward patience. That backdrop matters for the multiple, and we come back to it below.

Three growth rates, one company

Here is the guide the market had to interpret, alongside what the business just did.

Measure FY26 actual FY27 guide What it is measuring
Total revenue growth 26% ~13% Revenue recognised under ASC 606, including upfront term licences
Subscription ARR growth 23% ~18.0% Annualised recurring contract value at a point in time
Cloud revenue growth 31% (Q4) ~25.5% The part of the business customers are migrating into
Non-GAAP operating margin 30% ~25% Profitability, guided lower on continued investment

Note the shape. Total revenue growth is guided to less than half its FY26 rate. Cloud growth is guided down by about five and a half points. ARR is guided down by five. If demand were deteriorating, all three would fall together and roughly in proportion. They do not — and the company gave the reason explicitly.

Why upfront recognition distorts a growth rateUnder ASC 606, revenue from a term licence — software a customer installs and runs itself — is largely recognised at delivery rather than spread across the contract. When Atlassian announced in September 2025 that its Data Center product would reach end-of-life in March 2029, two things followed: a higher proportion of each Data Center contract began landing in revenue upfront, and customers pulled purchasing forward from later periods. Both effects lifted FY26. Neither repeats. Data Center revenue grew 44% year-on-year in Q3 FY26 and 21% in Q4; the company expects it to decline in FY27, which is the mechanical source of the drag on total growth — and the reason it expects total revenue growth to re-accelerate in FY28 as the comparison laps.
Sept 2025: end-of-life announcedData Center set to retire in March 2029.
Recognition shifts forwardMore contract value booked upfront; customers pull purchases into FY26.
FY26 total revenue flatters26% growth, with Data Center up 44% in Q3 and 21% in Q4.
FY27 comparison punishesData Center declines; total growth guided to ~13% while ARR holds ~18%.

This is why the company wrote that it views subscription ARR as the clearer measure of underlying strength — because ARR normalises "the variable revenue patterns and the timing effects of ASC 606." A reader does not have to accept that framing to use it. The point is that the 13% and the 18% are answers to different questions, and knowing which question you care about is the entire analytical task.

The seat thesis meets a real quarter

The reason a software company was priced for something close to decline in the first place is a thesis that dominated 2026: that autonomous AI agents do work previously done by licensed humans, and that per-seat subscription revenue therefore shrinks with the headcount it is priced against. The de-rating was broad enough that the label "SaaSpocalypse" attached itself to the sector, and Atlassian was among the names it hit hardest. The clearest institutional evidence of that: Nasdaq announced on 10 April 2026 that SanDisk would replace Atlassian in the Nasdaq-100 Index before the open on 20 April. An index committee does not have a view on AI; it has a methodology, and the methodology ejected the company.

What the quarter put on the other side of the ledger is specific. Cloud growth of 31% was attributed to seat expansion in core Jira and Confluence, alongside cross-sell into the company's bundled Collections and higher revenue per user — with paid seat expansion rates described as stable. On the AI side: Rovo assisted actions rose more than 50% quarter-on-quarter; over 80% of Fortune 500 companies use Rovo; Rovo adopters grow ARR more than twice as fast as non-adopters; monthly active users of the company's MCP server and Teamwork Graph CLI more than doubled in the quarter to pass one million, with MCP calls up more than 400%; and 98% of MCP users were also active in the Jira interface in the same month.

That last figure is the mechanism in miniature. If agents were substituting for seats, you would expect agent usage to concentrate where human usage is falling away. What the company reported is the opposite pattern — agent traffic arriving alongside continued human presence in the same product, in the same month. One quarter at one company is evidence, not proof, and the honest position is that the thesis has been complicated rather than closed.

The contrast that made the session legible came from a different pricing model entirely. Twilio reported Q2 2026 the same evening and rose about 24% on 7 August, from $193.20 to roughly $240: revenue near $1.5bn, up 22% with organic growth accelerating to 17%, adjusted EPS of $1.47 against about $1.32 expected, and full-year revenue growth guidance raised from 14–15% to 18–18.5%. Twilio charges for usage — messages, voice minutes, API calls — which is the structure the agent thesis is supposed to favour, since more agents mean more calls. A seat-priced company and a usage-priced company rallying hard on the same night is a category being repriced, not a business model being vindicated. We covered the same dynamic from the infrastructure side in how the web started charging AI agents.

Where a 35% move actually shows up

For a reader who trades an index rather than a single name, the arithmetic here is deflationary in a useful way. Atlassian's market value entering the print was roughly $29bn. A 35% gain adds about $10bn. And because Nasdaq removed the company from the Nasdaq-100 on 20 April 2026, a NAS100 or NDX position held none of it in the first place — the weight moved to SanDisk months ago.

This is the same mechanical point we worked through when a much larger float change ran through Nasdaq-100 weights: index membership and weight, not headline drama, determine whether a move reaches your instrument. A 35% single-day gain in a non-constituent is invisible to the future you are trading.

What does reach the index is read-across. If the market takes Atlassian's seat-expansion figures as evidence about the software category rather than about one company, that changes how the constituent software names are priced — and there the weights are real. The read-across channel is slower, noisier and impossible to size in advance, which is precisely why it is worth naming rather than assuming.

The rate channel, and why software feels it most

There is a macro leg to this, and it is not decoration. Subscription software is among the longest-duration cash-flow profiles in the equity market: the value sits in renewals years out, so the discount rate applied to those years does more work than in a business earning its cash now. That makes the software complex unusually sensitive to the front end of the US curve — which is why the same 7 August session that delivered these results also delivered a July payrolls print showing a net loss of 23,000 jobs, and why the market's read of Federal Reserve patience is part of the backdrop rather than a separate story. We walked through that print and its dollar channel in the July payrolls breakdown.

The direction of that link is worth stating carefully. A softer labour market lowers the path of expected policy rates, which raises the present value of distant cash flows, which supports long-duration equities — and simultaneously tends to weigh on the currency through the interest-rate factor, one of the five the meter scores for the US dollar. Those two effects are not in conflict; they are the same repricing seen from the equity side and the FX side. A reader who wants the currency half of that picture can see how the rate factor is scoring the majors on the live meter, and how the framework works on the about page.

The rate factor moves software multiples and currencies through the same channel.Open the live meter →

What would change the picture

Four falsifiers, in order of how quickly they surface.

Subscription ARR. The company has told the market this is the number that matters. That framing is only defensible while the number holds. An ARR print materially below the roughly 18% FY27 path removes the argument that the revenue guide is a timing artefact, because ARR is the measure that strips the timing out.

Cloud growth. Guided to about 25.5% against 31% delivered in Q4. Some deceleration is built in — the company is lapping the first full year of its bundled Collections. A sharper one is not, and cloud is where the migration is supposed to land.

Paid seat expansion. Described as stable. This is the cleanest single test of the agent thesis available anywhere in the sector, because it is a direct count of licensed humans at a company whose own AI products are being adopted at speed. If seats roll over while Rovo usage keeps climbing, the bear case gets its evidence.

Migration integrity. The March 2029 end-of-life makes the FY27 drag scheduled and knowable. What is not knowable is whether Data Center customers land in Atlassian's cloud or somewhere else. The expected FY28 re-acceleration depends entirely on the first outcome.

The transferable lesson

Strip out the ticker and this is a lesson about accounting calendars. A company that announces the retirement of a product line changes when it books that line's revenue, not just whether it earns it. The year of the announcement gets a windfall; the following year eats the comparison. Anyone reading only the headline growth rate will see acceleration followed by collapse and conclude that something happened to demand, when what happened was a recognition boundary moving.

The defence is mechanical: when a guide contains more than one growth rate, find out why they differ before deciding which one is the company. Here the three numbers were 13%, 18% and 25.5%, the reason for the spread was disclosed in the shareholder letter, and roughly $10bn of market value moved on which one investors thought was load-bearing. That is a question of measurement, and measurement questions have answers.

Educational macro context only — not investment advice.

Advertisement

Frequently asked

Why did Atlassian stock jump 35% on 7 August 2026?
Because the quarter it reported and the number it guided to were measuring two different things, and the market chose the one it believed. Atlassian closed at $110.17 on Thursday 6 August, reported Q4 FY26 after the bell, and closed at $149.07 on Friday 7 August — a gain of about 35%. The results beat on every guided line: total revenue of $1,766m grew 28% year-on-year against a consensus near $1.66bn, cloud revenue of $1,213m accelerated to 31% growth, and adjusted earnings of $1.87 a share came in against roughly $1.50 expected. GAAP operating margin was 12%, up 14 percentage points from a year earlier, which turned a prior-year GAAP loss per share of $0.09 into $0.55 of GAAP diluted earnings. The headline FY27 guide of approximately 13% total revenue growth looks like a collapse next to FY26's 26%, but the company also guided subscription ARR to grow about 18% and cloud revenue about 25.5% — and explained in its shareholder letter that the gap is an accounting and timing artefact of winding down its Data Center product, not a demand signal.
What is ASC 606 and why does it matter for Atlassian's revenue growth?
ASC 606 is the US revenue-recognition standard that determines when a company books cash it has contracted for. For term licences — software a customer runs on its own hardware — a large share of the contract value is recognised as revenue upfront, at the moment of delivery, rather than spread across the subscription period. In September 2025 Atlassian announced it would end-of-life its Data Center product in March 2029. That announcement changed the accounting: as the company puts it, a higher proportion of Data Center contract value is now recognised upfront. Customers also pulled purchases forward. The combined effect inflated FY26 Data Center revenue — it grew 21% in Q4 and 44% in Q3 — and leaves a hole in FY27, when that same revenue cannot be recognised twice. Atlassian expects Data Center revenue to decline in FY27, dragging total growth to roughly 13%, and expects total revenue growth to re-accelerate in FY28 once the effect laps. This is why the company said it views subscription ARR as the clearer measure of underlying strength: ARR normalises the timing effects.
Does the 35% move affect the Nasdaq 100 or NAS100 index?
No — not directly, and this is a detail many readers get wrong. Atlassian is not a Nasdaq-100 constituent. Nasdaq announced on 10 April 2026 that SanDisk would replace Atlassian in the Nasdaq-100 Index before the market open on Monday 20 April 2026. So whatever happened to the shares on 7 August, an NDX or NAS100 position owned none of it. The company's market value entering the print was roughly $29bn; even a 35% gain adds about $10bn, an amount that would be a rounding error inside a mega-cap-dominated index in any case. The transmission to an index trader runs entirely through read-across — whether the print changes how the market prices other software companies that are index constituents — and not through the weight of this one name.
Does AI destroy per-seat software revenue?
This print is one data point against that thesis, not a resolution of it. The bear argument — that autonomous agents do work previously done by licensed humans, so per-seat subscription revenue shrinks as headcount does — drove a broad de-rating of subscription-software shares through 2026. Atlassian's Q4 gave the counter-evidence in the company's own words: cloud revenue accelerated to 31% growth, attributed to strong seat expansion in core Jira and Confluence alongside cross-sell and higher ARPU, with 57,334 customers now above $10,000 in cloud ARR. Atlassian also reported that customers adopting its Rovo AI tools grow ARR more than twice as fast as non-adopters, and that monthly active users of its MCP server and Teamwork Graph CLI more than doubled in the quarter to surpass one million. The honest reading is narrower than either side's slogan: at this company, in this quarter, agent adoption ran alongside seat growth rather than against it. Whether that generalises across the software complex is exactly what the next few earnings seasons test.
Why did Twilio also rise sharply the same day?
Twilio reported Q2 2026 results the same evening, and its shares rose about 24% on 7 August, from a $193.20 close to roughly $240. Revenue was about $1.5bn, up 22% year-on-year with organic growth accelerating to 17%, adjusted earnings were $1.47 a share against roughly $1.32 expected, and the company raised its full-year 2026 revenue growth guidance from 14–15% to 18–18.5%. The mechanism is different from Atlassian's in a way worth noticing: Twilio charges by usage — messages, calls, API requests — not by seat. Under the agent thesis, usage-based pricing is the natural beneficiary, because software agents generate more calls, not fewer. Two names with opposite pricing models rallying on the same night is why the session read as a repricing of the category rather than a verdict on one business model.
What would change this picture?
Four things, in rough order of how quickly they would show up. First, subscription ARR growth: Atlassian has told the market this is the number that matters, so an ARR print materially below the roughly 18% FY27 path removes the argument that the revenue guide is an artefact. Second, cloud revenue growth: guided to about 25.5%, against 31% in Q4 — the deceleration is expected, a sharper one would not be. Third, paid seat expansion, which the company describes as stable; a reversal there is the single cleanest test of the agent thesis. Fourth, the Data Center migration path itself — the March 2029 end-of-life means this drag is scheduled, and the FY28 re-acceleration the company points to depends on migrations landing in cloud rather than leaking elsewhere.
PT
Pip Theory desk

We build the tools we write about. Educational macro context only — never investment advice.

About the desk