Status & uptime
Appolar targets 99.9% uptime for the API and Builder. Here is what each component covers, what the target means in practice, and what to expect during an incident.
Status page
A public status page has not shipped yet. Until it does, status inquiries go to support@appolar.com, and merchants affected by an incident are notified by email when it starts and again when it is resolved.
Components
It helps to think of the platform as five components, so during an incident you can tell exactly which part is affected.
| Component | What it covers | Impact if degraded |
|---|---|---|
| Builder | The Shopify admin UI where you design your app: theme settings, block layouts, preset loading | Design work is blocked; your live app is not affected |
| Live Preview | The Expo Web iframe embedded in the builder that shows how your app looks as you edit | The preview panel does not load; the builder and your live app still work normally |
| API | The Appolar backend that delivers config to your app, processes OTA updates, and handles builds | Live app config delivery may be delayed; new OTA versions may not reach users until the API recovers |
| Push Notifications | The delivery pipeline for manual campaigns and automated notifications (cart abandonment, and so on) | Campaigns may be delayed or fail to deliver; your app browsing and cart experience is unaffected |
| App Builds | The EAS-based cloud compile and submission service for generating iOS and Android binaries | New builds are queued but not processed; existing apps on the stores continue to work normally |
Uptime SLA
Appolar targets 99.9% uptime for the API and Builder. At that level, total allowed downtime is under 9 hours per year, or about 43 minutes per month.
App Builds and Push Notifications are best-effort. Build queue depth and notification delivery timing may vary during high-load periods. They are not covered by the 99.9% target.
Planned maintenance windows are announced at least 48 hours in advance by email and do not count against the SLA. Maintenance is scheduled during low-traffic hours (typically Sunday 02:00–05:00 UTC).
During an incident
When an incident is confirmed, affected merchants are notified by email. The update names the affected component, the current status (investigating, identified, monitoring, resolved), and a plain-language description of the impact.
If the API is affected, your live app is designed to degrade gracefully rather than go blank. The app falls back to the last successfully delivered config that was cached on the device. Your app stays open and fully browsable; customers can view products and manage their cart. Config updates (new OTA versions) will not reach users until the API recovers, at which point they are applied automatically on the next app open.
Once an incident is resolved, a follow-up covers what happened, how long it lasted, and what has changed to prevent a recurrence.
Contact
For any suspected incident, or if your store seems affected differently than an incident email describes, write to support@appolar.com with the subject line:
Incident report: your-store.myshopify.com
Include a description of what you are seeing, when it started, and which part of your app or admin is affected. This helps the team triage faster and link your report to an open incident if one exists.