Eppo is a warehouse-native experimentation and feature flag platform acquired by Datadog in 2025 and sold as Eppo by Datadog. Pages here cover replacing it with self-hosted GrowthBook.
Two warehouse-native experimentation tools compared: supported warehouses, how each reads assignment and event tables, local SDK evaluation, statistics features and which GrowthBook features need Enterprise, and the difference between a Datadog-owned SaaS and a self-hosted, MIT-licensed core.
Because Eppo already reads your own assignment logs and fact tables, moving to GrowthBook is mostly about rebuilding definitions: connecting GrowthBook to the same warehouse, recreating metrics and flags, swapping SDKs and logging callbacks, and re-running live experiments.
Cost of ownership by component, without vendor prices Eppo does not publish: subscription against GrowthBook's free or Enterprise self-hosted plan, warehouse compute that both tools spend, hosting GrowthBook and MongoDB, migration and ongoing operation.
What is documented about Eppo by Datadog, including continued support and integration with Datadog Product Analytics, what that means for teams not on Datadog, and the questions to settle before renewing or moving to self-hosted GrowthBook.
An exit checklist for Eppo: assignment logs and events already live in your warehouse, Eppo's output schema keeps results and intermediate tables, while flag configuration, metric definitions and experiment write-ups need capturing before access ends.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.