Reliability, stated honestly
We aim for high availability and communicate clearly when something goes wrong. We also draw a hard line between what we operate toward and what we contractually guarantee — because for procurement, that difference matters.
The one thing to know up front
We target 99.9% uptimeand run on Vercel and Supabase's managed infrastructure. We do not yet offer a contractual SLA with service credits as a standard part of our plans. If your organization requires a formal SLA before purchase, we can discuss one for Enterprise — but we will never dress up an operational target as a binding guarantee.
What's true right now
Our current reliability posture — operational targets and real capabilities, described without spin.
We target 99.9% uptime
99.9% is the availability we design and operate toward. It is an internal reliability target, not a contractual guarantee — standard plans do not include service credits for missed uptime, while credit-backed uptime commitments are negotiable on an Enterprise order. We're honest about that distinction on purpose.
Built on managed cloud infrastructure
The application runs on Vercel (hosting & global CDN) and Supabase (managed Postgres & authentication). We inherit their redundancy, failover, and operational maturity rather than running fragile infrastructure ourselves.
A public status page
We publish current and historical service status so you can check availability yourself at any time — no need to ask us whether something is down.
Incident communication
When there's a service-affecting incident, our approach is to post to the status page and, for significant events, notify affected customers by email with what happened and what we're doing about it.
Check live service status any time on our status page.
Response expectations by plan
These are the response times we aim for by plan. They're targets we work hard to meet — not credit-backed commitments. Enterprise orders can define specific terms in writing.
| Plan | Channel | Response target |
|---|---|---|
| Free & Starter | Community & email support | Best-effort response, typically within a few business days |
| Pro | Email support | We aim to respond within 1–2 business days |
| Growth & Multi-Location | Priority support | We aim to respond within 1 business day |
| Agency & Enterprise | Dedicated success manager | Priority handling with a named contact; specific response commitments can be agreed in your order |
The path to a formal SLA
Here's what we're working toward so a future SLA is something we can stand behind. None of the items below are available today unless explicitly agreed in an Enterprise order.
On our roadmap — not yet in place
- A formal, contractual SLA with defined uptime commitments and service credits — available on request for Enterprise, not yet a standard offering
- Published uptime history and monthly availability reporting
- Documented incident-response and escalation procedures shared with customers
- SOC 2 Type II attestation covering availability controls — targeted, not yet audited
If a contractual SLA is a hard requirement for your purchase, email hello@growmywebsite.com and we'll tell you honestly what we can commit to and on what timeline. See also our security overview and trust overview.
Reporting an issue
If you believe the service is degraded, check the status page first, then reach us at hello@growmywebsite.com. For significant incidents we'll post updates and follow up with affected customers.
This page describes our operational reliability posture and support targets. It is not a contract and does not create a service-level agreement or any guarantee of uptime or response time. Any binding SLA would be a separate written agreement.
Grow with a platform that tells you the truth
Create your free site in minutes — no credit card, and you own and export everything you build.