Why I built HelpNest

While building Babble, I hit a moment most product builders eventually face: I needed customer-facing help documentation.

I already had developer docs — but I quickly realised the audience is completely different. A developer is comfortable navigating a sidebar, scanning code snippets, and jumping between sections. A general customer isn't. They land on a page, want a quick answer, and leave if it isn't obvious. The bar for clarity is much higher.

So I did a quick scan of how other companies handle this. Every company I respected had a clean, searchable help center. The pattern was clear. What surprised me was the cost — many of these tools charge per seat, per page view, or lock key features behind expensive tiers. For an early-stage product that just needs a solid place to answer customer questions, the pricing felt out of proportion.

I searched for open source alternatives. There are several great developer documentation frameworks — Docusaurus, Mintlify, ReadMe — but they are built for developers, by developers. I could not find a single stable, well-maintained OSS tool focused on the general customer audience.

That gap is why HelpNest exists. A clean, self-hostable help center that your customers — not just your engineers — can actually use. MIT licensed, free forever, built for the world.