Knowledge base vs help center vs documentation: what's the difference?

If you are setting up self-service support for a SaaS product, you will run into three overlapping terms: knowledge base, help center, and documentation. Vendors use them loosely, which makes it hard to know what you actually need. The short answer: a knowledge base is the organized collection of knowledge itself, a help center is the customer-facing website where that knowledge is published, and documentation is the subset of content that explains how a product works in detail.

A knowledge base (also written as knowledgebase) is a structured, searchable repository of information about your product or company. It typically contains how-to guides, FAQs, troubleshooting steps, billing explanations, and onboarding content, organized into categories so people can browse or search for answers.

Knowledge bases come in two flavors. An external knowledge base is public and serves your customers. An internal knowledge base is private and serves your team — think runbooks, policies, and process docs. Most SaaS companies need the external kind first, because it directly reduces inbound support volume.

A help center is the website where your external knowledge base lives. It is what customers actually visit — usually at a URL like help.yourproduct.com or docs.yourproduct.com. A good help center has search, clear category navigation, and fast pages that rank in Google so customers land on answers directly from a search query.

In practice, 'knowledge base' and 'help center' describe two sides of the same thing: the content and the site that publishes it. Knowledge base software like LightDocs handles both — you write and organize articles, and it publishes them as a branded, searchable help center on your own domain.

Documentation is the deep-reference layer: API references, configuration guides, technical specifications, and exhaustive feature explanations. Documentation tends to be written for users who already know what they are looking for, while knowledge base articles are written for users with a problem to solve ('How do I reset my password?').

Many teams publish documentation inside their help center as its own category. That works well early on — one site, one search index, one domain. Splitting docs into a separate developer portal usually only makes sense once you have a large API surface.

For most SaaS products, the answer is an external knowledge base published as a help center. It answers the repetitive questions that otherwise become support tickets — getting started, billing, account access, and common troubleshooting. Start with a handful of articles that address your most frequent tickets, publish them where Google can find them, and grow from there.

LightDocs is built exactly for this: write articles in a simple editor, organize them into categories, and publish a fast, SEO-ready help center on your own domain. It is free while in beta, and your customers never need an account to read it.