Start by deciding who reads your content. If it's customers, choose a help centre built for public articles and search. If it's staff, choose an internal wiki that answers repeat questions. Then check how articles are written, organised and found, and who can edit them, because that decides whether the knowledge base stays current.
Papyrs describes itself as a modern take on the intranet, internal wiki and knowledge base, all in one site. That breadth suits some teams well. Support and product teams publishing help content often want something more focused: a public help centre for customers, or a tidy internal wiki for staff. The eight tools below, in no particular order, split along that line.
Who will read it: customers, staff or both
Public help centres for customers
Helpjuice, Document360 and ProProfs Knowledge Base are built for help content that customers search on their own, with AI search and chat now part of the pitch. HelpKit takes a lighter route, turning Notion pages into a hosted help centre, which suits small teams already writing everything in Notion.
Internal wikis for staff
Tettra and Slite focus on the questions colleagues ask over and over, with AI answers drawn from your own content. BookStack is the self-hosted, open source choice for organising internal information if you'd rather keep everything on your own server and control upgrades yourself.
Documentation for products and developers
Archbee brings user guides, API documentation, knowledge bases and standard operating procedures into one portal. It suits product teams that publish technical docs alongside everyday help articles and want one place for both.
Eight knowledge base tools, A to Z
Listed alphabetically and in no particular order. Each line reflects the vendor's own description.
Archbee
Best for: Product teams publishing user guides, API docs, knowledge bases and SOPs together in one portal that the vendor says is easy to search and contribute to.
BookStack
Best for: Anyone wanting a simple, open source wiki they host themselves for organising and storing information; the vendor names a free option.
Document360
Best for: Writers building documentation with AI search, an AI chatbot and writing tools built in, which the vendor frames as humans and AI working together.
Helpjuice
Best for: Support teams wanting a knowledge base that people go back to, aimed at streamlining support work; the vendor names a free trial.
HelpKit
Best for: Notion users who want those docs turned into a hosted help centre or documentation site without code, per the vendor.
ProProfs Knowledge Base
Best for: Businesses wanting a public or private AI knowledge base with integrations, which the vendor positions as a way to deflect support tickets.
Slite
Best for: Teams that want one source of truth connected to the apps where work happens, so staff and their AI tools work from reliable answers, says the vendor.
Tettra
Best for: Teams tired of answering the same internal questions, using an AI knowledge base to curate company information and give instant answers, per the vendor.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Writing, finding and editing: where these tools differ
A knowledge base lives or dies on habits, not features. If writing an article feels like a chore, people stop writing. If readers can't find what's there, they open a ticket or message a colleague instead. If anyone can edit anything, quality slips; if only one person can, the backlog grows. Test these four things with your own content:
- Writing: how the editor handles screenshots, steps and code, and whether drafts can be reviewed before they go live
- Organising: categories, tags and links between articles, and how easily you can restructure later
- Finding: how search copes with typos and plain-language questions, and what the AI answers draw on
- Editing rights: who can publish, who can suggest changes, and how out-of-date articles get flagged
AI search is now standard across most tools in this group. That's useful, but it can only answer from what's written, so the review and ownership side matters as much as ever. I've set the smarter options out separately in AI knowledge base software. Ask each vendor how their tool reminds owners to check articles that haven't been touched in a while.
At-a-glance comparison
| Tool | Main audience | Good for |
|---|---|---|
| Archbee | Documentation portal | Technical docs and help content in one place |
| BookStack | Self-hosted open source wiki | Keeping internal knowledge on your own server |
| Document360 | AI knowledge base | Customer documentation with AI search |
| Helpjuice | Support knowledge base | Support teams cutting repeat questions |
| HelpKit | Notion-based help centre | Publishing Notion pages as a help site |
| ProProfs Knowledge Base | Public or private knowledge base | Deflecting support tickets with self-service |
| Slite | Connected team wiki | A single source of truth for staff |
| Tettra | AI internal knowledge base | Answering repeat questions from colleagues |
Plain advice before you pick one
Pick the audience first and the tool second. A customer help centre and an internal wiki look alike in a demo, but they're judged on different things: customers want a quick answer from search, while colleagues want the right answer from a trusted owner. A tool that's great at one can feel clumsy at the other.
Then be honest about who'll write. If it's one support lead with an afternoon a week, choose the tool with the easiest editor, even if it does less. If it's a whole product team, choose the one with review steps and clear editing rights, so quality doesn't slip as more people contribute.
Moving your articles across
- List every article you have and mark which ones were opened recently; leave the rest behind or merge them.
- Agree your new categories before importing anything, so you're not reorganising twice.
- Import or copy the most read articles first and check images, links and formatting on each one.
- Give every article an owner and a review date in the new tool.
- Point old links and in-app help buttons to the new pages, then switch off the old site.
For more options, see my guide to knowledge base software and my list of help desk software for small businesses, which often bundle a help centre in.
Do you make knowledge base or help centre software? Tool makers can ask to be considered for a featured place on this list.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What's the difference between an intranet and a knowledge base?
An intranet is a home for internal news, people and pages. A knowledge base is a searchable library of answers, either for customers or for staff. Some tools do both; most specialise.
Should our help centre be public or private?
Public articles help customers help themselves and can be found in search engines. Keep internal processes, account rules and anything sensitive in a private space.
Can I write help articles in Notion and publish them?
Yes, some tools turn Notion pages into a hosted help centre, so your team keeps writing where it already works.
Does AI search replace well-written articles?
No. AI answers can only draw on what's written, so clear, current articles still decide the quality of every answer.
Is a self-hosted wiki a good idea?
It suits teams that want full control and have someone to run updates and backups. If nobody owns that job, a hosted tool is safer.