Skip to content

Security overview

See in one table how Kabaido isolates, encrypts and protects your commercial data.

Updated 23 September 2026

Why
A quote shows what a business buys, from whom, at what margin and for which customer.
How
Isolation lives in the database, not in application code, so a missed filter cannot leak another organisation's rows.

The model in one view

LayerPractice
IsolationEvery row is organisation scoped under row level security in Postgres. Storage paths start with the organisation's id.
EncryptionTLS in transit, AES-256 at rest, and integration credentials encrypted again by the application.
AccessRanked roles enforced by the database, owner safeguards and an audit log of administrative actions.
Your customersA separate principal that is never a member of your organisation. See the customer facing trust boundary.
AIAnthropic only, whose commercial terms bar training its models on customer content. Every value is cited or left empty.
HostingDatabase and files in the EU (AWS Frankfurt, eu-central-1); the application runs in London.
PaymentsStripe holds card details. Kabaido never sees them.
Your dataExport at any time; deletion by the owner or on request.

Every plan runs on the same shared infrastructure with the same isolation. There is no dedicated or customer held key tier today.

Every provider Kabaido runs on holds SOC 2 Type II, and the database, hosting and AI hold ISO 27001 too. The security page links each provider's own page so you can check.