Internal knowledge assistant
for your whole org
Connect Confluence, Notion, Google Drive, and internal docs sites. Give every engineer, support agent, and onboarding hire accurate AI answers with source citations — secured by SSO and granular permissions.
Enterprise features
Everything needed for a secure, organization-wide knowledge deployment
Multi-source Internal Knowledge
Unify Confluence spaces, Notion wikis, Google Drive folders, internal docs sites, and GitHub repos into a single queryable index.
SSO & Identity Integration
OIDC and SAML 2.0 support. Connect Okta, Azure AD, Google Workspace, or any compliant identity provider.
Granular Permissions
Control which teams see which knowledge bases. Engineering answers come from engineering docs. Support answers from support runbooks.
Microsoft Teams Bot
Deploy an AI assistant into Teams channels and DMs. Engineers get answers to incident runbooks, architecture decisions, and process docs in real time.
Dedicated Support & SLA
Dedicated support and a custom SLA, agreed in your Enterprise contract.
Compliance & Security
GDPR compliant, data encryption at rest and in transit, audit logs, custom data retention, and DPA on request.
How it works
- 1
Connect internal sources — Confluence spaces, Notion wikis, Google Drive folders, OneDrive folders, GitHub repos, and internal docs sites — into a single indexed knowledge base.
- 2
Configure SSO with your identity provider (OIDC or SAML 2.0) so employees sign in with existing corporate credentials. With Require SSO on, only the workspace owner keeps password sign-in, so an outage at your identity provider can't lock you out.
- 3
Grant teams access to knowledge bases with granular permissions, so each department queries only the content scoped to it.
- 4
Deploy the assistant where work happens — Ask in the dashboard, the browser extension, internal MCP servers, or Slack and Teams bots for knowledge bases that aren't internal.
- 5
Review audit logs and workspace analytics to see who is asking what, and where knowledge gaps exist across the org.
What you get
- One assistant across every internal knowledge silo, with citations back to the source document.
- SSO-secured access, with knowledge base permissions checked on every question in Ask, the browser extension and internal MCP servers.
- Engineers, support agents, and new hires self-serve answers instead of interrupting experts.
- Audit logs and access controls that satisfy security review from day one.
- Knowledge stays current via scheduled syncs — no manual re-indexing.
- Workspace-wide analytics on question volume, top sources, and knowledge gaps.
Enterprise-grade security from day one
Kelu is designed for organizations where data security and compliance are non-negotiable.
Got questions?
Frequently asked questions
What identity providers do you support for SSO?
We support SAML 2.0 and OpenID Connect (OIDC). This includes Okta, Azure AD, Google Workspace, OneLogin, Ping Identity, and any SAML-compliant identity provider. Setup typically takes 1 business day.
How do permissions work across departments?
You organize knowledge into knowledge bases (e.g., Engineering, Support, Finance). Access to each is granted per person on its Permissions tab. An engineer with access to Engineering can query that knowledge base but not the Finance one.
How is our internal knowledge data protected?
Your data is fully isolated from other customers. It is encrypted at rest (AES-256) and in transit (TLS 1.3). You can sign a DPA. Data is stored in the United States.
What is included in dedicated support?
Enterprise customers get dedicated support and a custom SLA. Response times are agreed in your contract.
How long does enterprise onboarding take?
Most deployments complete within 2 weeks, including SSO setup, collection configuration, and initial source indexing. Complex multi-source environments with custom permissions may require additional time.
Is our internal content used to train AI models?
No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own organization's questions. Content is never shared across customers or used for model training.
Are answers backed by citations?
Yes. Every answer from your documents cites the ones it was drawn from, with links back to the original Confluence page, Notion doc, or file. Employees can verify any claim against the source — essential when answers inform incidents, compliance, or customer commitments.
Ready to build your knowledge assistant?
Talk to our enterprise team about your requirements and get a custom deployment plan.
Contact Sales