Softwr

Testing · head to head

Eppo vs Ona (formerly Gitpod)

Eppo logo

Eppo

Testing

Warehouse-native experimentation and feature flagging, now sold as Datadog Experiments

From
On request
Free plan
No
Ona (formerly Gitpod) logo

Ona (formerly Gitpod)

Developer Tools

Cloud development environments repositioned as a control plane for software engineering agents

From
Free
Free plan
Yes

The short version

  • Ona (formerly Gitpod) starts at $20/mo; Eppo prices on request.
  • Only Eppo lists warehouse-native analysis; only Ona (formerly Gitpod) lists ephemeral environments.
  • Prices and features on this page were last checked on 20 November 2026.

How do Eppo and Ona (formerly Gitpod) differ?

Eppo and Ona (formerly Gitpod) differ on starting price (On request against Free), pricing model and free tier (No against Yes). Only the attributes on which Eppo and Ona (formerly Gitpod) actually diverge.

Attributes where Eppo and Ona (formerly Gitpod) differ
AttributeEppoOna (formerly Gitpod)
Starting priceOn requestFree
Pricing modelQuotePer month by compute unit
Free tierNoYes
PlatformsWebWeb, Linux, macOS, Windows, AWS
CategoryTestingDeveloper Tools

Not yet recorded: founded for Ona (formerly Gitpod).

Which features does each one have?

They share no listed features; 8 appear only for Eppo and 6 only for Ona (formerly Gitpod). 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 Eppo

  • Warehouse-native analysis
  • Sequential testing
  • CUPED variance reduction
  • Feature flagging
  • Metric governance
  • Contextual bandits
  • Experiment scorecards
  • Heterogeneous effect analysis

Only in Ona (formerly Gitpod)

  • Ephemeral environments
  • Agent sessions
  • Bring your own cloud
  • Devcontainer standard
  • Compute unit budgeting
  • Enterprise identity

What is each one used for?

The jobs each tool is most often brought in to do.

Eppo

  • A company whose experiment results have repeatedly disagreed with the analytics team’s own numbers because the two systems define revenue differentlynot Ona (formerly Gitpod)
  • A product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of monthsnot Ona (formerly Gitpod)
  • A team that must keep user-level event data inside its own warehouse for regulatory reasons and cannot ship it to a third-party analytics vendornot Ona (formerly Gitpod)
  • An existing Datadog customer consolidating product analytics, feature flags and experimentation onto one vendor agreementnot Ona (formerly Gitpod)

Ona (formerly Gitpod)

  • Giving a large engineering team identical, disposable environments so onboarding is a link rather than a two day setupnot Eppo
  • Running several coding agents in parallel against real databases and services instead of on a laptopnot Eppo
  • Keeping source code off contractor and offshore laptops by moving the whole environment into a controlled accountnot Eppo
  • Reproducing a hard-to-configure toolchain for a short-lived project without polluting anyone machinenot Eppo

Where do Eppo and Ona (formerly Gitpod) fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Eppo

  • Datadog acquired Eppo in May 2025 and is folding it into Datadog Experiments, so you are now buying a component of an observability suite rather than an independent product, and roadmap priorities will follow Datadog’s bundle strategy
  • No pricing is published anywhere, before or after the acquisition; the site offers only a demo request, so cost cannot be estimated without a sales process and is likely to be quoted alongside a wider Datadog contract
  • Because analysis runs in your warehouse, Eppo shifts compute cost onto your Snowflake or BigQuery bill; a large experiment programme with frequent recomputation raises a line item that does not appear in the Eppo quote at all
  • Results are only as fresh as the pipeline feeding the warehouse, so teams used to near-real-time dashboards from an event-based tool will wait hours for updated numbers, which slows down the fast iteration loops some product teams rely on
  • It assumes a mature data stack with a warehouse, defined metrics and analysts who can maintain them; an organisation without that has to build the data foundation first, which makes the real adoption cost far larger than the licence

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

How much do Eppo and Ona (formerly Gitpod) cost?

Eppo is priced on request; Ona (formerly Gitpod) has a free plan, with paid plans from $20/mo. Plan by plan below, from each vendor's own pricing page.

Eppo

On request
  • Eppo, now Datadog ExperimentsOn request
    • Warehouse-native experiment analysis
    • Feature flagging and assignment
    • Sequential testing and CUPED variance reduction

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

Which should you pick?

Choose Eppo if

  • You need warehouse-native analysis.
  • You also want sequential testing.

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.

Questions people ask

Is Eppo or Ona (formerly Gitpod) better?
Neither clearly leads. Eppo starts at On request and Ona (formerly Gitpod) at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Eppo or Ona (formerly Gitpod)?
Ona (formerly Gitpod) has a free tier; the other does not. Paid plans start at On request for Eppo and Free for Ona (formerly Gitpod).
Does Eppo or Ona (formerly Gitpod) run on more platforms?
Eppo runs on Web. Ona (formerly Gitpod) runs on Web, Linux, macOS, Windows, AWS.
Can I use Ona (formerly Gitpod) for free?
Yes. Ona (formerly Gitpod) has a free tier, so you can try it without paying. Eppo starts at On request.
What is Eppo best used for?
Eppo is most often used for a company whose experiment results have repeatedly disagreed with the analytics team’s own numbers because the two systems define revenue differently, a product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of months, a team that must keep user-level event data inside its own warehouse for regulatory reasons and cannot ship it to a third-party analytics vendor, an existing datadog customer consolidating product analytics, feature flags and experimentation onto one vendor agreement. Of those, a company whose experiment results have repeatedly disagreed with the analytics team’s own numbers because the two systems define revenue differently and a product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of months are not what Ona (formerly Gitpod) is typically brought in for.
What can Eppo do that Ona (formerly Gitpod) cannot?
Eppo covers Warehouse-native analysis, Sequential testing, CUPED variance reduction, Feature flagging. Ona (formerly Gitpod) covers Ephemeral environments, Agent sessions, Bring your own cloud, Devcontainer standard.

Answered from the vendors’ own pages

Eppo: Is Eppo still a separate product?

It is still sold and supported, but Datadog acquired it in May 2025 and it is branded as Datadog Experiments. Buy it expecting a Datadog product roadmap.

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.

Eppo: What does it cost?

Nothing is published. There is no pricing page, only a demo request, and pricing is now likely bundled into a Datadog agreement.

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.

Eppo: Does it need a data warehouse?

Yes. Warehouse-native analysis is the whole architecture. Without Snowflake, BigQuery, Redshift or Databricks there is no product.

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.

Eppo: Does it include feature flags?

Yes. Assignment and measurement come from the same system, which is the main reason teams pick it over pairing a flag tool with a separate analysis tool.

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.

Share

Related pages

Other head to heads