How Twenty runs its status page on openstatus

Open-source CRM needs an open-source status page. Openstatus took us minutes to set up — and it covers everything our customers actually depend on.

At Twenty, we're building the #1 open-source CRM, used by everyone from solo founders to public institutions. When our cloud is off, people need to know — and they need to trust what they're reading.

We needed a status page that matched how we ship the rest of Twenty: open source, developer-first, no vendor lock-in. Openstatus was the obvious fit. Same values, same European energy, pricing that doesn't punish you for adding monitors as you grow.

Setup took minutes. We pointed twenty-status.com at openstatus and added monitors for our marketing site, app, and docs — plus dedicated monitors for our GraphQL and REST APIs. From day one, the page reflects what customers actually depend on.

Monitoring runs from 28 regions worldwide, which matters when your users are in Paris, São Paulo, and Tokyo. If app.twenty.com is slow from Singapore, we hear about it before our Singapore customers do.

The unexpected win: compliance. Every status report is timestamped and documented automatically, which makes the incident-communication conversation a non-issue when enterprise prospects run their security reviews.