Service Level Objectives

This page states the service levels we aim for, honestly. It is not a credits contract: we do not currently publish a contractual uptime percentage, and no service credits are offered in the current version. If and when we commit to contractual figures, they will appear here explicitly rather than being implied.

We aim for the platform to be available 24/7. It runs on Vercel (application), Railway (database) and Cloudflare (storage and network), so those providers’ own availability underpins ours — we are not going to quote you a number that is really theirs.

When something breaks, incidents are acknowledged and worked with priority by severity:

• P1 — order-taking down for a live restaurant: worked immediately, ahead of everything else.
• P2 — a module degraded (bookings, messaging, dashboard) with ordering still up: worked with urgency behind any P1.
• P3 — cosmetic or non-blocking issues: scheduled into normal work.

Support is by email (join@quantumaiwebapps.com), and we aim to respond within one business day. Founding members get direct-line priority — that is part of what the founding seat buys.

Most maintenance is invisible and needs no window. Where maintenance will be disruptive, we announce it to affected restaurants in advance.

During an incident, status is communicated by email to affected restaurants. There is currently no public status page — if we add one, this page will say so.

Questions about these objectives: join@quantumaiwebapps.com.