Eppo StrawberryFeature flags checked against experiments, in one pass
Hand a companion the outcome. It reads the Eppo feature flags, does the 9-operation version of the job, and stops for your click on anything that changes a record.
Open the feature flag. Check it against something else. Write the change. Move to the next one. That is the Eppo afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a feature flag until you approve it.
What it can do is exactly what Eppo exposes to an account you authorise and nothing beyond it: 9 operations, 6 reads and 3 writes. In practice that means it can upsert a metric, create a feature flag and create an experiment, and work across the feature flags, experiments and metrics.
The Eppo API stops at Eppo. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the feature flags come from?
6 of the 9 operations are reads.
Your account, not a guess at it: a companion can toggle feature flag, list metrics and list feature flags, and the full list below is the whole list, with nothing inferred from Eppo's documentation.
The feature flags are what most of this inventory is about, alongside the experiments. A companion can hold all 9 of these operations and forty open tabs in the same pass, which is how an afternoon of Eppo admin becomes a queue you review.
- Toggle Feature Flag
- List Metrics
- List Feature Flags
- List Experiments
- Get Feature Flag
- Get Experiment Results
What happens before it can upsert metric?
All 3 write operations wait for you.
A companion can upsert a metric, create a feature flag and create an experiment, and each one is staged on an approval card first: you see the feature flag, the field and the new value before it lands in Eppo.
Nothing in Eppo is sent, changed or deleted on your behalf without that click, and a rejected card leaves the feature flag exactly as it was. The gate is the same one on every surface, described at security.
- Upsert Metric
- Create Feature Flag
- Create Experiment
What does the recurring feature flags pass look like?
Yes.
Saved as a routine, the Eppo feature flags pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The research and analysis playbook catalogues the other recurring shapes of the reporting, the Eppo feature flags sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents