Security overview

Plexivo is built to keep each customer’s work apart and every action accountable. This page gathers what Plexivo does for you and the controls you can turn on. For the reasoning behind each layer, see Security model.

What Plexivo does for you#

• Encrypted connections. The console and the API use HTTPS. Your apps’ public addresses, and custom domains you add, get TLS certificates that Plexivo manages. Connections to your databases and caches from the internet use TLS, and for Plexivo Postgres you can download a CA certificate so your client verifies the server.
• Isolation. Each customer’s resources sit behind their own network boundary. Every request is checked against your organisation, and a key or kubeconfig reaches only the organisation or namespace it was made for.
• Patching. Plexivo keeps your database and cache engines patched, in the maintenance window you choose. See Maintenance and versions.
• Secrets kept secret. Plexivo Secrets stores values encrypted, and lists show fingerprints, never values. See Plexivo Secrets.
• Data in India. Your apps and databases run in Mumbai; backups are copied to Hyderabad. Your data and its backups stay in India. See Data residency.
• A permanent record. Every change, and every access from outside your team, is in an audit log nobody can edit.

Your security checklist#

1. Turn on two-step verification. In Settings → Security, add an authenticator app and keep your recovery codes safe. It is optional, and we recommend it for every owner and admin.
2. Give the least access. Make builders admins and everyone else members. Grant billing with a policy, not extra owners. See Teams and roles.
3. Set session limits. Owners choose how soon idle console sessions end and how long a sign-in lasts. Owners and admins choose how long CLI sessions last. See Sessions.
4. Scope every key. Give each API key only the permissions it needs, an expiry and a spend limit. Use service accounts for pipelines. See API keys.
5. Keep databases private. Make a database Private to its project, or, on plans that include them, limit it to Trusted networks. Reach a private database from your laptop through the secure tunnel.
6. Decide on support access. Approve requests to reveal secrets or data only for as long as a ticket needs. See Support and agency access.
7. Get alerts. Add an alert channel so you hear when a Plexivo Postgres database stops serving or a certificate needs attention. See Alerts.

Security reviews#

For a vendor review, start with the Security page and Security model. The Privacy page explains how personal data is handled and who helps us run Plexivo. For a questionnaire, contact us.

Report a security issue#

Write to security@plexivo.io with what you found and how to reproduce it. Please do not include passwords, secret keys or customer data.