← Back to home
Comparison · ai-assistants

Dosu vs Sourcegraph

A side-by-side editorial comparison of Dosu and Sourcegraph — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:coding-agents

Dosu vs Sourcegraph: at a glance

FeatureDosuSourcegraph
Sectorai-assistantsai-assistants
Velocity score7.55.0
Sparks · 30d10
Top themesagent-memory, oss-pricing, coding-agents, content-marketingcode-search, coding-agents, context-retrieval, code-migrations
Last editorial update1d ago4d ago
WebsiteVisit →Visit →

What is Dosu?

The OSS terms change takes effect today, under a steady drumbeat of agent-memory explainers.

Dosu's feed is currently doing two jobs. One is a sustained series on agent memory — representation and storage, the building blocks of a memory system, where knowledge should live — published as a webinar and then a blog write-up of the same material. The other is the announced change to its open source plan, which takes effect 1 September 2026 and which Dosu says leaves roughly 96% of projects unaffected. The actual product releases sit just outside this window, in the monthly Drop posts and the Decant launch that reads Claude Code and Codex session logs locally.

Read the full Dosu trajectory →

What is Sourcegraph?

Sourcegraph stopped selling search to developers and started selling retrieval to their agents.

The product line has reorganized around coding agents as the customer. Code Finder runs its own search loop and hands an agent exact files and line ranges; Deep Search now executes scripts in a sandbox against the search APIs so a migration audit returns a CSV checklist rather than thousands of files of tokens; Agentic Batch Changes entered public beta to scope and ship migrations across hundreds of repositories. The argument threaded through all of it is that an agent searching on its own is slower, costlier, and worse than one handed scoped results.

Read the full Sourcegraph trajectory →

Dosu vs Sourcegraph: editorial side-by-side

D
Dosu
AI-ASSISTANTS
7.5

The OSS terms change takes effect today, under a steady drumbeat of agent-memory explainers.

◆ Current state

Dosu's feed is currently doing two jobs. One is a sustained series on agent memory — representation and storage, the building blocks of a memory system, where knowledge should live — published as a webinar and then a blog write-up of the same material. The other is the announced change to its open source plan, which takes effect 1 September 2026 and which Dosu says leaves roughly 96% of projects unaffected. The actual product releases sit just outside this window, in the monthly Drop posts and the Decant launch that reads Claude Code and Codex session logs locally.

◆ Where it's heading

The content is doing positioning work around the pricing boundary rather than filling time. The argument running through it — that a coding agent's budget goes to context rather than code, that most teams should start with Git as the memory substrate, that old agent logs are worth converting into maintained knowledge — all points at the same claim, that the durable asset is stored knowledge and Dosu is where it should live. The OSS terms change tests whether that argument stands on its own once the largest repositories are no longer free distribution.

◆ Prediction

Expect the September Drop to show how the new OSS terms landed in practice, and the memory series to close on a Dosu-shaped answer to where knowledge lives.

S
Sourcegraph
AI-ASSISTANTS
5.0

Sourcegraph stopped selling search to developers and started selling retrieval to their agents.

◆ Current state

The product line has reorganized around coding agents as the customer. Code Finder runs its own search loop and hands an agent exact files and line ranges; Deep Search now executes scripts in a sandbox against the search APIs so a migration audit returns a CSV checklist rather than thousands of files of tokens; Agentic Batch Changes entered public beta to scope and ship migrations across hundreds of repositories. The argument threaded through all of it is that an agent searching on its own is slower, costlier, and worse than one handed scoped results.

◆ Where it's heading

Two consequences of that repositioning are already showing. First, Sourcegraph is pushing into other vendors' agents rather than waiting for its own surface — reranking Claude Code's file picker on symbols instead of path characters is integration work on someone else's tool. Second, scoped retrieval is being sold as governance: if you can prove which files an agent read before it shipped a change, agent context becomes an audit trail, which is the wedge into regulated engineering teams. The security posts extend the same logic from migrations to vulnerability remediation across ten thousand repositories.

◆ Prediction

Expect Agentic Batch Changes to move from public beta toward general availability, and more retrieval integrations into third-party coding agents. The provenance angle looks like the basis of an enterprise tier aimed at regulated buyers.

Alternatives to Dosu and Sourcegraph

Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Dosu or Sourcegraph.

See all Dosu alternatives → · See all Sourcegraph alternatives →

Recent activity from Dosu and Sourcegraph

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoDosuHow to Build Agent Memory: Where Does Knowledge Live?
  2. 5d agoSourcegraphA smarter way to run code migrations with less LLM context
  3. 6d agoDosuAgent Memory: Where Does Knowledge Live?
  4. 8d agoDosuYour coding agent budget pays for context, not code
  5. 9d agoDosuAgent Memory: What Are the Building Blocks of a Memory System?
  6. 10d agoDosuOSS has Changed. So has Dosu.
  7. 12d agoDosuHow to Build Agent Memory: The Building Blocks of Agent Memory
  8. 13d agoSourcegraphMake Claude Code's @ picker search symbols, not filenames
  9. 1mo agoSourcegraphHow to evaluate Sourcegraph on your own codebase
  10. 1mo agoSourcegraphCompliance-first AI: proving agent provenance for regulated engineering teams
  11. 1mo agoSourcegraphCode Finder: fast, efficient code search for coding agents
  12. 1mo agoSourcegraphThree places enterprise security breaks down at codebase scale (and why your current tools don't cover them)

Frequently asked questions

What is the difference between Dosu and Sourcegraph?

Both compete on the same themes — coding-agents — within ai-assistants. Dosu is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Dosu better than Sourcegraph?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dosu is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.

What are the best alternatives to Dosu?

Top Dosu alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Dosu alternatives" section above for the current picks, or visit /alternatives/dosu for the full list with editorial commentary on each.

What are the best alternatives to Sourcegraph?

Top Sourcegraph alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Sourcegraph alternatives" section above for the current picks, or visit /alternatives/sourcegraph for the full list with editorial commentary on each.