Enterprise controls without the enterprise drag
Your knowledge is your business. Kelu isolates every workspace, can mask PII before content reaches the LLM, never trains models on your data, and ships the SSO, audit, and permission controls your security review will ask about.
Controls that matter
The security posture behind every deployment
Data Protection
- Workspace isolation for content, embeddings, and chats
- Encryption in transit and at rest
- Optional PII masking before the LLM call
- Your data is never used to train models
- Delete a source and its indexed content goes with it
Identity & Access
- SSO via OIDC and SAML 2.0
- Per-knowledge-base permissions for members
- Restricted document visibility within a knowledge base
- Client keys with scoped, revocable access
- Allowed-groups enforcement on integration keys
Auditability
- Workspace audit logs for admin actions
- Conversation history with citations
- A trace behind every answer
- Signature verification on every webhook
Grounded answers are a security feature
The biggest AI risk in customer-facing deployments isn't a breach — it's the assistant confidently saying something your company never approved. Kelu's architecture answers only from content you indexed, cites it, and falls back transparently otherwise.
- Answers bounded by your approved, indexed content
- Citations make every claim verifiable
- Public surfaces retrieve only public documents
- Enterprise plan adds OIDC/SAML SSO and SSO enforcement
Type
External
Customer-facing docs and support content
Internal
Team knowledge for your workspace
No public surface: the widget, the public API and MCP all refuse it, and client keys cannot be issued. Only signed-in workspace members with chat access, plus any chat bot you connect.
Who can reach this
Every way this knowledge base can currently be asked a question
- Public surface
None — internal
Widget, public API, MCP, form deflectors
- Chat bots
Slack
Answers from restricted documents, to everyone in the channel
- Workspace members
2 also granted individually
Private content stays private, and secrets stay sealed
Credentials are encrypted
Connection secrets are sealed with AES-256-GCM. If one can't be opened, the sync stops instead of running without it.
Private stays private
Internal knowledge bases have no public surface at all. To keep past tickets private, add them to an internal knowledge base.
A bad sync can't empty it
If one sync would remove more than 45% of a source's pages, Kelu holds the removals until a person approves them.
Got questions?
Frequently Asked Questions
Common questions about Security & Privacy
No. Indexed content, embeddings, and conversations stay isolated to your workspace and are used only to answer your own questions. Nothing is shared across customers or used for model training.
When PII masking is on for a knowledge base, personal data in its content and in widget, API, and Ask questions is masked before it reaches the LLM, and conversations are stored with that masking applied. Data is encrypted in transit and at rest.
OIDC and SAML 2.0 connections are supported per workspace, so employees authenticate through your identity provider. SSO is on the Enterprise plan; audit logs are on every plan.
Three layers: separate knowledge bases for public and internal content, per-knowledge-base permissions for members, and restricted document visibility within a knowledge base. Public widgets and API keys retrieve only public documents.
Bring it to your security review
Read the security overview, or talk to us about enterprise requirements.
Free to start · No credit card required