Security
Security is a first-class design constraint
Vorne is built to be governed, auditable, and least-privilege by default.
The practices behind it
Tenant isolation
Every tenant-owned record is scoped by organization and protected by PostgreSQL row-level security, enforced at the database. Not just the application.
Encryption of secrets
Integration credentials and access tokens are stored only as encrypted references (AES-GCM), never in plaintext, with key identifiers for rotation.
Least privilege
Authorization is applied at the API, domain, workflow, integration, and database layers. The runtime role is subject to tenant policies.
Auditability
Every side-effecting operation emits an append-only audit event. Destructive actions are reversible where possible.
Governed AI
Agents run under budgets, step limits, permissions, and approval gates. The creator agent is never its only verifier.
Data governance
Explicit data classification, retention, export, and two-phase reversible deletion with a grace period.
See also our Trust Center, Privacy Policy, and Subprocessors.