Skip to main content
GitLab10-Q: Recurring revenue shift

GitLab experiences customer adoption of usage-based consumption and flexible billing models

Source: Autobound Signal API · 93 signals tracked for GitLab · updated

Get GitLab's live signals in Claude or ChatGPT, or by API

AskWhat changed at GitLab this week? Use Autobound signals for gitlab.com.

What happened

GitLab is actively implementing usage or consumption billing models alongside its subscription models, leading to operational and revenue forecasting changes.

Source

SEC EDGARSep 1, 2026

Quarterly report (Form 10-Q)

GitLab 10-Q for Quarter ended Jul 31, 2026

Filing excerpt

We also expect our operating and other expenses to increase in the foreseeable future as we continue to invest in our future growth, including implementing usage billing, expanding our research and development function to drive further development of The DevSecOps platform (including related to AI capabilities), expanding our sales and marketing activities, developing the functionality to expand into adjacent markets, and reaching customers in new geographic locations, which will negatively affect our operating results if our total revenue does not increase.

sec.gov/Archives/edgar/data/1653482/000162828026059943/gtlb-20260731.htmRead the full source

Other signals in this filing (4)

Extracted by Autobound

From the Signal API record
Signal
10-Q: Recurring revenue shift

What this signalsFilings often name leadership changes, deals and spending plans.

Period
Quarter ended Jul 31, 2026
Fiscal year end
07/31
Filed
Sep 1, 2026

More 10-Q signals at other companies

The full record

From the Signal API record

Details

CIK
1653482
Accession number
0001628280-26-059943
Timeframe
Multi year
Quarter
Q2
Filing year
2026
Fiscal year
2027
Period end date
Jul 31, 2026
Why it matters
Billing/subscription tools

Topics and mentions

Technologies

  • AI

Extraction

Confidence
High
Relevance
75%
Sentiment
Neutral
Detected
Nov 9, 2026
signal_type
sec-10q
signal_subtype
recurringRevenueShift

Use this data

Get every 10-Q signal for GitLab and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at GitLab this week?”

  2. Send it to your own tools

    The Signal API returns 10-Q signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full sec-10q record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/814c2916-1ec3-4cd7-acae-1876a6f2c41d returns this record as JSON. POST /v1/companies/enrich returns every signal for gitlab.com.

{
  "signal_id": "814c2916-1ec3-4cd7-acae-1876a6f2c41d",
  "signal_type": "sec-10q",
  "signal_subtype": "recurringRevenueShift",
  "detected_at": "2026-11-09T06:34:41.451+00:00",
  "company": {
    "name": "GitLab",
    "domain": "gitlab.com"
  },
  "data": {
    "detail": "GitLab is actively implementing usage or consumption billing models alongside its subscription models, leading to operational and revenue forecasting changes. Sales teams offering billing infrastructure or usage analytics can target teams managing this transition.",
    "metrics": {
      "timeframe": "multi_year"
    },
    "quarter": "Q2",
    "summary": "GitLab experiences customer adoption of usage-based consumption and flexible billing models",
    "excerpts": "We also expect our operating and other expenses to increase in the foreseeable future as we continue to invest in our future growth, including implementing usage billing, expanding our research and development function to drive further development of The DevSecOps platform (including related to AI capabilities), expanding our sales and marketing activities, developing the functionality to expand into adjacent markets, and reaching customers in new geographic locations, which will negatively affect our operating results if our total revenue does not increase.",
    "relevance": 0.75,
    "sentiment": "neutral",
    "confidence": "high",
    "source_url": "https://www.sec.gov/Archives/edgar/data/1653482/000162828026059943/gtlb-20260731.htm",
    "filing_date": "2026-09-01",
    "filing_year": 2026,
    "fiscal_year": 2027,
    "fiscal_year_end": "07/31",
    "period_end_date": "2026-07-31",
    "sales_relevance": "Billing/subscription tools",
    "signal_category": "revenue",
    "technologies_mentioned": [
      "AI"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.