Private / on-premise
The AI models, voice agents, private chatbot, knowledge base, and every message live entirely on your servers. Nothing leaves.
IbhanAi Labs · Unified Messaging
Your staff know what to say — they just shouldn't have to paste sensitive information into a public AI. Kukku lets them dictate, search your own knowledge, and reach people by message or voice — every word following your policy, on your servers or in the cloud.
Four things Kukku does — in plain language
It meets your people where they already work, uses only your organisation's approved knowledge, speaks and listens on voice calls, and gives everyone a private chatbot that never leaks a word.
However your people capture information — talking, typing shorthand, or writing on paper — Kukku accepts it and turns it into a clear, professional record.
Examples
Guardrails first. Everything is checked against your policy before it goes anywhere. If it can't be said — bad news over SMS, a settlement figure in text, an identifier where it doesn't belong — Kukku flags it and asks for a human decision.
Your protocols, playbooks, leaflets, and approved glossary already exist as documents on someone's drive. Kukku uses only those — so every message stays inside what your organisation actually approves.
Examples
No IT project. You edit the glossary and upload new policy documents through a simple screen. No AI training. It's live for the next message.
Not everyone reads SMS. Kukku uses your voice-agent platform to speak the message — and to answer when people call in.
Outbound — Kukku calls them
Inbound — they call Kukku
Same policy, every channel. If it can't be sent as text, it isn't spoken either. Nothing goes out and nothing is spoken without a human having approved it once.
Your people already use public chatbots to draft and look things up — pasting patient details, claim numbers, and internal policies into someone else's cloud. Kukku gives them a private chatbot instead — on your infrastructure, reading only your approved knowledge, never sending a word outside your walls.
Examples
The same AI that powers your outbound messages powers the chatbot — so tone, terminology, and compliance boundaries are identical whether staff are drafting a message, summarising a thread, or just asking a question. Staff stop pasting sensitive information into public chatbots, and every question and answer can be audited.
Compliance, built in
You write your communication rules once — Kukku enforces them on every message, every call, every summary, and every chatbot answer, and shows the person approving exactly which rule was applied. Nothing gets out unless the guardrails pass and a human clicks approve.
You also see a complete record of everything sent, everything spoken, every question asked, and every knowledge document the AI used — for audit, review, or dispute.
Deployment
Kukku is built for regulated environments where your data cannot leave the building. And the AI models can be tuned to your organisation — your terminology, your tone, your typical scenarios — so suggestions read like they came from your senior staff.
The AI models, voice agents, private chatbot, knowledge base, and every message live entirely on your servers. Nothing leaves.
For less-sensitive work, use frontier models via API for the highest language quality.
Clinical conversations on-premise; internal team notifications in the cloud — all under the same compliance policy.
The same model that drafts your outbound messages answers your team's day-to-day questions, entirely inside your infrastructure.
Who Kukku is for
…and any organisation whose staff are already using public chatbots to get their work done, but shouldn't be. If your compliance team has ever had to send a "please don't paste patient information into ChatGPT" email — Kukku is the fix. Same convenience for your staff, none of the risk.
Ready to see it with your own examples?
One you find hard to write, one you get too many phone calls about, and one a staff member would normally have asked a public chatbot about. We'll show you all three, handled through Kukku, in a 20-minute walkthrough.