Few developer tools have changed identity as fast as Gitpod. In under a year it went from a beloved browser-based IDE to an AI agent platform called Ona — and now it's being absorbed into OpenAI. If you've been evaluating cloud development environments, the ground has shifted under your feet. Here's what actually happened, and what it means for your stack.
The rebrand nobody saw coming
For years, Gitpod did one thing very well: it spun up standardized, pre-configured development environments in seconds from any GitHub, GitLab, or Bitbucket repo. A `.gitpod.yml` file defined your dependencies, extensions, and editor settings so every teammate got an identical setup. Onboarding that used to take days took thirty seconds. By 2022 it claimed more than 750,000 developers.
Then, in September 2025, the company rebranded to **Ona** and reframed its entire mission. Instead of "cloud IDE for humans," the pitch became "mission control for your personal team of software engineering agents." The remote environments were still there under the hood, but the headline feature was now autonomous agents that plan, code, review, and deploy inside secure cloud sandboxes — sandboxes that keep running even after you close your laptop.
It was a classic AI-era pivot: take strong infrastructure built for one purpose and repoint it at agentic workflows.
Why OpenAI wanted it
In June 2026, OpenAI announced it is acquiring Ona — legally still Gitpod GmbH — to power long-running Codex agent tasks. The strategic logic is clean. Coding agents are most useful when they can grind on a problem for hours or days, with more compute than a laptop offers, without being cut off the moment a developer logs off. Ona's persistent cloud environments solve exactly that.
The deal reportedly folds Ona's entire team, led by co-founder Johannes Landgraf, into OpenAI's Codex group once it closes. Ona's enterprise agent usage had grown sharply, with clients spanning banks, pharmaceutical companies, and sovereign wealth funds — a customer base that makes the persistent-sandbox technology valuable far beyond a single IDE product.
What this means for developers
If you relied on Gitpod purely as a cloud IDE, this is a moment to reassess. A few practical takeaways:
- **The product's center of gravity has moved.** Ona is now an agent-orchestration platform first and a dev-environment provider second. If your need is simply "standardized environments that launch fast," check whether the new direction still fits — or whether an alternative serves you better.
- **Acquisition uncertainty is real.** Until the OpenAI deal fully closes and the roadmap settles, expect ambiguity about pricing, self-hosting, and long-term support for the classic cloud-environment use case.
- **Strong alternatives exist.** For repo-launched cloud environments, GitHub Codespaces remains the natural choice for GitHub-centric teams. Replit covers browser-based coding and rapid prototyping with its own agent. And for teams that just want consistent local-feeling environments, container-based dev setups are more mature than ever.
The bigger pattern
Ona isn't an isolated story. Across our developer-tools listings, the same gravitational pull keeps showing up: Better Uptime became Better Stack and swallowed logging; Bugsnag became SmartBear's Insight Hub and grew into full observability; Highlight was acquired by LaunchDarkly to power "guarded releases." Tools that started narrow are being rebranded, bundled, and acquired into broader AI-and-observability platforms.
For buyers, the lesson is to anchor decisions on the capability you actually need today, not the brand promise — because the brand may not survive the year. **The tool you adopt for one job may quietly become something else entirely; choose for the workflow, not the logo.**