{
  "audiences": {
    "enterprise": [
      "/login/",
      "/answers/how-can-my-team-adopt-openkuai/",
      "/answers/where-does-customer-data-live/"
    ],
    "prospect": [
      "/products/",
      "/products/",
      "/products/",
      "/products/",
      "/answers/how-does-the-whatsapp-agent-work/",
      "/answers/what-is-kuai-kb/",
      "/answers/what-is-openkuai/"
    ]
  },
  "articles": [
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/23/welcome-to-openkuai/",
      "markdownUrl": "/2026/09/23/welcome-to-openkuai/.md",
      "title": "Welcome to OpenKuai",
      "excerpt": "OpenKuai is a customer service agent and analytics system for sales teams. This site documents capabilities, research reports, deploy milestones, and builder notes.",
      "tags": [
        "openkuai",
        "overview"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-23"
    },
    {
      "type": "article",
      "audience": "reference",
      "url": "/2026/09/23/kuai-kb-is-live/",
      "markdownUrl": "/2026/09/23/kuai-kb-is-live/.md",
      "title": "Kuai KB Is Live — Serving the Real Database, Read-Only",
      "excerpt": "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.",
      "tags": [
        "news"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-23"
    },
    {
      "type": "article",
      "audience": "reference",
      "url": "/2026/09/23/whatsapp-enquiry-loop-measured/",
      "markdownUrl": "/2026/09/23/whatsapp-enquiry-loop-measured/.md",
      "title": "Inside the Enquiry Loop — What We Measured",
      "excerpt": "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.",
      "tags": [
        "news"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-23"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/22/k4-knowledge-automation/",
      "markdownUrl": "/2026/09/22/k4-knowledge-automation/.md",
      "title": "K4 — Product Knowledge That Maintains Itself",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-22"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/21/one-registry-name-per-service/",
      "markdownUrl": "/2026/09/21/one-registry-name-per-service/.md",
      "title": "One Registry Name per Service — the Networking Model",
      "excerpt": "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.",
      "tags": [
        "reports",
        "networking"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-21"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/20/k1-whatsapp-teams-segmentation/",
      "markdownUrl": "/2026/09/20/k1-whatsapp-teams-segmentation/.md",
      "title": "K1 — WhatsApp, Team Formation, and Segmentation",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-20"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/19/k3-conversation-intelligence/",
      "markdownUrl": "/2026/09/19/k3-conversation-intelligence/.md",
      "title": "K3 — Conversation Intelligence via Graph RAG",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-19"
    },
    {
      "type": "article",
      "audience": "reference",
      "url": "/2026/09/18/one-bot-per-rep/",
      "markdownUrl": "/2026/09/18/one-bot-per-rep/.md",
      "title": "One Bot per Rep — Why OpenKUAI Is 1:1-Only",
      "excerpt": "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.",
      "tags": [
        "news"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-18"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/17/k5-analytics-rendered-page/",
      "markdownUrl": "/2026/09/17/k5-analytics-rendered-page/.md",
      "title": "K5 — Analytics as a Rendered Page, Not a BI Stack",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-17"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/16/data-sovereignty-ciphertext-egress/",
      "markdownUrl": "/2026/09/16/data-sovereignty-ciphertext-egress/.md",
      "title": "Data Sovereignty by Architecture — Ciphertext-Only Egress",
      "excerpt": "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.",
      "tags": [
        "reports",
        "sovereignty"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-16"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/15/agents-draft-humans-send/",
      "markdownUrl": "/2026/09/15/agents-draft-humans-send/.md",
      "title": "Agents Draft, Humans Send",
      "excerpt": "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.",
      "tags": [
        "reports",
        "policy"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-15"
    }
  ],
  "answers": [
    {
      "type": "answer",
      "audience": "enterprise",
      "url": "/answers/how-can-my-team-adopt-openkuai/",
      "markdownUrl": "/answers/how-can-my-team-adopt-openkuai/.md",
      "title": "How can my team adopt OpenKuai?",
      "excerpt": "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.",
      "full": "OpenKuai is deployed **self-hosted, on your infrastructure**. A pilot has three steps:\n\n1. **Onboard the reps** — each rep's own WhatsApp business number joins via the official Cloud API; identity binds through your directory groups.\n2. **Feed the knowledge base** — Kuai KB imports from the product sources you already have, with review and audit from day one.\n3. **Pair the agents** — human + agent teams go live with the policy engine set conservatively (drafts only, quiet hours, disclosure), then loosens as trust is earned.\n\nManagers see their team's conversations through review; admins manage roles through directory groups — one source of entitlement. Reach out via the contact on the [About page](/about/) to talk through a pilot."
    },
    {
      "type": "answer",
      "audience": "prospect",
      "url": "/answers/how-does-the-whatsapp-agent-work/",
      "markdownUrl": "/answers/how-does-the-whatsapp-agent-work/.md",
      "title": "How does the OpenKuai WhatsApp agent work?",
      "excerpt": "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.",
      "full": "The interaction unit is the **1:1 thread, not a room**:\n\n1. **A customer writes to one rep's business number** — the number the rep already uses, on the official WhatsApp Cloud API.\n2. **The agent answers from the product catalogue with citations**, qualifies the enquiry, and escalates to a human when policy or confidence requires it.\n3. **A human authorises everything a customer receives** — the bridge commits before it acknowledges, and sends go out only when an authorisation row exists.\n4. **A policy engine keeps it polite** — never-reply rules, quiet hours, rate limits, and disclosure.\n\nThe agent drafts by default; it never sends autonomously."
    },
    {
      "type": "answer",
      "audience": "prospect",
      "url": "/answers/what-is-kuai-kb/",
      "markdownUrl": "/answers/what-is-kuai-kb/.md",
      "title": "What is Kuai KB?",
      "excerpt": "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.",
      "full": "**Kuai KB is the knowledge core of OpenKuai** — the source every agent and rep draws answers from.\n\n- **It maintains itself**: hourly fetch runs land sha256-checked records from your sources; a ledger applier applies them to the database idempotently.\n- **It is reviewable**: a review board for humans, and a full audit trail from every raw record to the run that fetched it.\n- **It is queryable**: retrieval over PostgreSQL + pgvector (HNSW + trigram + rerank), exposed over MCP so any agent can ask with citations.\n- **It serves read-only**: the app serves the real database through a read-only role, enforced at both the database and application layers.\n\nThe knowledge base is live and serving the real `kuai` database."
    },
    {
      "type": "answer",
      "audience": "prospect",
      "url": "/answers/what-is-openkuai/",
      "markdownUrl": "/answers/what-is-openkuai/.md",
      "title": "What is OpenKuai?",
      "excerpt": "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.",
      "full": "OpenKuai is a **customer service agent and analytics system** designed to work with **both** a company's sales team and the leads and customers that team serves.\n\nFour things, in the order a customer or a rep meets them:\n\n1. **The sales team works where they already work** — each rep on their own WhatsApp business number (official Cloud API), formed into human + agent teams.\n2. **Customers get answered in the conversation they are already in** — a 1:1 thread triggers auto-response and product enquiry from the catalogue.\n3. **Every conversation is logged, searchable and reviewable** — by humans and agents — through Graph RAG.\n4. **Product knowledge maintains itself** through agentic tooling that fits the team's existing tools.\n\nAgents are **paired with reps — not a replacement for them** — and a human remains the authorising party for anything a customer receives."
    },
    {
      "type": "answer",
      "audience": "enterprise",
      "url": "/answers/where-does-customer-data-live/",
      "markdownUrl": "/answers/where-does-customer-data-live/.md",
      "title": "Where does OpenKuai keep customer data?",
      "excerpt": "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.",
      "full": "Customer data is a **core asset held in-house**. Three non-negotiables, unchanged from the original brief:\n\n1. **The system is self-hosted** — the CRM, the conversation stores, and the session state run on infrastructure you control.\n2. **No third-party SaaS sees the customer corpus** — there is no analytics vendor, no cloud CRM, no training pipeline on the other side of your wall.\n3. **Egress carries ciphertext only** — the one relay that must reach WhatsApp's cloud never holds plaintext sessions or message content.\n\nCustomers, meanwhile, **never authenticate** — they are a third party whose data is processed, the data subject, not an account in a system."
    }
  ],
  "pages": [
    {
      "type": "page",
      "audience": "enterprise",
      "url": "/login/",
      "title": "Sign in",
      "excerpt": "Pre-conditions for the OpenKUAI data-admin console."
    }
  ],
  "products": [
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai Agent",
      "excerpt": "One agent per sales rep, answering product enquiries in 1:1 WhatsApp threads on the rep's own business number — with citations, qualification, and human-in-the-loop escalation.",
      "status": "active",
      "tags": [
        "whatsapp",
        "agent",
        "sales"
      ]
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai CRM",
      "excerpt": "The customer-side surface — NextCRM, self-hosted, extended with Kuai's rep identity spine so every conversation, lead, and approval belongs to a real person on a real team.",
      "status": "maintained",
      "tags": [
        "crm",
        "nextcrm",
        "self-hosted"
      ]
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai Insights",
      "excerpt": "Conversation analytics as a rendered page, not a BI surface — prime-agent plus HTML5 rendering over the conversation corpus and CRM, with no warehouse and no event pipeline.",
      "status": "planned",
      "tags": [
        "analytics",
        "rendering"
      ]
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai KB",
      "excerpt": "The self-maintaining product knowledge base at the core of OpenKuai — a review board, chat, and audit trail over a graph of your product knowledge, served read-only to agents and reps alike.",
      "status": "active",
      "tags": [
        "knowledge-base",
        "rag",
        "mcp"
      ]
    }
  ],
  "items": [
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/23/welcome-to-openkuai/",
      "markdownUrl": "/2026/09/23/welcome-to-openkuai/.md",
      "title": "Welcome to OpenKuai",
      "excerpt": "OpenKuai is a customer service agent and analytics system for sales teams. This site documents capabilities, research reports, deploy milestones, and builder notes.",
      "tags": [
        "openkuai",
        "overview"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-23"
    },
    {
      "type": "article",
      "audience": "reference",
      "url": "/2026/09/23/kuai-kb-is-live/",
      "markdownUrl": "/2026/09/23/kuai-kb-is-live/.md",
      "title": "Kuai KB Is Live — Serving the Real Database, Read-Only",
      "excerpt": "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.",
      "tags": [
        "news"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-23"
    },
    {
      "type": "article",
      "audience": "reference",
      "url": "/2026/09/23/whatsapp-enquiry-loop-measured/",
      "markdownUrl": "/2026/09/23/whatsapp-enquiry-loop-measured/.md",
      "title": "Inside the Enquiry Loop — What We Measured",
      "excerpt": "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.",
      "tags": [
        "news"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-23"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/22/k4-knowledge-automation/",
      "markdownUrl": "/2026/09/22/k4-knowledge-automation/.md",
      "title": "K4 — Product Knowledge That Maintains Itself",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-22"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/21/one-registry-name-per-service/",
      "markdownUrl": "/2026/09/21/one-registry-name-per-service/.md",
      "title": "One Registry Name per Service — the Networking Model",
      "excerpt": "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.",
      "tags": [
        "reports",
        "networking"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-21"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/20/k1-whatsapp-teams-segmentation/",
      "markdownUrl": "/2026/09/20/k1-whatsapp-teams-segmentation/.md",
      "title": "K1 — WhatsApp, Team Formation, and Segmentation",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-20"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/19/k3-conversation-intelligence/",
      "markdownUrl": "/2026/09/19/k3-conversation-intelligence/.md",
      "title": "K3 — Conversation Intelligence via Graph RAG",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-19"
    },
    {
      "type": "article",
      "audience": "reference",
      "url": "/2026/09/18/one-bot-per-rep/",
      "markdownUrl": "/2026/09/18/one-bot-per-rep/.md",
      "title": "One Bot per Rep — Why OpenKUAI Is 1:1-Only",
      "excerpt": "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.",
      "tags": [
        "news"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-18"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/17/k5-analytics-rendered-page/",
      "markdownUrl": "/2026/09/17/k5-analytics-rendered-page/.md",
      "title": "K5 — Analytics as a Rendered Page, Not a BI Stack",
      "excerpt": "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.",
      "tags": [
        "explore"
      ],
      "series": "",
      "seriesName": "Article",
      "date": "2026-09-17"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/16/data-sovereignty-ciphertext-egress/",
      "markdownUrl": "/2026/09/16/data-sovereignty-ciphertext-egress/.md",
      "title": "Data Sovereignty by Architecture — Ciphertext-Only Egress",
      "excerpt": "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.",
      "tags": [
        "reports",
        "sovereignty"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-16"
    },
    {
      "type": "article",
      "audience": "prospect",
      "url": "/2026/09/15/agents-draft-humans-send/",
      "markdownUrl": "/2026/09/15/agents-draft-humans-send/.md",
      "title": "Agents Draft, Humans Send",
      "excerpt": "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.",
      "tags": [
        "reports",
        "policy"
      ],
      "series": "research",
      "seriesName": "Research",
      "date": "2026-09-15"
    },
    {
      "type": "page",
      "audience": "enterprise",
      "url": "/login/",
      "title": "Sign in",
      "excerpt": "Pre-conditions for the OpenKUAI data-admin console."
    },
    {
      "type": "answer",
      "audience": "enterprise",
      "title": "How can my team adopt OpenKuai?",
      "excerpt": "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.",
      "url": "/answers/how-can-my-team-adopt-openkuai/",
      "markdownUrl": "/answers/how-can-my-team-adopt-openkuai/.md"
    },
    {
      "type": "answer",
      "audience": "prospect",
      "title": "How does the OpenKuai WhatsApp agent work?",
      "excerpt": "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.",
      "url": "/answers/how-does-the-whatsapp-agent-work/",
      "markdownUrl": "/answers/how-does-the-whatsapp-agent-work/.md"
    },
    {
      "type": "answer",
      "audience": "prospect",
      "title": "What is Kuai KB?",
      "excerpt": "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.",
      "url": "/answers/what-is-kuai-kb/",
      "markdownUrl": "/answers/what-is-kuai-kb/.md"
    },
    {
      "type": "answer",
      "audience": "prospect",
      "title": "What is OpenKuai?",
      "excerpt": "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.",
      "url": "/answers/what-is-openkuai/",
      "markdownUrl": "/answers/what-is-openkuai/.md"
    },
    {
      "type": "answer",
      "audience": "enterprise",
      "title": "Where does OpenKuai keep customer data?",
      "excerpt": "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.",
      "url": "/answers/where-does-customer-data-live/",
      "markdownUrl": "/answers/where-does-customer-data-live/.md"
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai Agent",
      "excerpt": "One agent per sales rep, answering product enquiries in 1:1 WhatsApp threads on the rep's own business number — with citations, qualification, and human-in-the-loop escalation.",
      "status": "active",
      "tags": [
        "whatsapp",
        "agent",
        "sales"
      ]
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai CRM",
      "excerpt": "The customer-side surface — NextCRM, self-hosted, extended with Kuai's rep identity spine so every conversation, lead, and approval belongs to a real person on a real team.",
      "status": "maintained",
      "tags": [
        "crm",
        "nextcrm",
        "self-hosted"
      ]
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai Insights",
      "excerpt": "Conversation analytics as a rendered page, not a BI surface — prime-agent plus HTML5 rendering over the conversation corpus and CRM, with no warehouse and no event pipeline.",
      "status": "planned",
      "tags": [
        "analytics",
        "rendering"
      ]
    },
    {
      "type": "product",
      "audience": "prospect",
      "url": "/products/",
      "title": "Kuai KB",
      "excerpt": "The self-maintaining product knowledge base at the core of OpenKuai — a review board, chat, and audit trail over a graph of your product knowledge, served read-only to agents and reps alike.",
      "status": "active",
      "tags": [
        "knowledge-base",
        "rag",
        "mcp"
      ]
    }
  ]
}