The startup probe is optional and off by default on Quave ONE. Every probe that must pass before a new container takes traffic is paid once per rollout wave, and a readiness probe that only answers when the app is really ready already covers the slow start.
A Running app does not prove your snapshot is good. Quave ONE snapshot validation restores the recovery point into temporary storage and inspects it read-only, without replacing the source environment or moving traffic.
Quave ONE has always been passwordless: no password to phish, reuse, or leak. But enterprise security questionnaires still ask "Do you support MFA? Yes / No." Now the answer is an unambiguous yes.
Hundreds of deploys and one question: when did this variable change? The History tab's "Only versions with changes" filter answers who changed the environment, when, and exactly what changed.
Secrets Access is independent of Admin in Quave ONE. An admin without Secrets Access can still run administrative operations, but revealing secrets is denied.
High Availability on Quave ONE starts at three containers or replicas. Instances are spread across different VMs and physical machines in the same region to minimize disruption when a machine fails.
Using Cloudflare in front of Quave ONE? A certificate problem is always surfaced in the Hosts tab, but it never turns off ingress on its own. Traffic keeps flowing while you fix the certificate.
New Quave ONE managed databases on a platform disk get Enable disaster readiness on by default when a destination is available. You uncheck it only if you intentionally want the database unprotected.
