Loading…

Gitlab (GTLB) backlog: remaining performance obligations

How much revenue Gitlab already has under contract, how fast it converts, and who it is with.

Data as of .

Gitlab backlog history

$0$500M$1BOct 2022Apr 2023Oct 2023Apr 2024Oct 2024Apr 2025Oct 2025Apr 2026Jul 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
31 Jul 2026$1.20B$1.06B1.1 yrsn/a
30 Apr 2026$1.10B$1.00B1.1 yrs$533M
31 Jan 2026$1.14B$955M1.2 yrs$545M
31 Oct 2025$1.00B$906M1.1 yrs$465M
31 Jul 2025$988M$858M1.2 yrs$460M
30 Apr 2025$955M$805M1.2 yrs$451M
31 Jan 2025$945M$759M1.2 yrs$443M
31 Oct 2024$812M$712M1.1 yrs$383M
31 Jul 2024$748M$665M1.1 yrs$362M
30 Apr 2024$681M$622M1.1 yrs$342M
31 Jan 2024$674M$580M1.2 yrs$338M
31 Oct 2023$548M$539M1.0 yrs$288M

Questions

What is Gitlab's backlog?
Gitlab reported $1.20B of remaining performance obligations at 31 Jul 2026, up 21% from a year earlier and up 9% from the previous quarter. That is 1.1 years of trailing revenue already under contract. Book-to-bill last quarter: 1.35.
How fast does Gitlab's backlog turn into revenue?
Over the last twelve months Gitlab recognised revenue equal to about 100% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.