Products
How Vorynza protects your databases, credentials, and data at every layer of the stack.
Database passwords and connection strings are protected with strong authenticated encryption before storage. Encryption material is kept separate from the encrypted data.
All database connections require SSL (sslmode=require). Unencrypted connections are rejected at the transport layer.
Each Vorynza service gets a dedicated database name and dedicated database role. Customers cannot access each other's databases. No shared roles.
Vorynza service components run with narrow access for their responsibilities. Administrative credentials are never exposed to application code.
Sensitive actions, including password rotation, service deletion, and credential reveal, are recorded in an append-only audit log with user ID, timestamp, and action type.
Database passwords are only shown during approved reveal flows. The requester's identity and action are recorded for audit review.
If you discover a security vulnerability in Vorynza, please report it responsibly. We investigate all reports and respond within 2 business days.
security@vorynza.cloudPlease do not file public issues for security vulnerabilities. Use the email above.