Security & Compliance
How isolation, credentials, and access control actually work — and what isn't certified yet.
BYOK credential handling
Credentials are envelope-encrypted with AES-256-GCM, scoped to org, provider, and purpose. There's no shared platform key sitting behind the scenes — every outbound call to a model provider uses the credential you supplied, full stop.
Tenant isolation
Postgres Row-Level Security on every tenant table, with the application connecting as a non-owner role. This is a database guarantee, not an application-layer convention — it holds even if application code has a bug.
Auth
| Layer | Mechanism |
|---|---|
| Dashboard sessions | Browser session, exchanged for control-plane calls through a same-origin BFF |
| Data-plane traffic | API keys, scoped to an org |
| Authorization | RBAC — permissions, roles, and role assignments scoped to the org |
Audit trail
Security-relevant actions are recorded and visible from Dashboard → Audit — a record of who changed what, and when, without digging through logs.
What's not here yet
No certification exists today
SSO/SAML/SCIM and SOC 2 / ISO 27001 are not implemented. If either is a procurement requirement for you, treat it as a roadmap item — see Roadmap & Changelog — not an assumption.
Reporting a vulnerability
Found something? Contact the team directly rather than filing a public issue — see Contact on the Business & Pricing page.
Related