AI Infrastructure
OpenAI Buys Ona For Persistent Codex Agents [Deep Dive]
Published June 12, 2026 by Dillip Chowdary
OpenAI will acquire Ona to bring secure, persistent cloud execution into Codex for long-running software and knowledge-work agents.
Why Builders Should Care
This signal matters because it changes a live production decision: where agents run, how dependencies install, how security queues are triaged, or how teams compose model infrastructure. The practical question is whether the change can be adopted behind existing controls without creating hidden access paths, brittle CI behavior, or unmanaged cost.
Codex Scale
OpenAI says more than 5 million people use Codex each week, up 400% from earlier this year. The engineering consequence is not just adoption; it changes how teams budget rollout, observability, rollback, and policy enforcement.
Customer Control
Ona's model keeps agent execution inside customer cloud boundaries with scoped credentials, logs, and review paths. The engineering consequence is not just adoption; it changes how teams budget rollout, observability, rollback, and policy enforcement.
Long Horizon
The target workload is work that continues for hours or days after the initiating machine is closed. The engineering consequence is not just adoption; it changes how teams budget rollout, observability, rollback, and policy enforcement.
Implementation Checklist
- Inventory: Map affected repositories, runtimes, clouds, agent workspaces, and data stores.
- Guardrails: Add policy checks for credentials, network reachability, audit logs, and approval gates.
- Rollout: Test the change in a representative staging path before enabling it broadly.
- Telemetry: Capture traces, deployment events, and rollback signals so production behavior is reviewable.