Isolated.
Each customer’s apps, databases and caches have their own network boundary. Another customer’s workloads cannot reach them, and every request is checked against your organisation and the member making it.
Security
Private workloads, protected connections, and data that never leaves India.
Independent checks
Each result links to the scanner that measured it, so you can check it yourself.
Only passing results measured within the last 26 hours appear here. A scanner grade is not a certification or a guarantee.
Each customer’s apps, databases and caches have their own network boundary. Another customer’s workloads cannot reach them, and every request is checked against your organisation and the member making it.
The console, the API and your public addresses use TLS. Databases and caches accept TLS, and each cache has its own certificate authority. Stored data and backups are encrypted.
Your apps and databases run in our Mumbai data centre, and their backups are copied to Hyderabad, so one regional disaster cannot take both. Your data and its backups never leave India. Data location
Postgres and MySQL are backed up automatically, with recovery to a point in time, and restored only when you ask.
Plexivo Secrets stores keys and passwords encrypted and gives them to your app when it runs. Every reveal is recorded, and a revealed value hides itself after 30 seconds.
Who asked, who approved, what changed and when, in the console under Settings.
Members get roles, sign-in can require a second factor, and CLI sessions expire on their own.
Every change to your infrastructure waits for an approved plan and price.
Keep a database public, open it only to trusted IP addresses, or make it private and reach it through the Plexivo CLI. App Runner services can be private and callable only by your own services. Managed caches run in an extra sandbox and cannot open outbound connections.
Tell us what you found and how to reproduce it at security@plexivo.io. Please do not include passwords, secret keys or customer data.