System status
What ClientZapp is made of, how we monitor it, and where to look when something is wrong.
An honest note about this page
ClientZapp does not yet publish a live, independently-hosted status dashboard, and we would rather say so than show you a green tick that is drawn by hand. Component-by-component monitoring with a public history is on the list; until it ships, the checks below are the real ones, and incidents are announced by email to workspace Owners and Admins.
Components
- Web & marketing site nginx, US region
- Application (/app) Angular, served from the same origin
- API (/api/v1) Laravel, health check at
/up - Database managed MySQL, TLS required, daily backups
- File storage object storage, private, signed links only
- Scheduled jobs expiry, health recompute, alerts, digest
- Outbound email transactional only
How we watch it
The platform health-checks /up continuously and restarts the container if it stops answering. Application errors and failed scheduled jobs are logged and alerted to us, not to you.
Maintenance
Routine deployments are rolling and cause no downtime. Anything that will interrupt service is announced by email to Owners and Admins at least 48 hours ahead, outside US business hours where we can manage it.
If something looks wrong
Try a hard refresh first — a stale cached application file explains a surprising share of oddities. If it persists, email us with Support in the subject line and what you were doing.
Data safety, briefly
- Daily automated database backups with point-in-time recovery
- Files held in versioned, private object storage
- Every environment served over HTTPS; database connections require TLS
- Secrets held in the platform's encrypted configuration, never in the codebase
The full picture is on the security page.