Overview
Availability describes how reliably and reachably an Ottili Cloud service or region stays up — whether compute, storage, networking and the control plane are operational when you or your users need them. Availability is built from several layers: the uptime of each component, redundancy and failover, regional placement, and honest status reporting.
Ottili Cloud is today in Early Access* (preview, not generally available). This page therefore clearly separates what is live and reachable, what runs under Early Access, and what is still in development or planned — it does not invent uptime percentages or SLA commitments that are not yet published.
What availability means in Ottili Cloud
Availability is not a single switch but the interplay of:
- Uptime*: the share of time a component responds.
- Redundancy*: whether critical parts exist more than once, so a failure does not immediately end the service.
- Failover*: whether the service moves to a healthy instance when one component fails.
- Status reporting*: whether you can clearly see the current state (operational, degraded, down) and any ongoing incidents.
These layers depend on the maturity of each cloud area. Where an area is not yet live, this page says so instead of describing a guarantee that does not yet exist.
Status levels
Ottili Cloud uses the canonical product-status vocabulary. Every cloud capability carries one of these levels:
- Live / Generally available (GA)*: fully supported and reachable for everyone (status:
AVAILABLE). - Early Access*: reachable through a limited early-access program, preview (status:
EARLY_ACCESS). - Beta*: publicly available in a pre-release state, may still change (status:
BETA). - In development*: in progress, not yet orderable.
- Planned*: announced but not yet available.
- Concept*: early idea, not yet announced or available.
Regions and availability
A [region](/docs/cloud-regions) is a named geographic area where Ottili Cloud runs infrastructure. Regions affect availability directly: a region closer to your users reduces latency, and multiple regions let you run workloads distributed by location.
Regions are being established as part of the Ottili Cloud Early Access build-out. Specific region names and their live status are published on the product and status pages rather than invented here. Until a region is live, this documentation does not present it as orderable.
Redundancy and resilience
During Early Access, the reachable availability focuses on compute, which is provisioned through the early-access program. Multi-region redundancy, component-level failover and a contractual SLA with fixed uptime targets are part of the platform build-out and not yet live as self-service.
We do not publish uptime percentages or SLA numbers that are not yet measured and contractually committed. Once those targets are settled, they appear on the status and product pages — not first in this documentation.
Status page and incident transparency
The operational status of Ottili Cloud is published on the shared [status page](/docs/cloud-status), together with the rest of the platform. There you see whether cloud components are operational, degraded or down, plus active and past incidents. During Early Access, individual cloud components may show limited status granularity while the service matures.
Availability today (honesty matrix)
- Ottili Cloud (product)*: Early Access — preview, not GA.
- Compute*: Early Access — reachable through the program today.
- Regions*: In development — being established as part of the Early Access build-out; names + live status on product/status pages.
- Storage, networking, databases, containers, serverless*: Planned — in development, not yet orderable.
- Multi-region redundancy, component-level failover*: Planned — in development.
- Contractual SLA / uptime targets*: Planned — not yet published.
Related
- Learn how [regions](/docs/cloud-regions) group latency, residency and isolation.
- See where to view the current [cloud status](/docs/cloud-status).
- Understand how [networking](/docs/cloud-networking) connects resources.
- Read the product overview for [Ottili Cloud](/docs/ottili-cloud).
- Check how [compute](/docs/cloud-compute) is placed in a region.
- Understand the [security](/docs/cloud-security) of the cloud infrastructure.
Was this article helpful?