Network and database security

Security layers

• TLS protects data in transit.
• Private infrastructure and firewalls restrict service exposure.
• Per-customer databases and roles enforce logical isolation.
• Connection and storage quotas limit noisy-neighbor impact.
• Audit history records control-plane actions.

Why customer roles do not have CREATEDB

On shared PostgreSQL infrastructure, CREATEDB would let a tenant create unmanaged databases outside Renviq quotas and lifecycle controls. Renviq keeps that privilege with the provisioning layer and provides safe workflows—such as the Prisma shadow database wizard—when tooling needs an additional database.

Customer responsibilities

• Keep dependencies and PostgreSQL drivers supported.
• Use parameterized SQL and application authorization.
• Do not expose connection URLs in client-side bundles.
• Rotate credentials after team changes or suspected leakage.
• Classify, minimize, and encrypt sensitive application data.