Trust

Security

Dedicated database per tenant, dedicated encryption key, and an incident policy we publish against.

Talk to SalesSee pricing

Overview

Security in one paragraph.

Every tenant runs in a dedicated database with its own encryption key, held in a hardware security module. There is no shared schema and no cross-tenant query path. Key rotation is quarterly and can be triggered by you at any time.

Access to production requires hardware-token authentication and is logged with the ticket that justified it. We publish an incident report within five working days of any incident affecting your tenant, whether or not the cause was ours.

Tenancy
Dedicated database and encryption key per tenant, keys held in HSM
Encryption
AES-256 at rest, TLS 1.3 in transit, no downgrade path
Access control
Hardware-token authentication for production, ticket-linked audit log
Key rotation
Quarterly by default, customer-triggered on request
Penetration testing
Annual third-party test; summary letter under NDA
Incident reporting
Published within five working days, cause regardless
1:1
Tenant to database
AES-256
At rest
TLS 1.3
In transit
5 days
Incident report

Next step

Talk to a senior solutions engineer.

Your first call is with an engineer, not a sales-development representative.

Talk to SalesRead the architecture overview