STATUS
System status & incident posture
A dedicated status page with real-time component health is on the roadmap. Until it ships, here is exactly what we monitor and how incidents are handled today.
Today's posture
- Hosting: Cloudflare-fronted, single-region origin. Marketing pages and microtools are served from prerendered/cached assets at the edge.
- SLA: 99.95% uptime SLA on Enterprise contracts; best-effort on self-serve plans. See pricing for the breakdown.
- Monitoring: structured logs include
tenantId,userId,projectIdandrequestId; per-tenant metrics on rate-limited endpoints, error rates and storage usage.
How incidents are handled
- Triage within 1 hour of detection.
- Customer notification per contractual SLA (email for Enterprise; banner in-app for self-serve).
- Slack-bridged incident channel for paid tenants.
- Public post-mortems for any incident with customer-visible impact.
Subscribe to updates
Until the live status page ships, the most reliable channels are:
- Email [email protected] asking to be added to the incident notification list.
- Watch the changelog — every shipped fix lands there.
- GitHub project page for engineering visibility.
Reporting an issue
Security:[email protected]. See also /.well-known/security.txt.
Outage: [email protected] with the subject prefix [outage] and include the time window, affected workspace slug and a screenshot if visible.