Knowledge base software
Knowledge base software splits by who reads it: Document360 and GitBook for documentation teams, Helpjuice for a standalone public help center, Notion for an internal wiki, Zendesk Guide and Help Scout Docs if you already own the desk, and AcornReply if you want a help center that arrives with the support inbox instead of as a second subscription.
The phrase covers two products that are not much alike. One is a documentation platform, built for people whose job is writing docs: versioning, review workflows, translated content, API references. The other is a customer help center, a set of public answers attached to wherever your support email lands. Buying the first when you needed the second is the expensive mistake in this category, and the pricing pages do nothing to warn you.
The list below is ordered by who the knowledge base is genuinely for. AcornReply sits in one narrow spot on it: a small team that wants a public help center without buying a second product to hold it.
What is knowledge base software?
Knowledge base software is where you write, organize and publish help content so a customer or a colleague can find an answer without asking a person. A customer-facing one gives you an editor, categories, a search box, a public site you can point your own domain at, and structured data so the pages can be indexed and quoted. An internal one trades the public site for permissions and wiki-style linking. Past that, the products separate on three questions worth asking early: who is going to write the content, what happens to an article as it ages, and whether the tool that answers your customers can read the same store. The last one is why a knowledge base bought on its own often underdelivers. It holds good answers your support tool cannot see.
Knowledge base tools, and who each one is for
Start with the audience rather than the feature list. A documentation platform and a support help center look similar in a comparison table and feel nothing alike to run.
| Tool | Best for | Pricing model |
|---|---|---|
Document360 Purpose-built for documentation at scale: versioning, review workflows, translations, API reference hosting. More process than a two-person support team will ever use. | Documentation teams running a large, versioned knowledge base | Tiered, by project and team size |
Helpjuice A focused knowledge base product with deep theming and hands-on setup help. It is only a knowledge base, so your inbox stays wherever it is today. | Teams that want a heavily customized public help center and nothing else | Tiered by number of users |
GitBook Git-backed, with branching, review and versioned publishing. Excellent when engineers write the docs, awkward when a support agent does. | Product and engineering docs that live beside the code | Per user, tiered, with a free tier |
Notion The easiest place to start writing and the right answer for internal knowledge. A published Notion site is a set of pages, not a help center wired into your support tool. | Internal wikis and team knowledge, published to the web if you want | Per user, tiered, with a free tier |
Zendesk Guide A mature multi-language help center with permissions and its own AI reading from it. Sensible if you are already there, not a reason to move there. | Teams already running Zendesk | Included with the Zendesk Suite tiers |
Help Scout Docs A fast, clean public docs site the shared inbox can search and link from. You are buying the inbox, and Docs comes with it. | Small and mid-size support teams already inside Help Scout | Included with Help Scout plans, which are per seat |
AcornReply The help center is on every plan, free included, and the AI drafts replies from the same entries. Not a documentation platform: no versioning, no translation workflow. | A small support team that wants a public help center without a second product | Flat per organization, with a free tier |
When you should buy a documentation platform instead
If writing documentation is somebody's job title, buy a tool built for that job. Document360 and GitBook have what we deliberately do not: article versioning, a draft-review-approve workflow, translated content, and structure that holds up across hundreds of pages with an API reference in the middle of them. Notion is the better answer for an internal wiki, and if you never needed the support side at all, a published Notion site will do. We are not a documentation platform and are not trying to become one. Two more limits to weigh before you shortlist us: Crisp is the only help center we import from directly, so arriving from Zendesk, Intercom or Help Scout means an export file or the API, and a custom domain is a paid-plan feature, with the free help center served from your workspace subdomain on acornreply.com.
Frequently asked questions
Is a knowledge base included or a paid add-on?
In AcornReply it is included on every plan, starting with the $0 one, and there is no per-seat charge at any tier, so adding a teammate does not change what you pay. The free plan publishes up to 100 entries per workspace and 200 across the whole organization. What you pay for is the address: the free help center is served from your workspace subdomain on acornreply.com, and serving it from help.yourcompany.com needs a paid plan. Elsewhere it varies. Zendesk Guide and Help Scout Docs come with their desks, while Document360, Helpjuice and GitBook are the product you are buying, so the knowledge base is the whole bill rather than a line on it.
Does my knowledge base feed the AI that writes replies?
In AcornReply, yes, because there is one store and not two. When a customer email arrives, the draft is written from your published articles and FAQs, and the entries it drew on are listed beside the draft, so you can read the source before you send and drop a link to the article into the reply. Most suites do something equivalent within their own walls: Zendesk AI answers from Zendesk Guide, Help Scout AI from Docs. The combination to watch for is a standalone knowledge base plus a separate inbox, where the content is good and the tool writing your replies cannot read a word of it.
How do I know which articles to write or retire?
The evidence is already in your inbox, so AcornReply puts it on a knowledge analytics page. Gap notes flag an existing entry that did not cover the question that just came in, which is your write-this-next list. A never-shipped list names published entries the retriever keeps picking, at least five times in 90 days, that nobody has ever actually sent to a customer: usually a sign the entry is wrong or unclear rather than unwanted. Per-article view counts show what customers really read, counted against a pseudonymous daily-rotating visitor hash rather than a tracking cookie, and published entries with no views and no credit at all are listed on their own. Separately, the private entries captured from resolved conversations, which stay internal and only inform drafting, are retired by a weekly sweep once they have gone 90 days without earning anything. Retiring anything is an unpublish, never a delete.
Can I move an existing help center across?
Into AcornReply, yes, with an honest caveat about how much of it is hands-off. There is a direct importer for Crisp that pulls the articles over and re-hosts their images. For everything else, including Zendesk, Intercom and Help Scout, you export and bring a CSV or JSON file of question-and-answer pairs (up to 5 MB and 2,000 rows), or push content in through the API. Either way the entries land unpublished, so you read them before a customer can, which is worth the extra step: a help center moved over verbatim usually contains several answers that stopped being true a year ago.
Can an AI agent write and fix the articles for me?
In AcornReply, yes, if you want one to. The knowledge base has an MCP server and a matching REST API, both documented on our developers page, covering search, create, update, publish, categories and image upload, so a coding agent can draft an article, preview the write with a dry run, and leave it unpublished for you to approve. Two caveats worth saying out loud: an API key is scoped to one workspace but not to one action, so any key that can read the knowledge base can also write to it, and nothing in the loop reviews an agent for taste or accuracy. Several documentation tools now expose APIs and MCP servers of their own, so check the specific ones on your shortlist rather than assuming this is rare.