On this page
- Decision table
- repowise vs Sourcegraph at a glance
- What Sourcegraph does well
- What repowise adds
- Docs for every file, symbol and subsystem
- Git ownership, hotspots and co-change
- Code health, dead code and decisions
- Ten MCP tools built for change safety
- Open source and self-hosting
- One question, two tools
- Which one to pick
- Try it on your repo
- FAQ
Pick Sourcegraph to search and change code across thousands of repositories; pick repowise to understand a codebase, see where changing it is risky, and give coding agents that context. Sourcegraph is a commercial code search platform with regex and structural search, SCIP-based code navigation and Batch Changes. repowise is an open-source index that builds docs, a dependency graph, git ownership, hotspots, code health and decisions, and serves them through ten MCP tools.
Sourcegraph details are as of 15 November 2026, from Sourcegraph's pricing page, code search docs and MCP docs. repowise details are from release 0.56.
Sourcegraph cluster, updated 15 November 2026: Sourcegraph alternatives (nine options, priced), repowise vs Sourcegraph (decision table), best code search tools for teams (six tools, one table) and the short Sourcegraph alternative page.
Decision table
| Your situation | Use |
|---|---|
| Hundreds of repositories on several code hosts, one search box | Sourcegraph |
| One migration across many repos, tracked to merge | Sourcegraph (Batch Changes) |
| Budget under $16K a year | repowise, or Zoekt for literal search |
| Must run on your own hardware, source available | repowise (AGPL-3.0) |
| Agents need to know what a file does, who owns it and what breaks | repowise |
| Reviewing a diff for risk before merge | repowise (get_change_risk) |
| Exact regex across every branch and commit | Sourcegraph |
| Onboarding an engineer to an unfamiliar service | repowise |
Scroll the table sideways to see every column.
repowise vs Sourcegraph at a glance
Sourcegraph answers "where is this?"; repowise answers "what is this, who owns it and is it safe to change?".
| Sourcegraph | repowise | |
|---|---|---|
| What it is | Code search and navigation platform | Codebase intelligence engine |
| Licence | Proprietary | AGPL-3.0 |
| Pricing | One Enterprise plan from $16K a year (minimum annual contract), per the pricing page | Free to self-host; hosted Free covers two public repositories, private repositories on Pro |
| Deployment | Single-tenant cloud or self-hosted | pip install repowise on your machine or CI; also hosted at repowise.dev |
| Search | Regex, boolean, structural and symbol search; natural-language query assist | Semantic and keyword search over the wiki, symbols and paths (search_codebase) |
| Scale | Many repositories across many code hosts | One repository or a workspace of related repositories |
| Batch refactors | Batch Changes opens pull requests across repositories | Not a goal; agents and developers make the edits |
| Documentation | None generated | A wiki page per file, symbol, subsystem and API surface |
| Git history | Commit and diff search | Ownership, bus factor, hotspots, co-change, bug-fix history |
| Code health, dead code | Not part of the product | Per-file health scores, a Fix first queue, dead code by confidence tier |
| Change risk | Not part of the product | get_change_risk scores a commit or diff range |
| Agent access | MCP server on Enterprise | Ten MCP tools on a local index |
| Languages | Any language, as text | 28 parsed to a full AST, 15 at the Full tier |
Scroll the table sideways to see every column.
What Sourcegraph does well
Sourcegraph is the reference product for finding code across a large estate. Its code search covers regular expressions, boolean operators, structural search, symbol, commit and diff search, across branches and commits and across code hosts.
Code navigation. SCIP indexes give precise go-to-definition and find-references in the browser, across repositories, with the precision of a local IDE.
Batch Changes. A platform team can find a pattern and open pull requests that change it across hundreds of repositories, then track them to merge. For a library migration or a security fix across many services, nothing in this comparison replaces it.
An MCP server for agents. On Enterprise plans, the Sourcegraph MCP server exposes keyword_search, nls_search, go_to_definition, find_references, commit_search, diff_search, read_file and a deepsearch agent, with administrator controls over which tools are enabled. Agents get precise search over everything the instance indexes.
What repowise adds
repowise indexes a repository once into a code graph and its git history, then reads that index as docs, a health report, an ownership map and agent tools. The graph, git, health and dead-code layers make no model calls.
Docs for every file, symbol and subsystem
repowise renders a wiki from the code's structure: a page per source file, selected public symbol, subsystem, dependency cycle, infrastructure file and API surface. repowise init --no-prose builds it with no API key; a provider key (Anthropic, OpenAI, Gemini, OpenRouter, LiteLLM or local Ollama) adds model-written prose to subsystem and overview pages. Each page carries a freshness status of fresh, stale, expired or unknown, and repowise update re-renders only what your commits touched. See the wiki feature page.

