System status
Live platform status.
Operational health of the Riyadh-hosted production environment. The component panel below polls the backend health endpoint live. If you are reading this page during an incident you will see the change here within a minute.
Backend API
NestJS application: auth, EAM modules, AI orchestration
Unknown
checking…
Web app
Next.js front-end serving the in-app SPA + marketing site
Operational
checking…
Database
Managed Postgres in Alibaba Cloud Riyadh with PITR
Unknown
checking…
AI assistant
Anthropic Claude routed through tenant-scoped retrieval
Unknown
checking…
Live probe of /api/health. Polled every 60s, timeout 8s. Secondary components are inferred from the primary probe. Independent per-component checks are on the 2026 roadmap.
Service-level commitments
≥ 72 hours
Scheduled-maintenance notice
Planned maintenance windows are announced to tenant administrators at least 72 hours before they open.
72 hours
Breach-notification window
Per the PDPL Article 22 requirement. Tenant administrators receive a templated notification within the regulatory window.
Availability, recovery-point and recovery-time commitments are agreed per customer in the master services agreement. We do not publish platform-wide figures we do not yet measure in production.
Recent incidents
No customer-impacting incidents in the last 90 days.
When an incident occurs, a public post-mortem is published here within five business days of resolution. Customers on the Enterprise tier are notified directly through the tenant admin contact on file.
Note: this page is an honest summary, not a fully automated status tracker. Live component polling above is real; the incident log above is updated manually within five business days of any customer-impacting event. A fully automated status pipeline with subscriber-driven notifications is on the 2026 roadmap.
Notifications and follow-up
For real-time incident updates as a customer, contact your designated account architect. For procurement reviewers, the trust page documents the underlying controls behind the SLAs on this page.