Help inside your product
The Lighthouse widget puts search, suggested articles, and a contact form in your app, so a stuck user never leaves to find the answer.
For SaaS teams
Opened “Import your data” inside the appLighthouse
Shared “Getting started” in live chatIntercom
Answered from “API authentication”ChatGPT
Resolved a chat from “Billing and invoices”Fin
A knowledge base for SaaS that answers before the ticket.
HelpDocs is knowledge base software built for product companies: help inside your app, AI answers drawn from your own articles, and a help center on your domain in every language you sell in.
Opened “Import your data” inside the appLighthouseShared “Getting started” in live chatIntercomAnswered from “API authentication”ChatGPTResolved a chat from “Billing and invoices”FinYour product changes every sprint. Your docs have to keep up.
A SaaS help center is not a one-off project. Every release adds a feature to explain and quietly makes a screenshot wrong, and the people paying for that gap are your support team and your trial users.
WHAT MATTERS FOR SAAS
Docs that reach people where they get stuck.
Inside the product, in the languages you sell in, and in the assistants your customers now ask first.
AI answers, with the sources
Ask AI answers the question in the reader's own words and lists the articles it drew on, so nobody has to trust it blindly.
Search that reads the article
Matches inside the body, not just the title, with the matching passage highlighted so people can see at a glance which result is theirs.
Ship in 20+ languages
Add a language and translate the help center as you expand, instead of running a separate knowledge base per market.
On your domain, in your brand
Publish at help.yourdomain.com or a subfolder, styled to match your product down to dark mode, so the SEO lands on your domain rather than a vendor's.
See what people actually read
Top articles by views, alongside the searches that returned nothing. Together they are the cheapest roadmap of what to write next.
AI visibility
See which AI assistants are citing you.
A growing share of your customers ask an assistant before they open your help center. See which AIs are visiting, which articles support them, and how many of those visits were real customer queries.
Explore analyticsWhat to cover
Written for where the customer actually is.
Most help centers are organized the way the product team thinks, not the way a customer arrives. This order tends to survive contact with real traffic.
Trial
Getting started, the first workflow that proves the product, and the three things people get wrong in week one.
Onboarding
Importing data, inviting a team, connecting the integrations that make it stick.
Everyday use
The workflows support answers most often, written so somebody can follow them without a call.
Admin and billing
Seats, invoices, plan changes, and cancellation. Dull, high-traffic, and usually the last thing written.
Troubleshooting
The errors your inbox sees weekly, by symptom rather than by cause, because that is how people search.
What shipped
Release notes with a consistent shape, so customers can tell whether an update affects them.
Keeping up
From shipped to documented, same week.
Docs rot because updating them is a separate job nobody owns. Tie it to the release and it stops being one.
- 1
Draft from the changelog
Paste what shipped and let AI turn it into a release note in your existing shape, then edit rather than write.
- 2
Fix what the change broke
Stale flags surface the articles that quietly stopped being true when a screen moved or a setting was renamed.
- 3
Let the searches set the backlog
Queries that returned nothing tell you which article the release still owes people, without anyone having to guess.
Plugs into the stack you already run
Browse all integrations
Free to steal
Templates and guides to start from.
The blank page is the hard part. Every template ships with an AI prompt you can open straight in Claude or ChatGPT.
Templates
FAQ
SaaS knowledge base questions
What should a SaaS knowledge base include?
At minimum: getting started, the three or four workflows most customers actually use, billing and account management, troubleshooting for the errors your support inbox sees weekly, and an integrations or API section if you have one. Our guide to creating your first SaaS knowledge base walks through the whole structure.
Should the help center be on our domain or a subdomain?
Either works, and HelpDocs supports both. A subfolder like yourdomain.com/help keeps the SEO value on your main domain, which matters if help articles are a meaningful acquisition channel. A subdomain like help.yourdomain.com is simpler to set up. What matters more than the choice is that it is your domain rather than a vendor URL.
How do we keep docs current when the product ships weekly?
Tie it to the release rather than to good intentions. A release notes template gives every ship the same shape, stale-content flags surface the articles a change quietly broke, and AI drafting turns the changelog into a first pass. Knowledge base maintenance covers the wider routine.
Can our customers' AI assistants read our documentation?
Yes. The HelpDocs MCP server lets Claude, ChatGPT, and any other MCP-compatible client search and read your articles directly, so answers come from documentation you maintain rather than whatever a crawler picked up months ago.
How long does it take to migrate an existing help center?
There are guided imports from Zendesk, Intercom, Help Scout, Helpjuice, ReadMe, ProProfs, and CSV, so most teams move their existing articles in a day rather than a quarter. Restructuring the content afterwards is usually the part that takes real time.
Give your customers a reason not to email you.
Start free 14-day trialStart a free trial, import your existing articles, and put help inside the product where people get stuck.
No credit card required.
