High availability

The platform is designed to keep running through everyday failures without manual intervention.

Self-healing

Thanks to orchestration on Kubernetes, every component is continuously monitored. If one stops responding or fails:

The platform restarts or replaces it automatically.
Traffic is redirected to healthy instances in the meantime.

No operator needs to be on standby to recover from an isolated component failure.

Scaling

The platform scales your application's resources based on load, within agreed limits, to maintain performance during usage peaks.

Zero-downtime deployments

Changes and updates are applied via progressive replacement: new versions roll out gradually while previous ones keep serving traffic, so there's no perceptible cutover. See Deployments and changes.

Beyond everyday failures

For serious scenarios (not a single component, but an entire environment), the response is disaster recovery based on separate backups and reproducible rebuilding.

Pending validation

The availability commitments (uptime percentage) applicable to your service are set out in your service contract.