Who is behind OKStatus, and what happens if something stops
OKStatus is run by a very small team. We don't hide it: here is what protects your monitoring and your data despite that.
The publisher
ClearCloud, Dijon (France), SIREN 539 932 731. A very small team: the managing director designs, builds and operates the service; contractors work under a confidentiality agreement. The whole infrastructure is described in Git repositories, so a competent operator can rebuild it.
Your data stays retrievable
Export your data as JSON at any time, on every plan. On Max and Enterprise, the REST API and the Terraform provider also retrieve the configuration (import of existing resources). When the contract ends, your data is deleted or returned within 30 days.
If we stop the service
90 days' notice by email to every organisation owner. During the notice period the service keeps running and export stays open. Amounts paid in advance for the period after the shutdown are refunded pro rata. It is written in the terms of service (section 9.3).
If the infrastructure fails
The database is backed up continuously to a provider other than the host, with 30 days of retention. Targets: at most 15 minutes of lost data, recovery within 4 hours. Latest restore test on 28 September 2026: full database restored in 2 min 22 s.
If OKStatus itself is down
Our status page, status.okstatus.eu, runs on another host, in another country, with its own probes. It stays readable when the platform is not, and publishes measured availability over 24 hours, 7 days and 30 days.
What we don't have yet
No certification (SOC 2, ISO 27001) and no third-party penetration test yet. Email support only, with no on-call service. We would rather write it here than let you find out.
Ask a question, get the security pack
CAIQ-Lite and SIG-Lite questionnaires, security policies, incident-response plan, signed copy of the DPA: on request, whatever your plan.