What the bill is metered on (monthly active users, service connections, requests, or seats), whether you must self-host, and whether experimentation and analytics should come in the same product.
Notes on this pair
PostHog is a candidate when flags should sit next to product events and the rest of the analytics workflow. GrowthBook warrants a trial if experiments should run against an existing data warehouse. Verify exposure logging in both.
1 million flag requests free each month, then pay as you go.
No card is needed for the free allowance, and usage stops at the free limit until a card is added. Check the per-request rate on the pricing page before budgeting.
When to choose it
Flags next to PostHog analytics and replays.
What to confirm
Flags are one product among many, so the free flag-request allowance is shared with a pay-as-you-go model that needs watching.
Documented capabilities
Rollout percentages, cohort targeting and multivariate variants
Measure impact next to analytics and session replays
Create and update flags with PostHog AI or the MCP server
Usage stops at the free limit unless you add a card