GitLab GTLB Remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied
Remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied at other companies
Other financials
Where this comes from
Reported directly by GitLab in its filing.
Tagged under the XBRL concept us-gaap:RevenueRemainingPerformanceObligation.
The official record: GitLab’s 10-Q, filed June 2, 2026, on SEC EDGAR. View the filing →
Ask your AI about GitLab's remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied.
Connect your AI assistant and compare it to peers, right in your chat.
Connect your AI

Claude
Questions, answered.
- What is GitLab's remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied?
- GitLab (GTLB) reported remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied of $1.1B in Q1 2026.
- How has GitLab's remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied changed year-over-year?
- GitLab's remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied increased by 15.2% year-over-year, from $955.1M to $1.1B.
- What is the long-term trend for GitLab's remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied?
- Over 3 years (2021 to 2024), GitLab's remaining performance obligations related to customer contracts that are unsatisfied or partially unsatisfied has grown at a 61.5% compound annual growth rate (CAGR), from $159.9M to $673.8M.