Git ownership, hotspots and co-change
From git log and git blame, with no model and no network, repowise records who owns each file and module, the bus factor behind it, which files are hotspots (complex and often changed) and which files change together with no import between them. Sourcegraph can search commits; it does not compute a risk model from them. The FastAPI ownership map shows the result on a live public index, and git intelligence explains the signals.

Code health, dead code and decisions
Every file is scored from 1 to 10 for defect risk, maintainability and performance by deterministic detectors, and a Fix first queue ranks what to change and which tests to run. Scored before the bug window, the defect score predicts which files get bug-fixed over the next six months with a ROC AUC of 0.74 across 21 repositories, per our published benchmarks. Dead code is reported by confidence tier from the dependency graph, and the decisions layer ties ADRs, # WHY: comments and PR history to the code they govern. The FastAPI code health page shows all of it.

Ten MCP tools built for change safety
repowise serves the index over MCP as ten tools: get_answer, get_context, get_symbol, search_codebase, get_risk, get_change_risk, get_why, get_overview, get_health and get_dead_code. Sourcegraph's MCP server (16 tools on the full endpoint, Enterprise only) returns search hits and navigation; these return callers with confidence, ownership, risk, health findings and the decision behind a file. get_change_risk scores the defect risk of a commit or diff range from the shape of the change, before merge. repowise init registers the server with Claude Code, and repowise mcp starts it for any other MCP host. See repowise for AI agents.
Open source and self-hosting
repowise is AGPL-3.0 and runs on your own machine or CI; Sourcegraph is proprietary and self-hosting is part of its Enterprise plan. As of 15 November 2026 Sourcegraph's public repository is archived (30 September 2024) after its move to a private monorepo, and its pricing page lists self-hosted among Enterprise deployment options. The open piece that remains is Zoekt, the Apache 2.0 trigram engine inside Sourcegraph search, which covers literal search but not docs, ownership or risk.
For people searching for a Sourcegraph open source alternative, the split is by job. Zoekt replaces exact search. repowise replaces the understanding half: pip install repowise, repowise init, and the index sits in .repowise/ beside the repository. With --no-prose or a local Ollama model nothing leaves your network, and there are no seat limits.
One question, two tools
Take "what breaks if I change the retry logic in the payments service?". In Sourcegraph you search for the function, follow find-references across repositories, then read commit history by hand. In repowise one get_answer or get_context call returns the callers with confidence, the file's owners, its health findings and the decisions that govern it, and get_change_risk scores the resulting diff. Sourcegraph gives you every occurrence; repowise gives you the judgment about them.
Which one to pick
Pick Sourcegraph if:
- You search and refactor across hundreds or thousands of repositories and code hosts.
- You need structural search, SCIP navigation or Batch Changes at that scale.
- Your agents need precise search across an enterprise estate through its Enterprise MCP server.
Pick repowise if:
- You want docs, ownership, hotspots, code health and dead code without running a cluster.
- Your agents should check context and change risk before editing, on private code, locally.
- You need an open-source tool with no seat limits that runs offline with Ollama.
Use both if you run a large estate. Use Sourcegraph to find every occurrence of a deprecated API and drive the migration, and repowise to onboard engineers to a service, rank where the debt sits and hand agents a structured map. Both are MCP servers, so one agent can query each.
Try it on your repo
Index a repository you already search in Sourcegraph and compare what each tells you:
pip install repowise
repowise init --no-prose # graph, git history, wiki, MCP registration; no API key
repowise serve # browse docs and dashboards at localhost:3000
repowise mcp # serve the ten MCP tools to Cursor or any MCP host
Or paste a public GitHub URL on the repowise homepage and read the result with no account. See live examples, the Sourcegraph alternative page, nine Sourcegraph alternatives, priced and the best code search tools for teams.
FAQ
- Is repowise a replacement for Sourcegraph?
- For understanding a codebase, yes: docs, ownership, health and agent tooling come from one local index. It is not a replacement for cross-repository search or Batch Changes across a large estate, where Sourcegraph is the specialist.
- How much does Sourcegraph cost?
- As of 15 November 2026, Sourcegraph's pricing page lists one Enterprise plan from $16K a year with a minimum annual contract, deployed as single-tenant cloud or self-hosted. Cody Free and Pro ended on 23 July 2025. repowise is free to self-host under AGPL-3.0; its hosted Free plan covers two public repositories and private repositories are on Pro.
- Does Sourcegraph have an MCP server?
- Yes, on Enterprise plans. It exposes search, go-to-definition, find-references, commit and diff search and a Deep Search agent. repowise has its own server with ten tools covering docs, risk, health, decisions and dead code.
- Can I self-host repowise?
- Yes.
pip install repowiseandrepowise initwrite the index to.repowise/beside the repository. With a local Ollama model, or--no-prose, nothing leaves your network. - What languages does repowise support?
- 28 languages are parsed to a full AST, and 15 are at the Full tier, per the language support doc.

