
GitLab launches Orbit add-on, a context graph sold as query packs
By Rob Litterst, Co-founder, PricingSaaS
Published
GitLab’s pricing page · Change detected
What changed
GitLab added a new "GitLab Orbit" card to its pricing page, described as a context graph for the software lifecycle, sold in query packs sized to the organization that form one shared pool for humans and agents. It is available now for Premium and Ultimate on GitLab.com, with Self-Managed and Dedicated to follow in early November 2026. The new card now leads the "What credits unlock" panel, with GitLab Duo Agent Platform and Secrets Manager both pushed further down the page.
Why it matters
Orbit tests whether GitLab's credit-based billing, built for usage-based AI features, extends cleanly to a context-graph product sold in query packs rather than per seat. Watch whether the Self-Managed and Dedicated launch in early November reveals concrete query-pack pricing, and whether more of GitLab's add-ons migrate into the credits system instead of carrying their own flat price.
In context
GitLab has logged 25 tracked pricing events since Apr 11, 2025, and nearly all of them have reshaped what it already sells — feature changes account for 9 of them, more than any other type. Orbit breaks that pattern: it is GitLab's first tracked new-add-on launch, arriving 14 days after Secrets Manager reached Self-Managed, with Dedicated still pending, and it rides the same credits system GitLab built out with Flex Commitment's unified seat-and-credit billing in June and September's rename of per-use credits to on-demand. Across the index, new add-ons made up 125 of the 2,350 pricing changes tracked in the last 180 days across 108 companies — a pattern GitLab is only now joining.
What people are saying
“Fewer retries is the metric that matters, since every failed attempt burns tokens and reviewer attention. The catch is keeping that SDLC context fresh; stale context makes an agent confidently wrong.”
View original“Asking a map instead of crawling files sounds way easier on tokens. Curious how fresh it stays when the repo changes a lot.”
View original