Overview
An instance* in Ottili Cloud is a virtualized compute unit — a virtual machine that runs your workloads, services and Ottili Coder deployments. Instances run on the OpenStack foundation and are managed through the Ottili-owned control plane, dashboard and APIs — in the same company context as the rest of Ottili ONE.
This article describes the lifecycle of an instance*: from provisioning through operation, monitoring and backup to stopping and retirement. Every status claim follows the canonical product-status registry (config/product_truth) — nothing is invented.
What an instance is
An instance is a virtual machine you create and manage through the Ottili Cloud control plane. Typical characteristics:
- Compute*: on-demand compute capacity for hosting applications, agents and services.
- Block storage*: one or more volumes are attached to the instance.
- Networking*: the instance joins a virtual network and becomes reachable through your domains.
- One company context*: every instance belongs to your company (
company_id) — isolated like all Ottili ONE data.
The lifecycle of an instance
The lifecycle follows the real Ottili Cloud capabilities. Each phase is bound to a capability whose maturity status comes from the registry.
1. Provisioning
You create an instance from the dashboard or the API: choose a size (plan/quotas), attach a block volume and join the virtual network. Compute is an Available* capability.
2. Configure (network & domains)
Once the instance is running, you attach virtual networking, load balancers and firewall rules, and point your domains at it. Networking and domains are Available*.
3. Running
The instance runs your workloads. From the control plane you start, stop and scale it. Ottili Coder can target a managed cloud runner for long-running or compute-intensive work.
4. Monitoring
Health metrics and monitoring alerts are shown in the same dashboard. Monitoring is Available*.
5. Backups
You schedule automated snapshots of volumes and instances. Backups are Available*.
6. Update
You apply operating-system and application updates inside the instance; Ottili Cloud manages the underlying infrastructure.
7. Stop and terminate
You can stop an instance and start it again later, or delete it permanently (terminate) — including its attached volumes unless they are kept separately. Consumption is reflected through Usage Billing* (available / Available).
Availability and status
Ottili Cloud as a whole is in Early Access* (status component ottili-cloud-early-access): available through an early-access program to a limited group. The individual cloud capabilities that carry the instance lifecycle are attested in the registry as follows:
- Compute / instances* — available (Available)
- Storage / volumes* — available (Available)
- Networking* — available (Available)
- Domains* — available (Available)
- Backups / snapshots* — available (Available)
- Monitoring* — available (Available)
- Usage billing* — available (Available)
- Ottili Coder deployment handoff* — Early Access (not yet wired as live)
How Ottili ONE publicly labels maturity is described in [Understand feature-status labels](/docs/understand-feature-status-labels). The canonical status vocabulary is: Available*, Early Access*, Beta*, Planned*, Concept* — an instance running on available capabilities is usable today, while the Ottili Cloud product as a whole remains in Early Access.
Instances in the context of Ottili ONE
Instances are native to Ottili ONE: they share one login, one company context and one audit trail with Ottili HQ, Ottili AI, Ottili LD3 and Ottili Coder. The Coder deployment integration — where a passing Coder run hands off directly to managed Ottili Cloud infrastructure — is in Early Access* today; the page shows the honest early-access status rather than a not-yet-wired live handoff.
For the overview, see [Ottili Cloud](/docs/ottili-cloud), for compute see [Cloud compute](/docs/cloud-compute) and for regions see [Cloud regions](/docs/cloud-regions).
Was this article helpful?