Deploy Knoku
Deploy Knoku where people already ask questions: on your website, inside support flows, in community channels, and in developer tools.
Every surface uses the same project index. The important difference is audience: public visitors should only reach Public content, while trusted team and backend surfaces can reach Internal content when configured.
Add repo sync, crawls, uploads, and workspace connectors from Sources.
Website and product
| Surface | Best for | Guide |
|---|---|---|
| Website widget | Docs sites, marketing pages, help centers, and product pages | Website widget |
| Widget builder | Dashboard embed snippet without hand-editing attributes | Widget builder |
| Public API | Custom product UI, backend workflows, and internal tools | Public API |
Support
| Surface | Best for | Guide |
|---|---|---|
| Support form deflector | Searching docs before a visitor submits a support form | Support form deflector |
Community
| Surface | Best for | Guide |
|---|---|---|
| Slack | Team workspaces and internal support workflows | Slack |
| Discord | Public communities and developer support servers | Discord |
Developer tools
Use these when agents or IDEs need documentation context.
| Surface | Best for | Guide |
|---|---|---|
| MCP | Cursor, Claude Desktop, and other MCP clients | MCP |
Corpus access
Surface access is controlled by source groups:
| Surface | Corpus |
|---|---|
| Website widget | Public |
| Support form deflector | Public |
| MCP | Public |
| Discord | Public |
| Slack | Public + Internal |
| Public API key with public scope | Public |
| Public API key with internal scope | Public + Internal |
| Zendesk agent tooling | Public + Internal, Enterprise-gated |
Do not rely on frontend attributes to hide or expose knowledge. Put the document in the correct source group.
Configure in the dashboard
| Surface | Dashboard area |
|---|---|
| Website widget | Project -> Widgets |
| Slack, Discord, and deflector | Project -> Channels |
| MCP | Project -> Settings -> MCP |
| Public API | Project -> API Keys |
Sessions and analytics
Every surface creates sessions. Open Sessions to read the full conversation, cited sources, feedback, channel, and intent classification.
Analytics aggregates usage across channels: message volume, deflection, repeated questions, coverage gaps, cited sources, and traffic geography where available.