Half the documentation sites I visit now shove a little “Ask AI” chat bubble in the corner. I’ve leaned on them so much that some days I don’t even scroll past the first page, I just ask the bot what I need and move on. A Reddit user named u/MedyGames had the exact same habit, then kept hitting a wall: plenty of docs sites still don’t have one.
So this developer built LedgeIndex, an open source alternative to kapa.ai that lets you crawl and ingest any documentation, then ask it questions directly instead of hunting through pages for the answer yourself.
What’s new here is the flexibility. You’re not locked into someone else’s hosted widget the way you are with most of these “Ask AI” tools bolted onto docs sites. LedgeIndex runs on your local machine, on your own server, or on the LedgeIndex cloud, whichever fits your setup. In its current early MVP form, it already covers three things: a support chat widget you can drop straight onto your own site, custom support, builder, or planner agents you can run fully local or self-hosted through an SDK, CLI, or MCP, and a desktop app for asking questions to any doc you point it at.
Here’s the twist. Most RAG tools bluff. Ask them something outside what they actually ingested and they’ll confidently invent an answer rather than admit they came up empty. That’s the failure mode that quietly kills trust in these widgets over time. The creator specifically tuned LedgeIndex’s retrieval so it says “I don’t know” when the answer genuinely isn’t in the docs, instead of stitching together a plausible-sounding guess. That’s the actual hard problem in RAG. Not fetching the right chunk, it’s knowing when you didn’t fetch the right chunk and staying quiet instead of bluffing.
One commenter on the original thread backed this up hard. They said the onboarding on LedgeIndex was some of the best they’d ever had, and that they’d originally wanted to use kapa.ai but found the project too complicated to even join. Building on this open source alternative instead solved that problem in one step, and they now run their own version instead of waiting on someone else’s roadmap.
If you want to try this on your own docs, here’s the rough workflow:
- 🔧 Install the LedgeIndex CLI or SDK on your machine.
- 📄 Point it at your documentation source, a folder, a URL, or a repo.
- 🕷️ Let it crawl and ingest the docs into its local index.
- 🖥️ Query it through the desktop app, or wire it straight into an agent via MCP.
Once that’s working, adding the website widget for public-facing support chat runs off the same index, just a different front end. No need to rebuild the ingestion pipeline twice.
Pro tip: if you’re already running agents for support, planning, or internal tooling, treat LedgeIndex as the knowledge layer underneath them instead of a bolt-on chatbot. Since it’s exposed through SDK, CLI, and MCP, you can wire the same ingested docs into a Claude-based agent workflow instead of hand-rolling a separate retrieval pipeline for every project.
Second pro tip: test the “I don’t know” behavior on day one, before you trust it with anything real. Ask it something you know isn’t covered anywhere in your docs. If it hallucinates an answer instead of admitting the gap, your ingestion or chunking setup needs tuning first!
Third pro tip: because it’s fully open source, don’t just take the “honest RAG” claim on faith. Read how the retrieval and confidence scoring actually work in the repo. That’s the whole point of picking an open alternative over a closed hosted widget, you get to verify it instead of trusting a black box.
Worth flagging honestly: this is a very early MVP, so expect rough edges and missing polish compared to a mature product like kapa.ai. Support for every doc format, edge cases in crawling messy sites, and UI polish will all need time. But the core bet here, an assistant that admits ignorance instead of guessing, is exactly the kind of thing that matters once people start trusting these widgets more than the actual docs underneath them.
If your project’s docs still don’t have an “Ask AI” button, or the one you’re paying for keeps confidently making things up, this is worth a weekend of your time. Check out the repo, star it if it earns it, and self-host it on your own docs to see exactly where it breaks. 🚀
Frequently Asked Questions
Q: Can I run LedgeIndex on my own servers?
Yes. You have three options: local machine, self-hosted, or cloud. The open-source approach means you maintain full control over your documentation data without sending it to a third-party service.
Q: How does LedgeIndex compare to kapa.ai?
LedgeIndex is open-source with a much simpler onboarding process. You get a desktop app, CLI, SDK, and web widget, plus the flexibility to run everything privately on your infrastructure if needed.
Q: What happens when LedgeIndex doesn’t have an answer?
It tells you honestly. The RAG system is designed to say “I don’t know” instead of guessing or hallucinating. This keeps responses grounded in your actual documentation rather than confabulating answers.
Q: Can I build custom agents beyond the chat widget?
Yes. You can create Support, Builder, or Planner agents using the SDK, CLI, or MCP protocol and deploy them locally or self-hosted. This gives you programmatic control for more advanced automation use cases.
I created a kapa.ai alternative for getting honest answers from technichal documentation
by u/MedyGames in PromptEngineering