Coder deployment integration

Overview

Ottili Coder and Ottili Cloud are natively part of Ottili ONE: they share one login, one company context (company_id) and one audit trail. That means a service built and validated by Coder can, in principle, reach the same managed cloud infrastructure as the rest of your platform — without separate cloud credentials and without a new identity or permission silo.

This article describes the deployment integration between Ottili Coder and Ottili Cloud*: how results ship today, what cloud runs deliver, and what status the direct deployment handoff has. In short: Coder ships repository-first* today; handing a passing run directly to managed Ottili Cloud infrastructure is planned (PLANNED)* and not yet wired.

Status at a glance

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 the integration works today: repository-first

Every Coder run ends with reviewable artifacts in your Git workflow — whether it ran locally or in the cloud:

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. The flow is described in [Deployments with Ottili Coder](/docs/coder-deployments) and the local/cloud hybrid execution in [Local, cloud, and hybrid runs](/docs/coder-local-cloud-hybrid-runs).

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. The compute capacity that cloud runs use belongs to managed Ottili Cloud (see [Cloud compute](/docs/cloud-compute) and [Instances and lifecycle](/docs/instances-and-lifecycle)).

Planned direct deployment handoff

Handing a passing Coder run directly to managed Ottili Cloud infrastructure is planned (PLANNED)*. It is not yet a public destination and is not advertised as available. When it becomes available, the integration model is clear:

• Same identity*: the run executes in the same company context (company_id); no separate cloud credentials.
• Managed targets*: the deployment lands on managed Ottili Cloud infrastructure — instances, containers and serverless, as those capacities become generally available (today Early Access or planned, see [Ottili Cloud](/docs/ottili-cloud)).
• Approval first*: the deployment is approval-first; every action is enforced through Ottili Core* and Ottili Console* and logged through Ottili Core Audit*.
• Security in the task system*: Ottili Security Check* reviews dependency and secret risk into the same task system as the rest of the run.

Until the direct handoff 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 Coder-side security gates are explained in [Security checks in Coder](/docs/coder-security); the shared account context is described in [Company and team](/docs/company-and-team).

How it fits into the platform

Ottili Cloud and Ottili Coder are natively part of Ottili ONE. Both share a login, a company context and an audit trail with Ottili HQ, Ottili AI, Ottili LD3 and the rest of the platform. The same company boundary and identity serve every surface from your company outward. How the platform layer and product layer separate is described in [Platform layer and product layer](/docs/platform-layer-and-product-layer).

Where to go next

• Set up your [account](/docs/cloud-accounts) and [projects](/docs/cloud-projects) in Ottili Cloud.
• Understand [regions](/docs/cloud-regions), [compute](/docs/cloud-compute) and [networking](/docs/cloud-networking).
• Review [storage](/docs/cloud-storage) and [security](/docs/cloud-security) in Ottili Cloud.
• Read [Deployments with Ottili Coder](/docs/coder-deployments) and [Local, cloud, and hybrid runs](/docs/coder-local-cloud-hybrid-runs).