Trust center
Security controls and operating boundaries
A factual view of the service’s current controls, with roadmap work clearly separated from finished protections.
Trust center
A factual view of the service’s current controls, with roadmap work clearly separated from finished protections.
Control register
Status reflects the production controls reviewed September 28, 2026. Planned integrations stay outside the trust boundary until their own security gates pass.
Product and account forms accept lifecycle metadata and structured business details only.
Forced PostgreSQL row-level security rechecks organization scope beneath the application.
Short-lived opaque sessions, secure host-only cookies, password hashing, throttling, and TOTP MFA.
Security-relevant workspace changes create immutable, actor-attributed audit records.
Runtime, worker, migration, and backup processes use distinct database identities and grants.
An off-host drill passed September 7: B2 download, age decryption, checksum validation, and an isolated PostgreSQL restore.
Operating boundary
Access controls separate workspaces, encrypted backups support recovery, and restore rehearsals check the running application and tenant isolation. Our security architecture explains the controls and their limits.
Read the security architectureResponsible disclosure
Send a concise report with impact and reproduction steps. Do not include live credentials or access data you do not own.