# OpenKUAI

> Public articles, products, answers and machine endpoints for OpenKuai.

## For enterprise users

- [Sign in](https://openkuai.com/login/): console access and pre-conditions
- [Onboarding](https://openkuai.com/answers/how-can-my-team-adopt-openkuai/): how a self-hosted rollout starts
- [Answers](https://openkuai.com/answers/): adoption, the WhatsApp loop, data residency
- [Security and data residency](https://openkuai.com/answers/where-does-customer-data-live/): where the customer corpus lives
- [Products](https://openkuai.com/products/): the deployed components
- [News](https://openkuai.com/news/): release notes and milestones
- [Support](mailto:chance@openkuai.com): contact the operator

## For prospective customers

- [What OpenKuai is](https://openkuai.com/answers/what-is-openkuai/)
- [How the WhatsApp agent works](https://openkuai.com/answers/how-does-the-whatsapp-agent-work/)
- [Product suite](https://openkuai.com/products/)
- [Explore](https://openkuai.com/explore/): capability slate
- [Writing](https://openkuai.com/writing/): research, product notes and measurements
- [Contact for pilots](mailto:chance@openkuai.com)

## Machine endpoints

- [About OpenKuai](https://openkuai.com/about.md)
- [Profile JSON](https://openkuai.com/api/profile.json)
- [Search index](https://openkuai.com/api/search-index.json)
- [OpenAPI](https://openkuai.com/openapi.json)
- [Full corpus](https://openkuai.com/llms-full.txt)
- [AI catalog](https://openkuai.com/.well-known/ai-catalog.json)
- [MCP Server Card](https://openkuai.com/.well-known/mcp/server-card.json)
- [MCP discovery shim](https://openkuai.com/.well-known/mcp.json)
- Ask/MCP endpoints are not configured on this deployment (static search and curated answers only).

## Series

- [Research](https://openkuai.com/writing/research/)
- [Product](https://openkuai.com/writing/product/)

## Answers

- [How can my team adopt OpenKuai?](https://openkuai.com/answers/how-can-my-team-adopt-openkuai.md): Adoption starts with a self-hosted deployment. Your reps keep their own WhatsApp business numbers; your product knowledge is imported into Kuai KB from existing sources; then you switch on human+agent teaming and tune the policy engine per team.
- [How does the OpenKuai WhatsApp agent work?](https://openkuai.com/answers/how-does-the-whatsapp-agent-work.md): Each sales rep gets their own WhatsApp business number on the official Cloud API. When a customer messages in a 1:1 thread, the agent answers from the product catalogue with citations, qualifies the enquiry, and escalates to the rep when needed. Sends are gated on a human authorisation row.
- [What is Kuai KB?](https://openkuai.com/answers/what-is-kuai-kb.md): Kuai KB is OpenKuai's knowledge core — a product knowledge base maintained by agentic tooling, applied through an auditable ledger, and served read-only with a review board, chat, and full audit log. Agents query it over MCP with citations.
- [What is OpenKuai?](https://openkuai.com/answers/what-is-openkuai.md): OpenKuai is a customer service agent and analytics system for sales teams. Each rep gets an AI agent on their own WhatsApp business number; agents answer product enquiries with citations, and a human stays the authorising party. It is self-hosted, so customer data stays in-house.
- [Where does OpenKuai keep customer data?](https://openkuai.com/answers/where-does-customer-data-live.md): On your own infrastructure. OpenKuai is self-hosted — the customer corpus, sessions, and CRM all live on your node, and any relay that reaches WhatsApp carries ciphertext only. No third-party SaaS ever sees the customer data.

## Recent articles

- [Welcome to OpenKuai](https://openkuai.com/2026/09/23/welcome-to-openkuai.md): OpenKuai is a customer service agent and analytics system for sales teams. This site documents capabilities, research reports, deploy milestones, and builder notes.
- [Kuai KB Is Live — Serving the Real Database, Read-Only](https://openkuai.com/2026/09/23/kuai-kb-is-live.md): The Kuai KB knowledge tier went live, serving the real database read-only behind a review board and audit log; the fetch tier lands sha256-checked records hourly.
- [Inside the Enquiry Loop — What We Measured](https://openkuai.com/2026/09/23/whatsapp-enquiry-loop-measured.md): The 1:1 WhatsApp enquiry loop was measured end to end, webhook to send, on the live channel. The transport is not the bottleneck; the time goes to knowledge-base coverage and model re-asks.
- [K4 — Product Knowledge That Maintains Itself](https://openkuai.com/2026/09/22/k4-knowledge-automation.md): K4 keeps the product knowledge base current through agentic fetch, a ledger applier, retrieval over pgvector, and MCP bindings — live end to end, serving the real database read-only.
- [One Registry Name per Service — the Networking Model](https://openkuai.com/2026/09/21/one-registry-name-per-service.md): The OpenKuai networking model — three planes (bridge, tailnet, internet), a registry giving one name per service, and agents that are clients of everything and servers of exactly one thing.
- [K1 — WhatsApp, Team Formation, and Segmentation](https://openkuai.com/2026/09/20/k1-whatsapp-teams-segmentation.md): K1 is the delivery path — reps on their own WhatsApp business numbers (official Cloud API), human+agent team formation, and customer segmentation. Transport is live; the team and segmentation product surface is in design.
- [K3 — Conversation Intelligence via Graph RAG](https://openkuai.com/2026/09/19/k3-conversation-intelligence.md): K3 makes every customer↔rep↔agent conversation searchable and reviewable through Graph RAG, with citations — a second, rep-scoped corpus with index-time privacy and retraction paths.
- [One Bot per Rep — Why OpenKUAI Is 1:1-Only](https://openkuai.com/2026/09/18/one-bot-per-rep.md): OpenKUAI is 1:1-only by design — one agent per rep on the rep's own WhatsApp business number, with group chats out of scope. The 1:1 thread keeps session ownership, privacy and per-rep scoping simple.
- [K5 — Analytics as a Rendered Page, Not a BI Stack](https://openkuai.com/2026/09/17/k5-analytics-rendered-page.md): K5 renders analytics as a page over the existing stores — conversation corpus, Kuai DB, and the CRM — with no warehouse, no BI stack, and no event pipeline.
- [Data Sovereignty by Architecture — Ciphertext-Only Egress](https://openkuai.com/2026/09/16/data-sovereignty-ciphertext-egress.md): Data sovereignty is preserved architecturally — the egress relay that reaches WhatsApp carries ciphertext only; sessions and message content never leave the customer's own node.
- [Agents Draft, Humans Send](https://openkuai.com/2026/09/15/agents-draft-humans-send.md): The OpenKuai policy engine — never-reply rules, quiet hours, rate limits, and disclosure — with every send gated on a human authorisation row. Agents draft; humans send.