GitLab Q2 FY2027: $56.9M GAAP operating loss, $42.6M non-GAAP profit
Revenue of $286.3 million came in above the top of the $272–274 million range GitLab guided to in its June 2, 2026 8-K, and non-GAAP operating income of $42.6 million and non-GAAP EPS of $0.24 topped the $30–32 million and $0.17–0.18 guides; year over year, revenue rose 21% while non-GAAP EPS was flat at $0.24. Most of the $99 million gap between the two profit lines is $75.0 million of stock-based compensation.
- Results reported
- , after the close
- Analysis published
- Period covered
- Q2 FY2027 — quarter ended July 31, 2026
- Last updated
What changed this quarter
GitLab reported Q2 FY2027 revenue of $286.3 million, up 21% year over year, beating the Zacks consensus of about $273 million and posting non-GAAP EPS of $0.24 against $0.18 expected. Revenue of $286.3 million came in above the top of the $272–274 million range GitLab guided to in its June 2, 2026 8-K, and non-GAAP operating income of $42.6 million and non-GAAP EPS of $0.24 topped the $30–32 million and $0.17–0.18 guides; year over year, revenue rose 21% while non-GAAP EPS was flat at $0.24. Dollar-based net retention reaccelerated to 117% and customers with more than $100k of ARR rose 17% to 1,571. But the profit depends entirely on the lens: a GAAP operating loss of $56.9 million (a -20% margin that widened from -8% a year ago) becomes a $42.6 million non-GAAP operating profit only after adding back $75.0 million of stock-based compensation — 26% of revenue — and a one-time $19.4 million restructuring charge. Operating cash flow was actually negative $3.1 million for the quarter on a receivables swing, and the $9.8 million 'adjusted' free cash flow leans on a $14.0 million JiHu add-back.
GTLB Q2 FY2027 key figures
Total revenue
$286.3M
+21% YoY
GAAP operating margin
-20%
widened from -8% YoY
Non-GAAP operating income
$42.6M
15% margin, down from 17%
Stock-based comp
$75.0M
26% of revenue
Dollar-based net retention
117%
reaccelerated sequentially
Adjusted free cash flow
$9.8M
incl. $14.0M JiHu add-back
How is your own portfolio doing against SPY?
Add what you hold — no brokerage login — and Tradune puts your money-weighted return next to a buy-and-hold SPY twin funded on the same dates.
Free for everyone right now · no card · nothing to buy
GitLab sells the software factory floor — a single platform where engineers plan, write, secure, and ship code, now stretched to cover AI agents doing the same work alongside them. In its second fiscal quarter, that business grew revenue 21% to $286.3 million, beat the Street on both the top and bottom line, and reported that dollar-based net retention had reaccelerated to 117%. Those are the facts a bull leads with, and they are real.
The one thing worth understanding before you accept the headline “non-GAAP profit” is what stands underneath it. The same three months produced a $56.9 million GAAP operating loss — a -20% operating margin that got worse than the -8% a year ago — and a $42.6 million non-GAAP operating profit. The $99 million gap between those two numbers is the entire analysis, and most of it is one line: $75.0 million of stock-based compensation, 26% of revenue.
The quarter, as reported
Consensus first, because it frames the beat. Wall Street (the Zacks consensus, per the preview cited below) expected roughly $273.3 million of revenue and about $0.18 of non-GAAP EPS. GitLab delivered $286.3 million and $0.24. A clean beat on both lines.
| Q2 FY27 | Consensus (Zacks) | ||
|---|---|---|---|
| Total revenue | $286.3M | ~$273.3M | beat |
| Non-GAAP diluted EPS | $0.24 | ~$0.18 | beat |
| Non-GAAP operating income | $42.6M | — | 15% margin |
| GAAP operating loss | −$56.9M | — | −20% margin |
| Dollar-based net retention | 117% | — | reaccelerated |
Now the income statement itself, GitLab’s own figures, with the year-ago quarter beside it.
| $ thousands | Q2 FY27 | Q2 FY26 | YoY |
|---|---|---|---|
| Subscription — self-managed & SaaS | 258,311 | 212,684 | +21% |
| License — self-managed & other | 27,943 | 23,276 | +20% |
| Total revenue | 286,254 | 235,960 | +21% |
| Total cost of revenue | 45,638 | 28,505 | +60% |
| Gross profit | 240,616 | 207,455 | +16% |
| Sales & marketing | 134,363 | 109,583 | +23% |
| Research & development | 94,980 | 71,488 | +33% |
| General & administrative | 68,208 | 44,735 | +52% |
| Loss from operations | (56,935) | (18,351) | loss widened |
| Interest income | 12,202 | 11,511 | +6% |
| Other income (expense), net | 5,406 | (911) | — |
| Net loss attributable to GitLab | (36,844) | (9,208) | loss widened |
| GAAP EPS (basic & diluted) | (0.22) | (0.06) | — |
Two things jump off that table. First, cost of revenue grew 60% against 21% revenue growth, so GAAP gross margin fell to 84% from 88% — the first sign that this quarter carried heavier costs than the growth alone would suggest. Second, every operating expense line grew faster than revenue, G&A most of all at +52%, and the operating loss more than tripled to $56.9 million. On a GAAP basis, this was a worse quarter than a year ago, not a better one.
Did GitLab beat its own guidance in Q2 FY2027?
Yes. Revenue of $286.3 million came in above the top of the $272–274 million range GitLab guided to in its June 2, 2026 8-K, non-GAAP operating income of $42.6 million was above the guided $30–32 million, and non-GAAP diluted EPS of $0.24 was above the $0.17–0.18 guide. Year over year, revenue rose 21%, non-GAAP EPS was flat at $0.24, and the GAAP net loss attributable to GitLab widened to $36.8 million from $9.2 million. GitLab then raised its full-year guidance: revenue to $1,129–1,133 million from $1,112–1,118 million, and non-GAAP operating income to $148–152 million from $135–141 million.
The $99 million bridge
Hold the GAAP operating loss of −$56.9 million next to the non-GAAP operating profit of +$42.6 million. That is a $99.5 million swing, and GitLab itself lists exactly what fills it:
| Add-back to GAAP operating loss | Q2 FY27 ($000) |
|---|---|
| Stock-based compensation | 75,006 |
| Restructuring charges (May 2026 plan) | 19,422 |
| Amortization of acquired intangibles | 2,015 |
| Other non-recurring charges | 1,285 |
| Charitable donation of common stock | 1,166 |
| Acquisition-related expenses | 607 |
| Total add-backs | 99,501 |
| GAAP loss from operations | (56,935) |
| Non-GAAP income from operations | 42,566 |
Read the two largest lines carefully, because they are different kinds of number.
Stock-based compensation of $75.0 million is the whole story. It is 26% of revenue — more than a quarter of every dollar of sales handed to employees in shares — and it is larger than the entire non-GAAP operating profit it produces ($42.6 million). Without the add-back there is no non-GAAP profit; there is a loss. And it is not shrinking: SBC was 23% of revenue a year ago and rose to 26% this quarter. This is the standard shape of a growth-software income statement, but the magnitude is the point — the non-GAAP profit is, in substance, the SBC add-back with the rest of the business roughly breaking even around it.
The $19.4 million restructuring charge is a one-timer, and it flatters the comparison in a way worth naming. GitLab announced a restructuring in May 2026, and this charge — severance, retention, and accelerated vesting — is genuinely non-recurring; excluding it is defensible. But it also means the GAAP operating loss you see (−$56.9 million) is inflated by a cost that will not repeat, while the non-GAAP profit is not helped by it recurring either. Strip the restructuring out of both, and the underlying GAAP operating loss was about −$37.5 million, a -13% margin — still worse than the -8% a year ago. So even setting the one-timer aside, GAAP operating profitability moved backward this quarter, driven by the rising SBC and the gross-margin compression.
Non-GAAP profit barely grew, and the margin fell
Here is the subtlety the beat headline hides. Yes, GitLab reported a non-GAAP operating profit. But compare it to a year ago: $42.6 million this quarter versus $39.6 million a year ago — up just $3.0 million, or 8%, on revenue that grew 21%. The non-GAAP operating margin actually fell, from 17% to 15%.
That is the opposite of operating leverage. A software business scaling well should see profit grow faster than revenue as fixed costs spread over a bigger base; GitLab’s grew a quarter as fast. The CFO’s language — “meaningful operating leverage” — describes the full-year trajectory (six-month non-GAAP operating income of $80.1 million was up 22%), but the single quarter shows margin compression, not expansion, because of the gross-margin step-down and the faster opex growth.
Put the two profit lenses together and you get the honest picture: GAAP operating profitability got worse, and non-GAAP operating profitability, while positive, thinned out. The 21% revenue beat is real; the profitability of that revenue softened.
Rule of 40, and the leading indicators
A quick discipline check for a growth-software name is the “Rule of 40” — revenue growth plus profit margin should clear 40. On GitLab’s non-GAAP operating margin, that is 21% growth + 15% margin = 36 — below the line, and below where GitLab has historically sat as growth has decelerated from the 30%-plus rates of earlier years. It is not a failing grade; it is a company drifting from “hypergrowth” toward “durable-grower,” which is exactly the transition the market watches at this size. (This is our arithmetic from the disclosed figures, not a GitLab-reported metric.)
The forward indicators are more encouraging than the reported revenue, and they are the reason the quarter was received as strong:
- Dollar-based net retention reaccelerated to 117%, which the CFO called a sequential acceleration. Existing customers are spending more, and the direction reversed higher — the single most important health signal for a subscription business.
- Customers with more than $100,000 of ARR reached 1,571, up 17% year over year; customers over $5,000 of ARR reached 11,114, up 8%. The enterprise end of the base is growing faster than the long tail — the healthy mix.
- cRPO (current remaining performance obligations) grew 20% to $744.7 million, and total RPO reached $1.2 billion, up 16%. cRPO is contracted revenue due within a year and leads reported revenue; at +20% it is running slightly ahead of the 21% revenue print, which argues the top line is not about to fall off.
- Management also cited record gross bookings, net ARR growth exceeding 40%, and first-order growth over 100%. These are qualitative or non-standardized, so weight them less than cRPO — but they point the same direction.
Cash: the quarter was actually cash-negative
This is where a reader has to slow down, because “adjusted free cash flow of $9.8 million” is doing more work than it looks.
GAAP operating cash flow for the quarter was negative $3.1 million, versus a positive $49.4 million a year ago — a $52.5 million swing to the downside. The cause is visible in the cash-flow statement: accounts receivable was a $57.3 million use of cash this quarter (it released $3.9 million a year ago), a collections-timing swing rather than a deterioration in the business. Over the full six months, operating cash flow was a healthy positive $146.1 million, which confirms the quarterly negative is timing, not trend.
But the reported “adjusted free cash flow of $9.8 million” only clears zero because of a $14.0 million add-back for one-time payments tied to GitLab’s JiHu joint-venture in China. Do the plain calculation — operating cash flow of −$3.1 million minus $0.2 million of capex — and unadjusted free cash flow was about −$3.3 million. The company’s adjustment is disclosed and arguably fair, but the takeaway is that on a cash basis this was a roughly breakeven-to-slightly-negative quarter, propped to positive by a non-recurring add-back. The six-month adjusted free cash flow of $156.5 million is the number that shows the real cash engine; the single quarter does not.
The balance sheet is a fortress, and it is buying back its own dilution
GitLab ended the quarter with $226.5 million of cash plus $1,030.5 million of short-term investments — about $1.26 billion — and no debt. Deferred revenue (billings already collected, revenue not yet recognized) stood at $574.7 million. There is no solvency question here whatsoever.
The most interesting balance-sheet fact ties back to the SBC problem. GitLab repurchased about 3.5 million shares for $104.6 million in the quarter ($154.7 million over six months). Set that against six-month stock-based compensation of $125.1 million: the buyback is more than offsetting the dilution from stock grants. Total shares outstanding actually fell, from about 170.1 million at the start of the year to 167.3 million at quarter-end. So the per-share dilution that usually accompanies 26%-of-revenue SBC is, for now, being neutralized — but with cash, from a company whose quarterly free cash flow was roughly zero. GitLab is using its balance sheet to convert a dilution problem into a cash-outflow problem. That is a defensible choice at a $1.26 billion cash pile, and it is a choice a shareholder should see clearly rather than take on faith from the flat share count.
The bear case, stated fairly
Not “the growth is fake” — 21% revenue growth with 117% retention is a healthy business. The narrower version:
- GAAP operating profitability moved backward. The operating loss widened to −$56.9 million (−20% margin) from −$18.4 million (−8%), and even excluding the one-time restructuring it was worse than a year ago. Gross margin fell four points. The direction on GAAP profit this quarter was the wrong one.
- The non-GAAP profit is the SBC add-back. Stock comp at 26% of revenue is larger than the entire non-GAAP operating profit, and it rose as a share of revenue. The headline profit exists because that cost is excluded.
- Non-GAAP margin compressed as revenue grew 21%. Operating income up 8% on revenue up 21% is negative operating leverage for the quarter — the opposite of the scaling story, and the Rule-of-40 math lands at 36.
- The quarter was cash-flat. Operating cash flow was −$3.1 million and unadjusted free cash flow about −$3.3 million; the reported $9.8 million leans on a one-time JiHu add-back.
- Guidance implies a sequential revenue decline. Q3 revenue is guided to $281–283 million, below the $286.3 million just reported — a function of lumpy upfront-recognized self-managed license revenue, but a sequential step-down nonetheless.
The bull case, from the same numbers
- Retention reaccelerated to 117%. The cleanest signal in the release; existing customers are expanding and the trend turned up.
- cRPO grew 20%, slightly ahead of revenue, so the forward book supports the top line rather than warning of a slowdown.
- The enterprise base is compounding — $100k+ customers up 17% — which is where GitLab’s platform pricing power lives.
- A $1.26 billion net-cash balance sheet funds the R&D and the buyback that is holding share count flat, and the six-month cash engine ($146 million operating, $156 million adjusted free cash flow) is genuinely strong even if this single quarter was not.
- They beat and raised while investing. Full-year revenue guidance stands at $1,129–1,133 million and non-GAAP operating income at $148–152 million — profitable growth on a non-GAAP basis, with an AI-agent product roadmap (Duo, Orbit, Flex) attached to the demand story.
What to check at the Q3 report
Specific and falsifiable, in rough order of importance:
- Dollar-based net retention. Did 117% hold or keep climbing? This is the number that decides whether the reacceleration is a trend or a blip.
- Non-GAAP operating margin. Whether it stabilizes near 15% or resumes expanding — the test of whether “operating leverage” is real at the quarterly level, not just year-to-date.
- Stock-based compensation as a percent of revenue. Whether it trends down from 26% as the company scales, or stays put. This is the dilution dial, and the buyback’s sustainability rides on it.
- GAAP operating loss ex-restructuring. Whether the underlying loss narrows once the one-time charge is behind them, or the gross-margin compression persists.
- Operating cash flow. Whether the receivables swing reverses and quarterly cash generation returns to positive without needing add-backs.
- cRPO growth. The forward book; whether it holds above the reported revenue growth rate.
The read
GitLab beat consensus, grew 21%, and reaccelerated retention to 117% — a good quarter for the growth story, and the bookings and cRPO signals say the top line is durable. If the question is “is the business healthy and expanding,” the answer this quarter is yes.
The discipline is to read the profit with the same care. This one quarter is simultaneously a −20% GAAP operating margin that widened year over year and a +15% non-GAAP operating margin that narrowed — and the $99 million bridge between them is three-quarters stock-based compensation, a cost that at 26% of revenue is larger than the non-GAAP profit itself. The cash flow, usually the tiebreaker, was roughly zero for the quarter and positive only after a one-time add-back; the six-month figures are the ones that show the real engine. Hold the retention reacceleration and the cRPO as the bull case, hold the rising SBC and the backward step in GAAP margin as the bill, and check dollar-based net retention and non-GAAP operating margin first at the next report. The growth is the reason to own it; the widening gap between the two profit numbers is the reason to size it knowing which one you are buying.
Sources and method. Company figures in this piece — total, subscription, and license revenue and their growth rates; GAAP and non-GAAP gross margin; GAAP loss from operations of $56.9 million and non-GAAP income from operations of $42.6 million and their margins; the full GAAP-to-non-GAAP operating bridge including stock-based compensation of $75.0 million, the $19.4 million restructuring charge, amortization, charitable donation, acquisition, and other non-recurring lines; GAAP net loss attributable to GitLab of $36.8 million and GAAP EPS of −$0.22; non-GAAP net income of $42.1 million and non-GAAP diluted EPS of $0.24; interest income; operating cash flow of −$3.1 million and adjusted free cash flow of $9.8 million (and the six-month figures of $146.1 million and $156.5 million); the $14.0 million JiHu add-back and $0.2 million of capex; the $226.5 million cash and $1,030.5 million short-term-investment balances and $574.7 million of deferred revenue; the $104.6 million ($154.7 million six-month) share repurchase and ~3.5 million shares; dollar-based net retention of 117%; customers over $100,000 (1,571, +17%) and over $5,000 (11,114, +8%) of ARR; RPO of $1.2 billion and cRPO of $744.7 million; and the Q3 and full-year FY2027 guidance — are GitLab’s own disclosures from its Q2 FY2027 results release (Form 8-K, Exhibit 99.1) filed 2026-09-01 for the quarter ended 2026-07-31, reported after the close, with the balance-sheet and cash-flow detail corroborated by the Form 10-Q filed 2026-09-02. Prior-year comparatives are the year-ago columns in that same release.
Not company figures, and attributed accordingly: the consensus estimates (revenue ~$273.3 million, non-GAAP EPS ~$0.18) are the Zacks consensus as reported in the Zacks/TradingView preview cited above. Whether the quarter beat or missed its own targets is judged only against the company’s own previously issued guidance (Form 8-K, Exhibit 99.1, filed 2026-06-02: Q2 revenue of $272–274 million, non-GAAP operating income of $30–32 million, non-GAAP diluted EPS of $0.17–0.18) and against the year-ago quarter; the third-party figures are reported separately and play no part in that verdict. This piece makes no claim about the share-price reaction. The interpretation — that the non-GAAP operating profit is substantially the stock-comp add-back, that GAAP operating profitability moved backward even excluding the one-time restructuring, that the quarter was roughly cash-flat before the JiHu add-back, that the buyback is neutralizing dilution with cash, and that the Rule-of-40 math lands at 36 — is our analysis, computed from the disclosed dollars (“our arithmetic,” and approximate where rounded), not a company statement and not a forecast. Every percentage and ratio above was recomputed from the filing’s dollar figures and ties to the disclosed totals.
Related: CrowdStrike Q2 FY2027, the security-software name where the same GAAP-versus-non-GAAP, stock-comp-add-back debate is the whole story; Palantir Q2 2026, another high-multiple software business where the gap between the two profit lenses defines the argument; and Shopify Q2 2026, a larger software platform to compare durable-growth economics against.
Tradune shows what you actually hold across every account, and whether a position has beaten a plain index fund since you bought it. Educational analysis, not investment advice.
How exposed is your portfolio to this?
Tradune shows what you actually hold across every account — concentration, correlation between your biggest positions, and how each one has done against a buy-and-hold SPY twin funded on your own dates.
Start freeFree for everyone right now · no card · nothing to buy
Sources
- GitLab Reports Second Quarter Fiscal Year 2027 Financial Results — Form 8-K, Exhibit 99.1 (SEC EDGAR, CIK 0001653482, filed 2026-09-01) — the company's own results release and the primary document for every company figure here
- GitLab Inc. — GitLab Reports First Quarter Fiscal Year 2027 Financial Results — Form 8-K, Exhibit 99.1 for the quarter ended April 30, 2026, filed June 2, 2026 (SEC EDGAR, accession 0001628280-26-039805) — source of the Q2 FY2027 guidance the results are compared against
- GitLab Inc. — Form 8-K filing index, filed 2026-09-01 (SEC EDGAR)
- GitLab Inc. — Form 10-Q for the quarter ended July 31, 2026 (SEC EDGAR, filed 2026-09-02)
- Zacks / TradingView — GitLab set to report Q2 earnings (Zacks consensus: revenue ~$273.3M, EPS ~$0.18)
- GitLab investor relations — quarterly results and shareholder letter
Other earnings analysis
Keep reading
This analysis summarizes results a company reported publicly, together with our own arithmetic on those reported figures. It is descriptive and educational — not a rating, a price target, a recommendation, or investment advice. Tradune is not a registered investment adviser.
Company financials are taken from the results release and related SEC filings; amended or final filings may revise them. Consensus estimates come from the named reports listed above and are not company-published data. Past results do not predict future returns.