Public Beta · Now Accepting Design Partners

Your code + SDLC data, one property graph your agents love

Orbit, the GitLab Knowledge Graph, unifies code, merge requests, pipelines, projects, and people into a single queryable graph. Your AI agents traverse real relationships instead of grepping and guessing. Join a small group of design partners shaping it with us.

Apply to the Program Browse Resources

What Orbit Is

A knowledge graph of everything in your GitLab instance

Orbit builds a live, structured graph of your software development lifecycle: code definitions and references across files, projects, groups, merge requests, CI/CD pipelines, and more. AI agents query that graph instead of guessing from file snippets.

Works inside GitLab Duo

Orbit powers the Duo Agent Platform. Duo Developer Flow and the foundational agents pull answers from the graph when a question is best answered by traversing your SDLC data.

GitLab Duo Duo Developer Flow

Works with your agents

Connect external agents like Claude Code and Codex through the glab CLI, or secondarily over MCP. Any MCP/CLI compatible agent can query the graph and explore its schema.

Claude Code Codex Cursor Copilot Gemini CLI + any MCP/CLI agent

Deep language coverage

Full cross-file code intelligence for Ruby, Java, Kotlin, Python, TypeScript, JavaScript, Rust, Go, C#, C, and C++.

What You'll Test

Questions your team can finally ask

These are the six starter scenarios design partners run in their own environment. As a partner, you commit to validating at least three business use cases like these. Full playbook on the resources page.

Blast radius analysis

Understand impact before you change anything.

"Show me every caller of this function across all repos. Blast radius assessment."

Safe deprecation

Retire endpoints and services with confidence.

"I'm deprecating this endpoint. Find all internal callers."

System mapping

Accelerate onboarding into unfamiliar systems.

"Give me a high level map of this system: key files, dependencies, call chains."

CI pipeline health

See pipeline health across the whole org, not one project at a time.

"Which files correlate most with pipeline failures? Top 10 with the jobs they tend to break."

Codebase health

Engineering health data you can report to leadership.

"Codebase health snapshot: most churn, highest failure rate, fewest contributors."

Duplicate detection

Stop rebuilding what already exists.

"Before I write a new helper or service, do we have something similar?"

The Program

Six weeks, one sync per week, real outcomes

This is a structured program, not an open-ended trial. You pick three business use cases at application time, we validate them together across six weeks, and you finish with a written readout you can share internally.

Week 1

Kickoff + enablement

Enable Orbit on your top-level group. Indexing starts automatically. Your team connects through Duo and/or an external agent.

Week 2

First queries

Run the starter prompt pack in Duo and/or your external agents. Confirm the graph reflects your codebase.

Week 3

Use case 1

Deep validation of your first business use case with the product team in your weekly sync.

Week 4

Use case 2

Second use case, plus feedback on query accuracy, indexing completeness, and agent behavior.

Week 5

Use case 3

Third use case, plus a look at what's coming next on the roadmap and how it maps to your needs.

Week 6

Readout

Joint summary of what was proven, what wasn't, and what we're building next because of your feedback.

Expectations

What we commit to, and what we ask of you

Here is what each side commits to. The full version is in the expectations one-pager.

GitLab commits to

  • A weekly 30-minute working session with the product team for all six weeks
  • Hands-on enablement support: setup, starter prompts, and a test plan matched to your use cases
  • A direct line for bugs and questions, with responses within one business day
  • Roadmap input: your validated gaps become prioritized issues
  • Early access to new capabilities as they ship during the program

You commit to

  • Three business use cases, defined at application time, that you will validate
  • One 30-minute sync per week for six weeks, prescheduled when you apply
  • Enabling Orbit on at least one top-level group during week 1
  • First queries within 7 days of enablement
  • Honest, specific feedback: what worked, what didn't, and what's missing
  • Willingness to complete GitLab's Testing Agreement for beta feature use, including any legal review your organization requires

Who Should Apply

Is your organization a fit?

The program is open to GitLab.com (SaaS), Self-Managed, and Dedicated customers. On GitLab.com you can enable Orbit yourself in minutes. For Self-Managed and Dedicated partners, the program starts with deployment: getting Orbit running in your environment is the first phase, with our engineers working directly with your infrastructure team.

You need

GitLab.com, Self-Managed, or Dedicated Premium or Ultimate Top-level group Owner access Time for a weekly sync

Bring an MCP/CLI compatible agent such as Claude Code or Codex for testing external agent integration. Self-Managed partners should have an infrastructure team ready to partner with our engineers on deployment, including Kubernetes capacity.

Best signal comes from codebases in

Ruby Java Kotlin Python TypeScript JavaScript Rust Go C# C C++

Not yet indexed: Swift COBOL Terraform / YAML config

Ready?

Apply to become a design partner

The application takes about ten minutes. You'll pick your three use cases, choose your weekly sync slot, and tell us about your environment.

Start Your Application

Applications are reviewed on a rolling basis. Spots are limited to keep the feedback loop tight.