Contextual help inside your product
Answers in-app, so users never leave the flow.
Users hit a confusing screen, cannot find help without leaving your product, and either abandon the task or file a ticket. Your help center gets traffic, but the drop-off happens in-app, where the docs are not.
Embed Kelu with the drop-in widget in chat, sidebar, or Cmd+K mode. Users ask from the screen they are stuck on and get cited answers without context-switching; the streaming REST API lets you build fully custom in-product experiences on the same pipeline.
How it works
- 1
Index your docs and help center as sources.
- 2
Embed help in-app: the drop-in widget in chat, sidebar, or Cmd+K mode.
- 3
Users ask from the screen they are stuck on and get cited answers without leaving the flow.
- 4
For fully custom UIs, build on the same streaming REST API the widget uses.
What you get
- Answer users at the moment of confusion instead of after the context switch.
- Reduce in-app abandonment on confusing screens.
- Ship help UI in an afternoon with the widget, or build fully custom on the REST API.
- Keep in-app answers identical to your help center's — one knowledge index.
Features that make it work
Got questions?
Frequently asked questions
What integration options are there?
Today: the drop-in widget (one script tag; chat, sidebar, or Cmd+K modes), the streaming REST API for fully custom UIs, or the React and JavaScript SDKs on npm.
Is it safe to ship a key in client-side code?
Yes — public client keys (kl_pk_…) are designed for the browser and grant access only to the specific knowledge base and endpoints they were issued for. Backend integrations use a separate client ID/secret pair that stays server-side.
Can the widget match our product's look?
The widget is themable, and enterprise plans can hide Kelu branding. For pixel-perfect control, build your own UI on the REST API and own every element.
How long does setup take?
Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and Kelu crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack bot installs in a few clicks. There is no model to fine-tune and no infrastructure to run.
Are answers backed by citations?
Yes. Every answer from your docs includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.
Is my 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 questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, a widget without Kelu branding, and a custom SLA.
Which knowledge sources can I connect?
24 source types: websites, GitHub (docs files, source code, issues, pull requests, discussions), Notion, Confluence, Google Drive, OneDrive, Zendesk (Help Center and solved tickets), Jira, Jira Service Management, Linear, Salesforce Knowledge articles, Salesforce Cases, Discourse, Stack Overflow for Teams, YouTube, OpenAPI specs, S3, curated Q&A, and direct file uploads (PDF, DOCX, XLSX, CSV, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub sources can re-index automatically via webhook on every push.
What happens when the AI is not confident in an answer?
Answers are grounded in your sources. When they do not cover a question, Kelu returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.
Related use cases
Unblock developers integrating your API
Answer auth, webhook, and SDK questions with code-aware AI.
Put your docs inside the IDE via MCP
Cursor, Claude, and other MCP clients answer from your docs.
Fix developer portal search
Hybrid semantic + keyword search that actually finds the page.
Ready to contextual help inside your product?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Free to start · No credit card required