Introduction
Knoku turns your documentation and support knowledge into cited answers. Index your sources once, then let visitors, community members, support teams, and developer tools ask questions against the same project.
Answers are grounded in the content you connect. When Knoku cannot find a reliable answer, it should say so instead of guessing. Analytics then show what people asked, which pages were cited, and where your docs need work.
New workspaces start with a 14-day Business trial. You can create a project, connect a source, and embed the widget without adding a card.
What Knoku does
| Area | What it handles | Start here |
|---|---|---|
| Sources | Bring docs, repos, help centers, files, and workspace knowledge into one index | Sources |
| Deploy Knoku | Put answers where users ask: website, support flows, Slack, Discord, MCP, and API | Deploy Knoku |
| Widget | Embed a cited AI assistant on your docs or product | Website widget |
| Analytics | Find repeated questions, coverage gaps, cited pages, and deflection outcomes | Analytics |
| Dashboard | Manage projects, domains, source groups, API keys, security, team access, and billing | Dashboard |
Main workflows
Add an Ask Docs widget
Use the website widget to add a chat panel to your docs, marketing site, or product. Visitors ask in natural language and receive answers with citations back to your indexed content.
Keep documentation current
Sync docs from GitHub repo sync or crawl a deployed site with website crawl. You can also connect Notion, Confluence, Jira, OpenAPI, Zendesk Help Center, and uploaded files.
Answer in team and community channels
Connect Slack or Discord so people can ask Knoku from the places they already use. Sessions and feedback still appear in the dashboard.
Give agents access to docs
Enable MCP to expose your public project index to Cursor, Claude Desktop, and other MCP clients.
Deflect support before ticket creation
Use the support form deflector to intercept a support form, search your docs first, and track whether the visitor resolved the issue or continued to support.
Public and internal knowledge
Every project has source groups. Public content can answer through visitor-facing surfaces like the widget, deflector, MCP, and public API keys. Internal content is for team/support surfaces such as Slack, Zendesk agent tooling, and public API keys configured with internal corpus scope.
Read Source groups before connecting private repositories or workspace tools.
Next step
Follow Get started to create a project, connect the first source, embed the widget, and verify citations.