Knowledge base software for a branded customer help center

Run the help center on your domain and your outline. The software keeps one structured knowledge base behind that center, so the article and the answer share a source.

Publish with Help, Docs, and Chat templates on your domain. Visitors use the help center. The workspace where your team edits stays under access control.

The Chat template returns answers with source citations and a link to the full document. That is the live behavior described in Baklib’s AI guide. Sentence-level RAG traces are on the roadmap. When you compare products, ask to see a citation on a published article.

MCP lets an IDE or agent read and update organization content with an API key. A write still needs a person to confirm. On a private deployment, that API points at your own domain. See the MCP guide.

This is key-based access plus a confirmation step. Ask separately whether an agent is limited to a single published site.

Install on your own infrastructure when data must stay in your environment. The Chinese page 私有化知识库 summarizes that path. Install steps: Docker deployment.