Internal knowledge stays internal.
Every source in your index is marked public or internal. Customer-facing channels answer only from public sources. Your team sees everything.
No credit card required
One index, two audiences
Connect internal runbooks and wikis next to your public docs without publishing them. The audience is set on the source and respected everywhere.
Marked at the source
Website and docs crawls are public. Notion, Confluence, and Jira connect as internal sources. GitHub repos can be public, internal, or both.
Filtered per channel
Each channel searches only the sources its audience is allowed to see. One index, no duplicate setup to maintain.
Never a public link
Internal pages and uploaded files are cited by name in team channels and never served to website visitors.
Which channels see what
Every channel answers from the same project. The difference is scope.
Customer channels
Visitor-facing surfaces answer from the sources you marked public, and cite the page the answer came from.
- Website widget
- Answers on your docs and marketing site.
- Support form
- Answers before a ticket is created.
- Discord
- Community questions in your server.
- MCP server
- Cursor, Claude Desktop, and other MCP clients.
- Public API
- Your own UI with a public-scope key.
Team channels
Your team searches public and internal sources together. Answers still cite their sources, so an agent can open the original page in Notion, Confluence, or Zendesk.
- Slack
- Your team asks across public and internal sources.
- Zendesk agent tools
- Suggested answers while agents work tickets.
- MCP (internal)
- Internal-scope MCP for your own agents and tools.
- Agent Replay
- Review how an answer was reached, across every source.
- Internal API
- Server-side keys with internal scope.
API keys carry the boundary
When you build on the API, the key decides the scope, not the code that calls it.
pk_live_·······Public scope
Safe for browsers and visitor-facing surfaces. Searches public sources only, same as the widget.
sk_live_·······Internal scope
Reaches workspace sources and uploads. For server-side use in internal tools.
Questions about boundaries
How public and internal knowledge stay separate.