Datadog feature flags vs Flagger.gg
Datadog's feature flags come from its 2025 purchase of Eppo and tie flags to Datadog's metrics and experiments. Flagger.gg doesn't need an observability suite: it's a standalone flag service with local evaluation and agent access through MCP and the CLI. Metric-tied rollouts and auto-rollback are in development on Flagger.gg.
Updated
Datadog, Eppo and feature flags
Datadog announced it was acquiring Eppo, an experimentation and feature-flag platform, in May 2025 (Datadog's announcement). Datadog now offers Feature Flags, built on OpenFeature, which correlate flags with APM, RUM, logs and SLOs and support monitor-driven canaries with automatic rollback, and Eppo's experimentation as Datadog Experiments. Datadog's hosted MCP server has a feature-flags toolset (MCP tools). Facts checked October 30, 2026.
Side by side
| Datadog Feature Flags | Flagger.gg | |
|---|---|---|
| What it needs | Part of the Datadog platform | Standalone; no observability suite |
| Metrics and rollback | Flags tied to APM, RUM, logs and SLOs; monitor-driven canaries with automatic rollback | Kill switch (within a second) and revert today; metric-tied rollouts and auto-rollback In development |
| Experiments | Datadog Experiments (formerly Eppo) | In development |
| SDK standard | OpenFeature | Go and Node SDKs with local, synchronous evaluation and shared test vectors |
| Agent access | Feature-flags toolset in Datadog's hosted MCP server | Hosted or stdio MCP with 11 tools scoped by agent token, a JSON CLI, a note required on every agent write, no approve tool |
Where Datadog is stronger
- Flags next to your telemetry. If you already run Datadog, seeing a flag's effect on errors and latency, and rolling back on a monitor, is built in.
- Experimentation. Eppo's statistics, now Datadog Experiments.
- OpenFeature. A vendor-neutral SDK API.
Where Flagger.gg fits better
- You don't want flags tied to an observability vendor. Flagger.gg works on its own.
- Agents ship your code. Scoped agent tokens, per-run audit, notes on every write, protected flags agents can only kill, and approvals that agents can't grant themselves.
- Local evaluation with a disk cache. Checks never make a network call, and a restart during an outage serves the last good rules.
Flagger.gg isn't the Flux/CNCF Flagger, a Kubernetes operator; it's the hosted flag service at flagger.gg.
FAQ
What's an alternative to Datadog feature flags?
If you want flags without an observability platform, a standalone service such as Flagger.gg, LaunchDarkly or one of the open-source tools. Flagger.gg is the one built around AI agents changing flags.
Did Datadog buy Eppo?
Yes. Datadog announced the acquisition in May 2025, and Eppo's product is now Datadog Experiments.
Does Flagger.gg roll back automatically on bad metrics?
Not yet; that's in development. Today a person or an agent kills or reverts the flag with one command, and the change reaches apps within a second.
Ship your next change behind a flag.
Sign up, add an SDK key to your app and give your agent a token.