Kelu vs Cody (Sourcegraph)
Last reviewed:
Cody is Sourcegraph's AI coding assistant. It lives in your editor and pulls context from your codebase through Sourcegraph's code search. Since July 2025 it is sold only with Sourcegraph Enterprise. Kelu is a docs and support assistant that answers questions from your docs, wikis and tickets on your website, in Slack and Teams, over MCP and inside your helpdesk. Different jobs; many teams use both.
Choose Cody if your engineers need an AI coding assistant in the IDE that understands your whole codebase, and your company buys Sourcegraph Enterprise. Choose Kelu if you need cited answers from your docs, wikis and tickets for customers and staff, on your website, in Slack and Teams, over MCP and inside your helpdesk. Many teams run both.
Feature comparison
Information about Cody is drawn from Sourcegraph's own pricing page, docs and blog.
Where Kelu focuses differently
Different jobs, not competitors
Cody helps an engineer at your company navigate and write code inside the IDE. Kelu helps your customers (or your own employees) get cited answers from docs, wikis and tickets — on your website, in Slack, in the helpdesk. Both can coexist; many teams use each for what it does best.
Where Kelu reaches that Cody doesn't
A customer-facing widget on your docs, form deflection before a ticket is filed, Support Ticket AI inside your helpdesk, Slack and Teams bots, and an MCP endpoint so AI tools such as Cursor and Claude can ask your docs. Cody is an IDE tool by design; Kelu is the docs-and-support assistant layer.
Where Cody reaches that Kelu doesn't
Symbol-level code understanding, code completion, auto-edits and IDE-native context. If your main need is 'help engineers write code faster', Cody is built for it. Kelu can index source files through its GitHub Code source and quote them in answers, but it has no symbol graph, cross-references or completion — a different retrieval story.
How they complement
Cody knows your code; Kelu knows your docs. When an engineer asks 'how do I use our payment SDK?', Cody can inspect the SDK code; Kelu can retrieve the docs that explain the intended usage. Together they cover both sides of the developer experience.
Got questions?
Frequently asked questions
Do I need to choose between Cody and Kelu?
Usually not. They solve different jobs. Cody is an IDE coding assistant that reasons about your codebase; Kelu is a docs-and-support assistant that answers questions from your written knowledge across every surface. If your main need is 'help engineers write code', evaluate Cody; if it's 'help customers or non-engineer employees find answers', evaluate Kelu.
Is Cody still available?
Yes, for Sourcegraph Enterprise customers. Sourcegraph ended Cody Free and Cody Pro on July 23, 2025, removed Cody from its Enterprise Starter plan, and pointed individual users to Amp, its agentic coding tool.
Can Kelu answer code questions?
It can answer docs-shaped questions about your code — 'how do I use the pagination endpoint', 'what are the config options for X', 'what's the retry policy'. With the GitHub Code source it can also quote the implementation from the files you choose to index. It cannot follow symbol references, refactor or complete code the way Cody can. The right split is: docs questions to Kelu, code understanding to Cody.
Can Cody replace an in-IDE docs assistant?
Cody's context is your codebase. For docs-shaped questions grounded in your published documentation, Kelu's MCP server (usable from Cursor, Claude Desktop, ChatGPT with MCP and Windsurf) is the docs-side answer.
How does pricing compare?
Cody is sold only with Sourcegraph Enterprise, which starts at $16K a year on a minimum annual contract and includes credits for AI features. Kelu has a free plan, Pro at $99 a month ($79 billed yearly) with 10 team members included, and custom Enterprise pricing. Different unit: Sourcegraph sells a platform for your engineering org; Kelu sells the assistant behind your widget, bots and helpdesk.
Do you index code the way Sourcegraph does?
Not the same way. Kelu's GitHub Code source indexes the files you pick (by language, folder and pattern) and splits code at top-level declarations, so answers can quote and cite the implementation. It does not build a symbol index, references or code navigation — that is Sourcegraph's specialty; docs-and-support answers are ours.
See for yourself
Connect your docs and get your first AI-powered answer in under 5 minutes. No credit card required.
Free to start · No credit card required · Talk to Sales →