Ottili Coder

Local, cloud, and hybrid execution

Where Ottili Coder executes work, what each runner is for, and their current maturity — local available, cloud and hybrid in beta.

Overview

Ottili Coder runs the same task queue in three execution modes: local, cloud, and hybrid. Only the runner changes — orchestration, logs, validation loops, and the audit trail are identical in every mode. That means a run looks the same regardless of runner, and you can switch modes without losing the mission, the queue, or the audit history.

The maturity levels are deliberately different: local execution is available (AVAILABLE), cloud and hybrid execution are in beta (BETA). Shipping a run result directly to Ottili Cloud (deployment) is planned (PLANNED). These statuses follow the Ottili Coder feature-status registry and the public Coder product page.

Local execution (available)

Code and agents run on your own machine — through the Coder CLI or the desktop app. Your source stays in your environment; only the run metadata needed for identity, credits, and audit leaves it.

Use local runs for:

everyday work and fast iteration,
anything that must stay on your infrastructure for privacy or compliance reasons,
workloads you do not want in a shared cloud environment.

Cloud execution (Beta)

Ottili provisions a managed remote runner in Ottili Cloud*. Your repository and task context are sent to a cloud workspace, and results return to the same run record. Cloud runs are in beta:

capacity is limited,
they are credit-metered,
behavior may change,
they are not intended for production secrets without approval.

Hybrid execution (Beta)

Plan and run lightweight tasks locally, then hand long-running or compute-heavy work to a cloud runner — on the same run, with one coherent queue. Hybrid builds on cloud runs, so it carries the same beta maturity: everything that applies to cloud runs (limited capacity, credit metering, changeability) also applies to the hybrid-offloaded portion.

Choosing a runner

Use local* for speed, privacy, or work that must stay on your machine.
Use cloud* for long-running or compute-heavy work you do not want on your laptop.
Use hybrid* to keep planning local while offloading heavy execution.

Status and availability

Execution	Status	What it means
Local	Available (AVAILABLE)	Runs on your infrastructure; source never leaves your environment.
Cloud	Beta (BETA)	Limited capacity, credit-metered, subject to change, not for production secrets without approval.
Hybrid	Beta (BETA)	Builds on cloud runs; carries the same beta maturity.
Cloud deployment	Planned (PLANNED)	Shipping a run result directly to Ottili Cloud is planned; not yet a public destination.

Current Coder service status (Web, Cloud Runtime, CLI Services, GitHub Integration) is published on the public status page. How Ottili ONE labels maturity publicly is described in [Understanding feature-status labels](/docs/understand-feature-status-labels).