Security
Credentials stay on the server, encrypted, and are never sent back to your browser. Deleting a project deletes them with it.
Credentials
- Database credentials are encrypted at rest with a key that lives outside the database and outside the repository.
- The encryption is bound to the owning account: a record moved between accounts fails to decrypt instead of opening for the wrong one.
- Each migration receives the credential sealed for that run, with a short validity.
- No response, log line or report contains a credential.
- Removing a project removes its stored credentials at the same time.
Isolation
- Each environment has its own database, network and storage.
- On a shared host, customer environments cannot reach each other or the control plane — measured on our homologation host.
- Secrets reach your application as files readable only by it — never in the image, the logs or the environment listing.
What we do not do
- We do not apply automatic corrections to a production system. We report; a person decides.
- We do not issue security attestations and do not claim to replace an audit.
- We do not publish an availability figure before it has been measured over a meaningful period.