Developer Tools · head to head
Ona (formerly Gitpod) vs Split

Ona (formerly Gitpod)
Developer Tools
Cloud development environments repositioned as a control plane for software engineering agents
- From
- Free
- Free plan
- Yes

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- Ona (formerly Gitpod) starts at $20/mo; Split prices on request.
- Only Ona (formerly Gitpod) lists ephemeral environments; only Split lists feature flags with targeting.
- Prices and features on this page were last checked on 20 November 2026.
How do Ona (formerly Gitpod) and Split differ?
Ona (formerly Gitpod) and Split differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Ona (formerly Gitpod) and Split actually diverge.
| Attribute | Ona (formerly Gitpod) | Split |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | Per month by compute unit | Quote |
| Free tier | Yes | No |
| Platforms | Web, Linux, macOS, Windows, AWS | Web, API, iOS, Android, Windows |
| Category | Developer Tools | Testing |
Which features does each one have?
They share no listed features; 6 appear only for Ona (formerly Gitpod) and 8 only for Split. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Ona (formerly Gitpod)
- Ephemeral environments
- Agent sessions
- Bring your own cloud
- Devcontainer standard
- Compute unit budgeting
- Enterprise identity
Only in Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform integration
What is each one used for?
The jobs each tool is most often brought in to do.
Ona (formerly Gitpod)
- Giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setupnot Split
- Running several coding agents in parallel against real databases and services instead of on a laptopnot Split
- Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Split
- Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Ona (formerly Gitpod)
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Ona (formerly Gitpod)
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Ona (formerly Gitpod)
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Ona (formerly Gitpod)
Where do Ona (formerly Gitpod) and Split fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Ona (formerly Gitpod)
- Acquisition risk has already materialised: the company closed a sale to OpenAI on 10 August 2026 and now sits inside the Codex team, so nothing public guarantees pricing, continuity or neutrality between model vendors beyond honouring existing commitments
- Two disruptive changes of direction inside a year, from development environments to agent orchestration and then from independence to acquisition, mean the product a browser IDE buyer originally chose no longer exists in that form
- The Gitpod Classic sunset on 15 October 2025 required manual conversion of configuration, hand-moved secrets, self-rescued workspace data and a brand new account, which is the clearest available precedent for how the vendor handles deprecation
- Community self-hosting is finished: the AGPL-3.0 repository is deprecated by its own README, and self-hosted now means a vendor-operated install in your AWS or GCP account, with no Azure, no on-premises and no air-gapped path
- Pricing is difficult to model because it runs on a compute unit currency where subscription credits expire at the end of the month, the mapping from units to actual compute is not published on the pricing page, and Enterprise is quotation only
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do Ona (formerly Gitpod) and Split cost?
Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
Ona (formerly Gitpod)
Free- FreeFree
- Up to 3 parallel environments
- Machines up to 4 vCPU, 16 GB memory and 80 GB disk
- Ona Cloud multi-tenant only
- Core$20/mo
- From 20 US dollars a month, up to 100 team members
- Includes 80 to 2,200 recurring compute units a month depending on tier
- Additional units from 10 US dollars per 40 units
- EnterpriseOn request
- Single-tenant deployment in your own AWS or GCP account
- SAML and OIDC single sign-on
- Dedicated account management and forward deployed engineers
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
Which should you pick?
Choose Ona (formerly Gitpod) if
- You need ephemeral environments.
- You want to start without paying.
- You work on Web, Linux, macOS, Windows, AWS.
- You also want agent sessions.
Choose Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is Ona (formerly Gitpod) or Split better?
- Neither clearly leads. Ona (formerly Gitpod) starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Ona (formerly Gitpod) or Split?
- Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at Free for Ona (formerly Gitpod) and On request for Split.
- Does Ona (formerly Gitpod) or Split run on more platforms?
- Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS. Split runs on Web, API, iOS, Android, Windows.
- Can I use Ona (formerly Gitpod) for free?
- Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Split starts at On request.
- What is Ona (formerly Gitpod) best used for?
- Ona (formerly Gitpod) is most often used for giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setup, running several coding agents in parallel against real databases and services instead of on a laptop, keeping source code off contractor and offshore laptops by moving the whole environment into a controlled account, reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machine. Of those, giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setup and running several coding agents in parallel against real databases and services instead of on a laptop are not what Split is typically brought in for.
- What can Ona (formerly Gitpod) do that Split cannot?
- Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
Answered from the vendors’ own pages
Ona (formerly Gitpod): Is Gitpod still called Gitpod?
No. It rebranded to Ona in September 2025, and gitpod.io now redirects to ona.com. The company was acquired by OpenAI in a deal that closed on 10 August 2026.
Split: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
Ona (formerly Gitpod): Can I still self-host it for free?
No. The AGPL-3.0 self-hosted project is deprecated by its own README. What is offered now is a vendor-operated single-tenant install in your AWS or GCP account on the Enterprise plan.
Split: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
Ona (formerly Gitpod): What happened to Gitpod Classic?
Pay-as-you-go Classic was switched off on 15 October 2025. Migration required converting gitpod.yml to devcontainer.json, moving secrets by hand, downloading workspace data before the cutoff and creating a new account.
Split: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
Ona (formerly Gitpod): What does it cost?
Core starts at 20 US dollars a month and includes a monthly allowance of Ona Compute Units, with more from 10 dollars per 40 units. Subscription credits expire monthly. Enterprise is quoted.
Split: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
More on Ona (formerly Gitpod)
Other head to heads
- Ona (formerly Gitpod) vs Coder
- Ona (formerly Gitpod) vs CodeSandbox
- Ona (formerly Gitpod) vs StackBlitz
- Ona (formerly Gitpod) vs Namespace
- Ona (formerly Gitpod) vs Okteto
- Ona (formerly Gitpod) vs GitHub Codespaces
- Ona (formerly Gitpod) vs Daytona
- Ona (formerly Gitpod) vs Earthly
- Ona (formerly Gitpod) vs Envoy
- Ona (formerly Gitpod) vs Nixpacks
- Ona (formerly Gitpod) vs Spacelift
- Ona (formerly Gitpod) vs Istio
- Ona (formerly Gitpod) vs Warp
- Ona (formerly Gitpod) vs Apache Maven
- Ona (formerly Gitpod) vs Avo
- Ona (formerly Gitpod) vs Deep Code
- Ona (formerly Gitpod) vs Fig
- Ona (formerly Gitpod) vs Frappe
- Ona (formerly Gitpod) vs GrowthBook
- Ona (formerly Gitpod) vs Kameleoon
- Ona (formerly Gitpod) vs Eppo
- Ona (formerly Gitpod) vs Katalon
- Ona (formerly Gitpod) vs Selenium
- Ona (formerly Gitpod) vs Sauce Labs
- Ona (formerly Gitpod) vs TestRail
- Ona (formerly Gitpod) vs Applitools
- Ona (formerly Gitpod) vs CloudBees Smart Tests
- Ona (formerly Gitpod) vs QA Wolf
- Ona (formerly Gitpod) vs CircleCI
- Ona (formerly Gitpod) vs BrowserStack
- Ona (formerly Gitpod) vs BugHerd
- Ona (formerly Gitpod) vs SoapUI
- Ona (formerly Gitpod) vs Playwright
- Ona (formerly Gitpod) vs GitHub Actions
- Ona (formerly Gitpod) vs Cypress
- Ona (formerly Gitpod) vs Appium
- Split vs Coder
- Split vs CodeSandbox
- Split vs StackBlitz
- Split vs Namespace
- Split vs Okteto
- Split vs GitHub Codespaces
- Split vs Daytona
- Split vs Earthly
- Split vs Envoy
- Split vs Nixpacks
- Split vs Spacelift
- Split vs Istio
- Split vs Warp
- Split vs Apache Maven
- Split vs Avo
- Split vs Deep Code
- Split vs Fig
- Split vs Frappe
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
