GitLab charges rival AI agents $0.03 a query for context they cannot get elsewhere
The company's context graph went generally available on October 29 with consumption pricing, and most of its traffic comes from rival agents paying per query; the governance controls it shipped the same week are what keep the platform sellable.
Richard Tang · 3 min read
GitLab+1.04% — GitLab, up 1.04 percent as of its last quote went generally available with Orbit on October 29, a live graph of a team's code, merge requests, pipelines and vulnerabilities that AI coding agents query before they write anything 2. The bet is unusual: rather than build the winning agent, GitLab charges every agent for the context it works from. And the agents paying the most are not its own.
Usage is real but small. GitLab says more than 3,500 organizations have used Orbit and coding agents have run over 280,000 queries through it, all vendor-reported 13. Orbit is sold by consumption, not by seat: a query pack costs $30 per user per month for 1,000 queries into a shared pool, with use beyond it billed at about $0.03 a query 2.
At that overage rate, 280,000 queries is roughly $8,400 of metered usage, a rounding error inside a company with about $9 billion in market value growing revenue about 23% a year 2. The revenue is not the story yet; the mix is. The chief executive said on the July earnings call that roughly 80% of Orbit's query volume comes from customers wiring it to outside agents, chiefly Claude Code from Anthropic$350B — Anthropic, private, latest valuation $350B and Codex from OpenAI$1.18T — OpenAI, private, latest valuation $1.18T 2. The agents GitLab does not own are the heaviest users of the product it gets paid for by the query.
The controls are what make agent-heavy platforms usable
The same November 5 announcement shipped the governance layer: Secrets Manager generally available on GitLab.com, a Dependency Firewall in early access, Impact Analytics for AI spend by team and task, and spending caps at subscription, group and user level 1.
This is the right link to build. Elastic's threat report out the same day found attackers driving Claude Code through its VS Code extension and tunnelling into a self-hosted GitLab instance, with stolen logins used an average of eight minutes after infection 5. Truffle Security opened a program on November 4 to revoke 1.4 million live exposed credentials, and reported that of 21,981 live keys it disclosed on GitLab and Bitbucket in 2025, 81% still worked six months later 4. An agent-contested platform without revocation, spend caps and audit records is not sellable to a security team.
The efficiency claims are the vendor's, and the test is December
GitLab's figures that Orbit cuts hallucinations up to 45 times and token use up to 4.5 times are its own testing, with no independent benchmark published 32. They are directionally plausible, since an agent starting from a current map should retry less, but price them as marketing until reproduced.
The market's real objection is durability: if token costs keep falling and context windows widen, agents may load the code themselves and the graph's value shrinks 2. December's earnings, the first print covering Orbit's general availability, will show whether external-agent query volume compounds once promotional terms end. That number, not the launch, is what to watch.
Agent use on GitLab is growing fastest of all
Agentic development is growing faster than the surrounding platform
Data
| YoY growth | |
|---|---|
| Agentic users | 200% |
| Secure repos | 100% |
| User namespaces | 80% |
| CI/CD pipelines | 40% |
Get Platforms by email, free
The cloud, data and developer software AI is built on. In our daily email, every weekday.
