Skip to content

Security at Keiki

Your agents hold your keys and talk to your customers. Here is how we protect both.

Compliance

Keiki is SOC 2 and HIPAA compliant.

To request our compliance documentation, email support@onkeiki.com.

Encryption

Bring-your-own keys are encrypted at rest with AES-256-GCM. Each value has its own nonce and authentication tag. The encryption key lives in a managed secret store, not in the database or in source code. Traffic to Keiki uses TLS.

Keys the agent never sees

A secret can be bound to a host. The sandbox then gets a placeholder, and the real value is added only on the way out to that host. Secrets do not enter the prompt, the transcript, traces, or tool arguments. Keiki’s own provider credentials never reach a sandbox or a prompt.

Data storage and your own database

If you run the agent loop yourself with the SDK, history, profiles, and usage can live in your own database. Messages that go through Keiki-provisioned channels are also stored by Keiki so they can be delivered. To keep message storage on your side, self-host the transport as well.

Access and SSO

Organizations have four roles: owner, admin, member, and viewer. Viewers are read-only. SSO access requires the workspace spending threshold or an explicit access grant. An Enterprise label alone does not enable it. You can require SSO for your verified domains. Sessions expire, and signing out ends them on the server.

Report a vulnerability

Email support@onkeiki.com. Include the URL, what you observed, and steps to reproduce it. Do not include an active credential or unnecessary personal data.

Read the security docs · support@onkeiki.com