GitHub Copilot Enterprise launched in February 2024 at $39 per user per month, exactly double the Business tier at $19. The most-asked question in engineering forums since then: is the code graph what you're paying for, and does it actually work?
TL;DR
Copilot Enterprise builds a semantic code graph over your GitHub repos, giving completions and chat answers that span across files and repos rather than just what's open in your editor. It's the main technical differentiator from Business tier. It helps most on large codebases with many cross-module dependencies. For teams under 10 on a single repo, Business tier is usually sufficient.
What the Code Graph Actually Is
Copilot Business limits its context to the files open in your editor plus a rolling window. It doesn't know about utils/auth.ts unless you have it open. This is fine for simple edits but breaks down when you ask "how does our permission system work?" or when Copilot autocompletes a function call with the wrong signature because the real definition is in another file.
Copilot Enterprise solves this by indexing your repositories into a code graph: a structured semantic map of how your codebase is connected. It captures:
- Symbol relationships: which functions call which, which types implement which interfaces
- Cross-file dependencies: import graphs, re-export chains, type inheritance
- Cross-repo links: shared packages, internal libraries, monorepo package boundaries
- Semantic clusters: groups of files that co-change frequently or share domain concepts
When you type a completion or ask Copilot Chat a question, the code graph retrieves the most relevant nodes from this graph to expand the context window beyond what fits in a single file.
What This Changes in Practice
Completions With Cross-File Context
In Business tier, if your createOrder function is in services/orders.ts and you're editing handlers/checkout.ts, Copilot doesn't know createOrder's full signature unless that file is open. In Enterprise, the code graph has already indexed services/orders.ts, so Copilot can autocomplete the call correctly without you manually opening the file first.
Copilot Chat on Your Whole Repo
The clearest improvement is in Copilot Chat. With Business, asking "where do we validate email addresses?" returns generic guidance. With Enterprise and the code graph indexed, it returns the specific function name, file path, and a summary of what the current implementation does.
The code graph powers Copilot Chat's "Your Repository" mode in GitHub.com. You need to be in github.com (not your editor) for the cross-repo version. The editor extension uses a subset of the graph via Copilot Knowledge Bases.
Pull Request Summaries
Copilot Enterprise can write PR summaries that reference related changes in other PRs and flag API surface changes that might affect downstream repos. This uses the code graph to trace what your diff touches.
Where the Code Graph Underdelivers
Fresh private repos: The indexing job runs on a schedule. A repo you just created or one with recent large commits may have a stale index. You'll see Copilot Chat responding with outdated context or falling back to generic answers.
Very large monorepos: GitHub's indexing has practical limits. Monorepos above several million lines of code may only get partial indexing. You can check which files are included in your organization's Knowledge Base settings.
Proprietary naming conventions: The code graph is better at structural relationships than semantic intent. If your team uses terse internal names (prxHandler, cpol_v2_compat), the graph captures the call relationships but Copilot Chat may still give imprecise summaries about what those symbols mean.
Local-only work: The code graph lives on GitHub's servers. If your development workflow involves long-running local branches that haven't been pushed, Copilot doesn't know about those changes.
The code graph is a read path for Copilot, not a write path. It does not give Copilot any new ability to modify files, run code, or access secrets. The privacy concern is that your code structure and symbol names are indexed on GitHub's infrastructure. For SOC 2 or ISO 27001 workflows, review GitHub's Enterprise Cloud data retention policy before enabling.
Copilot Enterprise vs Business: Feature Comparison
| Feature | Business ($19/user/mo) | Enterprise ($39/user/mo) |
|---|---|---|
| Code completions | Open files only | Cross-repo via code graph |
| Copilot Chat | Editor context | Repo-wide + PR context |
| Knowledge Bases | No | Yes (up to 50 repos) |
| PR summaries | Basic | Code-graph-aware |
| Fine-tuned model | No | Optional (custom model) |
| GitHub.com integration | Partial | Full (Discussions, Issues) |
| Policy controls | Org-level | Org + enterprise-level |
| SAML SSO requirement | Optional | Required for Enterprise Cloud |
When Enterprise Is Worth the Premium
You get real value from the code graph when at least two of these are true:
- Your team has 15+ engineers all generating Copilot-suggested code
- Your codebase has more than one repo that depends on shared internal libraries
- You're spending meaningful time answering "where is X implemented?" questions
- You want Copilot Chat embedded in GitHub PRs and Discussions, not just the editor
If you're a solo founder or a small team with a single-repo app, Business tier at $19 gets you 90% of the completion benefit at half the cost. The code graph is the right call when you've outgrown "open the file first" as a workaround.
What is the GitHub Copilot Enterprise code graph?
The code graph is a semantic index GitHub Copilot Enterprise builds over your repositories. It maps how files, functions, types, and modules relate to each other so Copilot can suggest completions and answers that span multiple files and repos, not just what's open in your editor.
Does GitHub Copilot Business have a code graph?
No. Business tier context is limited to open files and a rolling window in your editor. Enterprise adds repo-level and cross-repo indexing via the code graph, which is the main technical reason the price doubles from $19 to $39 per user per month.
Is the code graph worth the cost for a small team?
Probably not. The code graph's value scales with codebase complexity and team size. For solo founders or teams under 10 with a single repo under 100k lines, Copilot Business delivers most of the completions value at half the cost.
How does Copilot Enterprise code graph differ from Cursor's codebase indexing?
Cursor's @codebase feature uses embeddings to do semantic search across your local repo. Copilot Enterprise's code graph is server-side on GitHub and covers multiple repos. Cursor tends to be faster and cheaper; Copilot Enterprise integrates directly into GitHub PRs and Discussions.
What repos get indexed by the code graph?
GitHub Enterprise Cloud admins configure which repos are indexed. Repos you explicitly add to a Knowledge Base (the UI surface for the code graph) are included. Private repos require explicit admin opt-in and are subject to the organization's data policy.
Check What AI Tools Your App Was Built With
Our scanner detects which AI coding tools generated your codebase and flags security patterns common to each.