Ona (formerly Gitpod)

Ona is the current name of Gitpod, the product that arguably created the mainstream expectation that a development environment could be a URL. It provisions ephemeral, prebuilt environments from a repository and connects them to VS Code, JetBrains IDEs, or a browser session. The rename came with a shift in emphasis: the environments are now presented as somewhere coding agents work as much as somewhere people do.

Two structural facts matter more than any feature in the product, and both are easy to miss because the vendor's own materials handle them loosely. The first is what "self-hosted" means here. The second is that the company has entered into an agreement to join OpenAI, and that agreement had not closed when this page was written.

Neither is a reason to dismiss the product. Ona is a mature, capable platform with a real answer for teams that need source code to stay inside their own cloud account, and that answer is genuinely rarer than it was two years ago. But both facts change what you are signing up for, and both belong in the first conversation rather than the last.

Environments run on "runners". A runner can be Ona Cloud, which is entirely Ona's infrastructure, or an AWS or GCP runner deployed into your own account and VPC on the Enterprise plan. In the second case source code is cloned and executed inside your network, on compute you pay your cloud provider for directly. The orchestration plane that schedules, authenticates, and manages all of it remains Ona's in both cases, and that is the part with no customer-operated option.

That last row is the one to sit with. Bring-your-own-cloud gives you a network boundary and a data-jurisdiction story, which is real value that a security review will accept. It does not give you an exit. Compare against GitHub Codespaces, which offers regional residency but no runner in your account at all, and against the genuinely self-hostable platforms covered in open source CDEs.

Figures above are from Ona's own pricing page as of July 2026: ona.com/pricing. Enterprise pricing is not published, so no total-cost comparison against a per-hour competitor is possible without entering a sales process.

One further budgeting note for the Enterprise path: the subscription does not include the compute. Runners in your own account bill to your own cloud provider, so the total is the Ona contract plus the AWS or GCP spend the environments generate. Cost analysis works through comparisons that account for both sides.

Take the announcement at face value rather than reading either optimism or doom into it. An agreement to be acquired is not an announced shutdown, acquisitions frequently leave products running for years, and being absorbed into a well-funded buyer's flagship coding effort is not obviously worse for the product than remaining independent. Nobody has said Ona is being discontinued, and this page is not predicting that.

What has genuinely not been addressed is everything a buyer would want addressed. There has been no public statement about the future of the Core plan, the bring-your-own-cloud runner model, the AGPL repository, or support commitments for existing customers after close. A buyer standardizing an engineering organization on this platform is making a three-year decision against a set of unanswered questions, and no amount of product quality compensates for that if the timeline is unforgiving.

Set against the rest of this category the picture is less unusual than it sounds. AWS closed two products to new customers, JetBrains discontinued Space, and Daytona left the category entirely. Ona at least has a well-capitalized acquirer and an operating product. But vendor evaluation and risk management exist precisely for decisions shaped like this one, and skipping them here would be a mistake.