Overview
Ottili Coder turns an everyday-language mission into a reviewable task list, runs agents, and ships validated results. This article explains how those results are shipped today* and what status direct cloud deployment currently has.
In short: Coder ships repository-first* today — results land as branches, commits, and pull requests in your own Git repository. Direct delivery to Ottili Cloud infrastructure is planned (PLANNED)* and not yet available. Coder never bypasses your release gates.
Status at a glance
| Surface / capability | Maturity | What is true today |
|---|---|---|
| Local runs | Available (AVAILABLE) | Results stay in your local environment. |
| Cloud runs (Ottili Cloud) | Beta (BETA) | The same task queue runs in Ottili Cloud; results return to your repository. |
| Direct cloud deployment from Coder | Planned (PLANNED) | Not yet a public destination; never presented as available. |
How Ottili ONE publicly labels maturity is described in [Understand feature-status labels](/docs/understand-feature-status-labels). The product lifecycle and beta model of Ottili ONE is explained in [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status).
How Coder ships today: repository-first
Every run ends with reviewable artifacts in your Git workflow:
1. Coder creates one or more branches* with the agents' changes.
2. Each task runs through validation loops* (tests, types, security gates) before it counts as done.
3. Coder opens a pull request* in your repository — it does not merge on its own.
4. You review, approve, and merge through your existing CI/CD and deployment pipeline*.
Coder does not replace your pipeline. It prepares validated, reviewable results and leaves approval and delivery to your established processes. Your release gates, approvals, and rollbacks stay with you.
Cloud runs (beta)
With cloud runs* you execute the same task queue in Ottili Cloud* so local machines are not tied up. The maturity is beta (BETA)* — never presented as available (AVAILABLE). Importantly, cloud runs also return their results to your repository; they do not deploy anything to production on their own.
How local, cloud, and hybrid runs work is described in [Local, cloud, and hybrid runs](/docs/coder-local-cloud-hybrid-runs).
Direct cloud deployment: planned
Shipping a run result directly to Ottili Cloud infrastructure is planned (PLANNED)*. It is not yet a public destination and is not advertised as available. Until it is available, deployments go through your repository and your own pipeline.
We deliberately avoid describing planned deployment as if it were shipping today. When direct cloud delivery becomes available, this guide will be updated and the feature status will be shown on the product and status pages.
Security and company context
Every Coder run is company-scoped: it runs inside exactly one company (company_id) and is logged through Ottili Core Audit*. Ottili Security Check* reviews dependency and secret risk into the same task system. Critical actions are enforced through Ottili Console* and Ottili Core*.
The shared account context is described in [Company and team](/docs/company-and-team). Security gates in Coder are explained in [Security checks in Coder](/docs/coder-security).
Related articles
- [Ottili Coder — Overview](/docs/ottili-coder)
- [Local, cloud, and hybrid runs](/docs/coder-local-cloud-hybrid-runs)
- [Git and GitHub integration](/docs/coder-git)
- [Security checks in Coder](/docs/coder-security)
- [Understand feature-status labels](/docs/understand-feature-status-labels)
- [Product lifecycle and feature status](/docs/product-lifecycle-and-feature-status)
Was this article helpful?