OpenAI announced plans to acquire Ona, the cloud execution platform formerly known as Gitpod, to solve the biggest barrier keeping enterprises from trusting AI coding agents: the inability to run long-running tasks without a developer present. The acquisition, announced on June 11, 2026, directly addresses what industry experts call the "session-boundary problem" that has stalled enterprise adoption of AI coding tools.

Why Do Enterprises Reject AI Coding Agents Despite Impressive Demos?

Codex has grown to 5 million weekly active users, up 400% since January 2026, but enterprise adoption has hit a wall. The problem is not the model's intelligence. It is the runtime environment. Close your laptop, and the agent dies. A five-minute code review survives a session. A six-hour dependency migration does not. This architectural limitation has made enterprises unwilling to hand agents anything time-consuming or mission-critical.

Enterprise developers have been stalling on Codex for months, not because they doubt the model, but because they cannot allow an AI agent to touch production data on OpenAI's servers. Regulated industries, in particular, need assurance that sensitive code and data stay within their own infrastructure. Ona changes that equation by letting agents run inside the customer's own virtual private cloud (VPC), with full audit trails, role-based access control, and kernel-level enforcement for every action the agent takes.

How Does Ona Actually Solve the Session-Boundary Problem?

Ona, which rebranded from Gitpod in September 2025 and rebuilt entirely around AI agents, solves the persistence problem with three architectural layers. First, sandboxed Firecracker microVM environments survive disconnects through automatic 10-minute checkpointing, turning tasks into durable jobs rather than sessions. Second, background agent workflows can be triggered by tickets, webhooks, or CI/CD pipeline events, with no developer present required. Third, kernel-level enforcement logs and audits every action: file access, network connections, memory usage, and execution details.

"Agents need more than intelligence; they need a trusted workspace," stated the Ona CEO.

Ona CEO

This is not marketing copy. It is a genuine architectural observation about why impressive demos consistently fail to translate into production deployment. With Ona's infrastructure, agents can work overnight on structured tasks with clear success conditions, then present results in the morning.

What Makes Customer-Controlled Execution the Real Story?

The persistence story is compelling, but the governance story is what actually moves enterprise procurement. Ona's architecture lets agents run inside the customer's own VPC, with OpenAI providing the model intelligence and orchestration while the customer owns the runtime. This separation is the sentence regulated industries needed to hear before opening production systems to an AI agent.

In practice, this means role-based access control (RBAC), single sign-on (SSO) and OpenID Connect (OIDC) integration with short-lived tokens rather than static credentials, and full audit trails for SOC 2 compliance. Near-term use cases include CVE remediation, dependency upgrades, test-failure triage, and documentation updates. However, one important caveat remains: OpenAI's intelligence layer is still processing requests. The data stays in the customer VPC, but the reasoning does not. For most enterprise teams, that is an acceptable tradeoff. For the most sensitive regulated environments, that conversation remains open.

How Does This Acquisition Reshape the AI Coding Agent Market?

With Ona, Codex now has a third path to enterprise trust that neither Claude Code nor GitHub Copilot currently offers. Claude Code's strongest enterprise argument has been local execution, where agents run on the developer's machine and data never leaves the building. GitHub Copilot leans on Microsoft's cloud trust relationships built over decades. Codex now offers cloud execution, but in your cloud. That meaningfully narrows the gap without requiring enterprises to trust OpenAI as a cloud provider.

Independent sandbox providers like E2B, Daytona, and Modal now face a first-party player with tight model-to-runtime integration. Their genuine advantage remains model-agnosticism: they work with Claude, GPT, and open-weight models alike. According to a 2026 sandbox comparison from Northflank, Daytona raised $4 million in February on exactly this compliance-first positioning. If you are building a multi-vendor AI agent infrastructure, neutral sandboxes remain the more portable bet. If you are all-in on Codex, Ona's integration depth is the obvious choice.

Steps to Evaluate Codex and Ona for Your Organization

• Clarify Data Boundaries: Ask OpenAI explicitly where model inference happens relative to your VPC boundary. Confirm that production data stays in your infrastructure and understand exactly what the intelligence layer processes.
• Review Contract Terms: Get clear answers about what happens to Ona's independent enterprise contracts after the acquisition closes in Q4 2026. Pricing and support terms may change, and you need to understand the implications before committing.
• Assess Model Flexibility: Determine whether Ona environments will remain model-agnostic after the deal closes or become Codex-exclusive infrastructure. This affects your ability to switch models or use multiple vendors in the future.
• Evaluate Multi-Vendor Strategy: Consider how tight integration with Codex and Ona affects your broader AI agent strategy. Tight integration is only valuable if you are committed to staying in the OpenAI ecosystem long-term.

The coding agent race has moved past "whose model is better." The new competition is about who owns the execution stack, the orchestration layer, and the enterprise trust relationship. OpenAI just answered all three for its ecosystem, at the cost of locking customers further into it. The acquisition is expected to close in Q4 2026, pending regulatory approval. Until then, Ona and OpenAI remain independent, but the integration will happen quickly once the deal closes.

For teams considering this move, the timing matters. Before committing your agent infrastructure to Codex and Ona, get clear answers to the questions outlined above. The technology solves a real problem that has blocked enterprise adoption. But the business terms and long-term flexibility implications deserve careful scrutiny before you sign anything new.