Give your team answers from its internal docs
Connect the runbooks, guides, and procedures your team maintains. Employees can ask in a connected chat app and follow answers back to the source. Review access requirements with us before a private rollout.
Used by documentation and developer-experience teams
What it does
Help your team find documented answers
Answers from approved internal sources
Index your internal documentation, processes, and knowledge base so answers can draw on company-specific context and link back to the source.
Frees senior people from repeat questions
Handle repeat questions about tools, processes, and policies without asking the same subject-matter expert each time.
Shows recurring and unresolved questions
Use query analytics to find topics people ask about repeatedly and questions the documentation does not yet cover.
Sounds like your company
Configure tone, terminology, and voice. Define what’s in scope and what isn’t. The assistant introduces itself the way you’d introduce it, in the language your team actually uses.
Access controls that fit how you work
Configure project-scoped API keys and confirm which sources each audience may access. Contact us to review deployments that require department-level permissions.
Refreshes with your sources
Re-index on a schedule, after a commit, or through the refresh API so the assistant tracks published changes.
Connect approved sources to your team’s tools
Choose the sources this audience should use, then connect a supported chat app, internal widget, API client, or MCP tool. Keep your existing authoring workflow.
- ConfluenceWikis, spaces, and pages
- GitHubRepos, wikis, READMEs
- Internal sitesAny crawlable site or sitemap
- FilesPDF, Word, Markdown uploads
- OpenAPI specsAPI references from your current index
- Slack@-mention or DM in any workspace
- Microsoft TeamsPersonal, group, and channel chats
- Discord/ask slash command in any server
- Intranet widgetDrop-in for any internal portal
- API & MCPFor internal tools and AI assistants
Review access before you deploy
Check the project’s source scope, reader authentication, and data-handling requirements. Our Security Overview documents the available controls.
- Domain restrictionsChoose which domains may embed the widget. This controls embedding and does not replace employee authentication.
- Scoped API keysLimit an API key to a project and specific permissions. Rotate or revoke it when needed.
- Rate limitingPer-session and per-IP limits help control abuse. Review your deployment’s requirements with the product team.
- Encryption in transit and at restBiel encrypts customer content in transit and at rest. See the security documentation for current implementation details.
- Audit logsSecurity-sensitive operations are logged. See the Security Overview for the current controls.
GDPR support
A DPA is available. EU data residency is an Enterprise option.
No model training
Your indexed content and conversations are not used to train AI models.
Your tenant, your data
Indexed content stays in your project. Delete or export at any time.
Plan reader access
Confirm source access and reader authentication before making internal content available through an assistant.
“Easy to set up, yet the positive effects are felt immediately.”