Published objectives
The targets below describe service objectives. They are not measured availability or a substitute for your service agreement. Real-time public status page: Planned This page is maintained by hand.
Last updated: 2026-09-10 (manual; wording review)
| Service |
Uptime target |
Scope |
| Store API |
99.95% |
Publish, download and license issuance |
| Store Web |
99.95% |
Browse and install |
| Identity (managed cloud) |
99.95% |
OAuth2 / OIDC token issuance |
| License signing service |
99.99% |
License issuance and signature verification |
| Setup activation endpoint |
99.9% |
Instance activation and key refresh |
| Update delivery |
99.9% |
Automatic update checks (configurable cadence) |
| Marketing site (createrun.ai) |
Not published |
No uptime target for the marketing site |
These figures are targets, not live measurements. Historical uptime reporting begins with the real-time public status page; until then, any customer-impacting incident is communicated directly and documented on this page.
No incident history is published on this page. This does not establish that no incidents have occurred.
Our incident process targets a written post-mortem within 5 business days. Contractual response and reporting obligations are defined in the applicable service agreement. To report a suspected incident or a security issue, email security@createrun.com.
What counts as an incident
- Major: Customer-impacting outage > 5 minutes on a critical service.
- Minor: Degraded performance, retries, partial outage on a non-critical path.
- Maintenance: Pre-announced window with no customer-impacting effect (announced 7 days in advance).
On-premises instances expose health endpoints suitable for the monitoring tools you already run. Agree the logging, metrics, tracing and alerting configuration for your deployment during setup. The available health endpoints depend on the installed services.
Observability integration details 