Service Level Agreement

1. Where we are

AppMecca is in invite-only early access, and we do not offer a contractual SLA yet. There is no uptime percentage you can hold us to, no service-credit scheme, and no guaranteed response times. There is also no billing during early access, so there would be nothing for a credit to apply against.

We would rather tell you that plainly than publish a contract we are not yet staffed to honour. A formal SLA is a promise about a team's availability as much as a platform's, and ours is small. Publishing one before we can stand behind it would make this page worth less than nothing to you.

2. What we do commit to

These are engineering and operational practices we run today, not contractual guarantees:

• Redundant infrastructure. Production environments run across three AWS availability zones, with the database configured for automatic failover.
• A failed deploy never takes your app down. For container apps, the new version starts and has to pass a health check alongside the version already running before any traffic moves to it — if it never passes, it is discarded and your previous version carries on serving. Static sites cut over atomically, so a publish that fails leaves the previous build in place.
• Health checks about once a minute. Every web-facing service is probed regularly, including static sites served from our CDN. A container that crashes is restarted automatically. One that is running but failing its checks is taken out of the load balancer and raised to us — we would rather look at it than restart it blindly.
• A database backup before every deploy. If your app has a managed database, it is dumped automatically before each deployment and kept for 14 days, so your data can be recovered if a deploy goes wrong. For a restore you can run yourself, take an on-demand backup with mecca app backup — that produces a checksummed bundle covering your database and every mounted drive.
• We will tell you. If something goes wrong that affects your applications, you will hear it from us — not discover it. During early access that is a person contacting you directly, not an automated status feed.

Background services — workers, scheduled jobs — have no front door to probe, so they are not covered by the health checks above. We monitor the platform they run on, not the work they do.

3. What we do not promise yet

Being explicit about the gaps matters more than the list above:

• No guaranteed uptime percentage, and no service credits.
• No guaranteed incident response or resolution times. We are not running a 24/7 on-call rotation.
• No public status page. Incident communication during early access is by email.
• No committed maintenance windows. We will give you notice of anything disruptive, but not on a fixed schedule.

4. Your data

None of the above changes how we treat your data. Backups run as described for every app, your data is exportable at any time, and if you leave we will help you take it with you. Data handling is covered in our Privacy Policy.

5. When this page changes

A full SLA — with an uptime commitment, a measurement method, service credits and response-time targets — will be published when AppMecca reaches general availability and paid plans begin. We will give existing customers at least 30 days' notice before any billing starts, and the SLA will be in place before you are charged, not after.

If you need a contractual uptime commitment before then, talk to us. We would rather scope something we can actually meet with you than have you assume one from a template.

6. Contact

For questions about availability, incidents, or what we can commit to for your workload:

• Email: info@appmecca.com