No warehouse. No BI stack.
When analytics comes up, the default reflex is a pipeline: events to a warehouse, a BI tool on top, dashboards to maintain. K5 refuses that reflex. The analytics capability of OpenKuai is a prime-agent plus HTML5 rendering over the dataset — the stores that already exist: the conversation corpus, the Kuai database, and the CRM.
What it produces
A rendered page. The manager asks; the agent queries what is already there and renders the answer as HTML5. What ships is a readable picture of the team’s conversations — response patterns, enquiry topics, escalation rates — not a new system to operate.
Why this shape
Every additional moving part in the analytics path is another thing that can drift from the truth it reports. Rendering directly over the stores of record means the numbers cannot disagree with the source — there is only one source. For a self-hosted product run by a small team, the surface you don’t have to operate is the most valuable feature you can ship.