GTLB · Forward model · Subscription - self-managed and SaaS · Bull case
What has to happen in Subscription - self-managed and SaaS
Model as of
This page changes Subscription - self-managed and SaaS inside the complete GTLB model. Every other vertical, corporate programme and valuation assumption stays in the selected portfolio case.
Shares this vertical and portfolio case. Slider and horizon edits stay in your browser.
Subscription - self-managed and SaaS
Basis quarter$239M
Final quarter$527M
Implied CAGR+17%
Final revenue mix94%
90.6% of revenue and effectively the whole equity story. GitLab recognises this line ratably across self-managed subscriptions and its SaaS offering, and it publishes the two things a subscription driver needs: Base Customers, its own defined count of customers paying more than $5,000 of annual recurring revenue, and a dollar-based net retention rate that says what the existing base does to its spending. Both have decelerated for seven straight quarters - customer growth from 16% to 7%, retention from 124% to 117% - while revenue still grew 23%, because the base keeps trading up: $100,000-ARR customers grew 18% and $1 million-ARR customers 26%. So the driver has to carry almost all of its growth in revenue per customer rather than in customer count, and that is exactly what the fiscal 2027 guide implies.
Last four quarters
2026 Q2
$213M
Reported
2026 Q3
$223M
Reported
2026 Q4
$234M
Reported
2027 Q1
$239M
Reported
Self-managed subscriptions and SaaS subscriptions to the GitLab DevSecOps platform across the Premium and Ultimate tiers, including GitLab Duo and the Duo Agent Platform, plus professional services. GitLab discloses no revenue, annual recurring revenue or customer count for SaaS versus self-managed, for any tier, or for any AI or agentic product, so nothing inside this line may be sized separately.
Subscribers
11K
24.1% of a 45K addressable base
10,831 Base Customers at 30 April 2026 - GitLab's own defined metric for customers above $5,000 of ARR.
Addressable subscribers
45K
the S-curve ceiling
Assumed pool of organisations able to pay above $5,000 of ARR. Nothing is disclosed; it never binds inside the horizon.
Net adds
200/qtr
ramping toward 120/qtr, throttled as the base approaches the TAM
Last four adds ran 234/137/207/149. Against the saturation term this yields about 150 real adds a quarter.
Net-add ceiling
120/qtr
what supply can deliver at full rate
Adds fade as the base matures and 22 country exits thin coverage. Nothing disclosed sets a floor.
ARPU
$7,365.40/mo
drifting +1.8% per quarter, floor $0.00
$239.3m of subscription revenue over three months over 10,831 Base Customers. A monetisation index, not a contract value.
Non-subscriber revenue
$0/qtr
growing 0.0% per quarter
Zero: the licence line is its own vertical, so nothing sits outside the Base Customer calculation.
Subscription - self-managed and SaaS
Latest: $527M (2032Q1E)
| Period | Value |
|---|---|
| 2024Q3 | $131M |
| 2024Q4 | $142M |
| 2025Q1 | $151M |
| 2025Q2 | $163M |
| 2025Q3 | $175M |
| 2025Q4 | $186M |
| 2026Q1 | $194M |
| 2026Q2 | $213M |
| 2026Q3 | $223M |
| 2026Q4 | $234M |
| 2027Q1 | $239M |
| 2027Q2E | $250M |
| 2027Q3E | $261M |
| 2027Q4E | $272M |
| 2028Q1E | $284M |
| 2028Q2E | $295M |
| 2028Q3E | $308M |
| 2028Q4E | $320M |
| 2029Q1E | $333M |
| 2029Q2E | $347M |
| 2029Q3E | $361M |
| 2029Q4E | $375M |
| 2030Q1E | $390M |
| 2030Q2E | $405M |
| 2030Q3E | $421M |
| 2030Q4E | $437M |
| 2031Q1E | $454M |
| 2031Q2E | $471M |
| 2031Q3E | $489M |
| 2031Q4E | $508M |
| 2032Q1E | $527M |
Assumptions & reasoning
- Every quarter of this history is a filed number off the face of a condensed consolidated statement of operations, read from seven separate 8-K exhibits in which each quarter appears twice - once as the current quarter and once as the following year's comparative - and every overlap agrees to the dollar. Nothing here is estimated and nothing was apportioned.
- ARPU here is a monetisation index for the Base Customer cohort, not an average contract value. The line also carries revenue from customers below the $5,000 ARR threshold and from professional services, so this figure is higher than any customer actually pays. It is internally consistent because it is derived from, and reconciles back to, the same disclosed revenue line.
- The 40.6% EBITDA margin is a CALIBRATED CASH margin, not a reported operating margin, and reading it as one will mislead. GitLab's non-GAAP operating margin was 14% in the basis quarter and 17% for fiscal 2026. Adjusted free cash flow ran far above that - $219.6m on $955.2m of fiscal 2026 revenue, or 23.0% - because roughly $200m a year of stock compensation is non-cash. This engine has no concept for that, so the calibration lives in the margin: solving 23.0% = (E - 1.0% capex) x (1 - 22% tax) gives 30.5% consolidated, adding back the 10.0% corporate overhead line gives 40.5% at vertical level, and splitting that across the two lines by the disclosed gross-margin gap puts this one at 40.6%.
- The engine's ARPU drift is a single constant. Holding 1.80% a quarter for twenty quarters implies 7.4% a year of expansion forever, which a net retention rate that has fallen one point in each of the last seven quarters would not sustain indefinitely. This is the model's main extrapolation risk, and it is why the bear case moves growth rather than only the multiple.
- This vertical carries no seasonality. Factors fitted by ratio to a centred four-quarter moving average come out at 0.9877 / 1.0062 / 1.0069 / 0.9992 - a signal of 1.92 points against a worst window-to-window spread of 1.34 points, which is not separable from noise. There is a real mechanism pointing the same way, since GitLab's fiscal Q1 runs 1 February to 30 April and is 89 or 90 days against 92 for the other three, but that alone is worth under a point on a ratable line and is absorbed into the ARPU drift.