Softwr

Testing · head to head

Eppo vs Merge

Eppo logo

Eppo

Testing

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

From
On request
Free plan
No
Merge logo

Merge

Automation Integration

One API for all your integrations

From
Free
Free plan
Yes

The short version

  • Merge is a unified API platform.
  • Merge starts at $650/mo; Eppo prices on request.
  • Only Eppo lists warehouse-native analysis; only Merge lists unified API.
  • Where Merge falls short: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings.
  • Prices and features on this page were last checked on 20 November 2026.

How do Eppo and Merge differ?

Eppo and Merge differ on starting price (On request against Free), pricing model (Quote against Usage-based) and free tier (No against Yes). Only the attributes on which Eppo and Merge actually diverge.

Attributes where Eppo and Merge differ
AttributeEppoMerge
Starting priceOn requestFree
Pricing modelQuoteUsage-based
Free tierNoYes
PlatformsWebAPI
CategoryTestingAutomation Integration
Founded20212020

Which features does each one have?

They share no listed features; 8 appear only for Eppo and 20 only for Merge. 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 Merge

  • Unified API
  • HRIS integrations
  • Accounting integrations
  • CRM integrations
  • ATS integrations
  • Ticketing integrations
  • File storage integrations
  • Workday

What is each one used for?

Merge is most often brought in for workflow Automation. 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 Merge
  • A product organisation with low traffic on a key surface that needs variance reduction to reach a decision in weeks instead of monthsnot Merge
  • 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 Merge
  • An existing Datadog customer consolidating product analytics, feature flags and experimentation onto one vendor agreementnot Merge

Merge

  • Workflow Automationnot Eppo
  • Data Integrationnot Eppo
  • Process Automationnot Eppo
  • App Integrationnot Eppo
  • API Connectivitynot Eppo

Where do Eppo and Merge fall short?

Merge's most cited limit: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings. 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

Merge

  • Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
  • No support for legacy systems without APIs; limited to modern SaaS applications
  • Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs

How much do Eppo and Merge cost?

Eppo is priced on request; Merge has a free plan, with paid plans from $650/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

Merge

Free
  • FreeFree
    • 1 linked account
    • All integrations
    • Standard support
  • Launch$650/mo
    • 50 linked accounts
    • All categories
    • Email support
  • Scale$2,500/mo
    • Unlimited accounts
    • Priority support
    • SLA
  • EnterpriseOn request
    • Dedicated support
    • Custom contracts
    • Advanced security

Which should you pick?

Choose Eppo if

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

Choose Merge if

  • You need unified api.
  • You want to start without paying.
  • You work on API.
  • You also want hris integrations.

Questions people ask

Is Eppo or Merge better?
Neither clearly leads. Eppo starts at On request and Merge at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Eppo or Merge?
Merge has a free tier; the other does not. Paid plans start at On request for Eppo and Free for Merge.
Does Eppo or Merge run on more platforms?
Eppo runs on Web. Merge runs on API.
Can I use Merge for free?
Yes. Merge 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 Merge is typically brought in for.
What can Eppo do that Merge cannot?
Eppo covers Warehouse-native analysis, Sequential testing, CUPED variance reduction, Feature flagging. Merge covers Unified API, HRIS integrations, Accounting integrations, CRM integrations.

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.

Merge: What is a Linked Account in Merge?

A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.

Source
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.

Merge: Can I access custom data not in Merge's universal schema?

No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.

Source
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.

Merge: What happens if I switch away from Merge?

Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.

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.

Merge: Does Merge work with legacy systems?

No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.

Share

Related pages

Other head to heads