Critical
Production site is fully down or core payment/auth flow is broken for all users.
- First response
- ≤ 1 hour, 24/7
- Resolution target
- ≤ 4 hours
Hosting subscriptions come with measurable promises: availability targets, response times by severity, and credits when we don't hit them.
When you open a ticket we tag it with one of four levels. The tag is visible in your portal and drives our internal escalation.
Production site is fully down or core payment/auth flow is broken for all users.
Major feature is broken for many users, or significant degradation in performance.
Non-critical bug, content fix, small enhancement, or anything that isn't blocking users.
Question, suggestion, or scheduled change. Tackled in the next planning cycle.
If your monthly uptime falls below the target, you get a credit on the following invoice:
Credits are automatic — no ticket required, no proof of loss. Posted within 5 business days of month-end.
Planned maintenance happens at most once per calendar month, in a 2-hour window between 02:00 and 05:00 CET, announced at least 5 days in advance.
Maintenance windows don't count against the uptime number above — but we publish a separate status page showing how often we actually need them. The honest number is “rarely”.