Trust Centre

Availability

Isometric diagram of a flowing primary housing and a charged standby housing joined by a weighted transfer bridge, with a monitoring loop returning from downstream and a replacement module sliding in on rails while the line keeps running — Deployments replace instances rather than stopping the line, and the environment is declared in source so it can be rebuilt from the repository rather than from memory. What you will not find on this page is an uptime percentage — that belongs in a signed agreement, not in marketing.

How it is deployed

The application runs as containers behind a managed ingress, with health probes and rolling revisions, so a deployment replaces instances rather than taking the service down. Database backups are managed by the platform with point-in-time restore. Infrastructure is declared in source, so an environment can be rebuilt from the repository rather than from memory.

What this page does not claim

There is no uptime percentage here, and the omission is deliberate. A number like that is only meaningful against a defined measurement window, a definition of downtime and a published remedy — that is a service level agreement, and it belongs in a signed contract rather than on a marketing page. Ask us and you will get the real operating history and the SLA we are prepared to commit to.

Scheduled work

Routine deployments are online and require no window. Where a change does require one, customers under an executed agreement are notified in advance on the notice period that agreement specifies.

Security Data handling Subprocessors Incident response Compliance Data Processing Agreement AI disclosures