Rights by role
Members see their own work and what is shared with them; a manager sees the team; administrators set who sees which table. Kibo follows the same rights as the screens.
Kibo / Security
Security and governance, built into the product.
Role-based access, approvals enforced by code, an audit record of every action and encrypted backups. The AI runs on the same server as your data, so no third-party AI provider ever sees it.
How it is built
Eight controls, all in the product.
Confirmation before every action
Sending, deleting, paying, granting access: Kibo shows exactly what it will do and acts only after the person confirms.
Approvals by code
Who approves what, in which order, above which amount, is applied by code, the same way every time. The model never decides that a step can be skipped.
A record of everything
Every action and every rule applied is written down with a name, a time and a version, for your audit.
Encrypted backups
Backups are encrypted with AES-256 under a key that is never stored next to them. On your own server, you hold the key.
No outside AI
The model runs inside your Kibo server. Prompts and answers are never sent to an outside AI provider, and no telemetry is sent to anyone.
Customers see only their own
When your customers use the portal, they see only their own records, through a short fixed list of actions.
Leaving is clean
An owner can delete the organisation; nobody can use it from then on and its data is erased after 30 days.
Plainly
What we do not claim.
Kibo has no security certification of its own yet. When we host it for you, the contract names the hosting provider and the region. We will send the detailed data sheet on request.
More: sovereignty · what is inside · why trust it