Experiments & Feature Flags: Free/Growth plan availability - #192
Open
tylergoerzen-mxp wants to merge 7 commits into
Open
Experiments & Feature Flags: Free/Growth plan availability#192tylergoerzen-mxp wants to merge 7 commits into
tylergoerzen-mxp wants to merge 7 commits into
Conversation
Experiments and Feature Flags launch on Free and Growth plans on 2026-08-24. Replace Enterprise-only gating across 24 pages with per-plan entitlements (Plan Availability tables on the two core pages), rewrite both pricing FAQs for the MEU-based self-serve model, and drop the retired API-request pricing unit for bundled Feature Flags. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Confidence Score: 5/5The PR appears safe to merge after the planned launch hold. No blocking failure remains; the previously reported Enterprise entitlement inconsistency is resolved at the current head.
|
| Filename | Overview |
|---|---|
| docs/experiments.mdx | Documents plan entitlements and over-cap behavior; the previously incorrect Enterprise MEU guidance is fixed. |
| docs/featureflags.mdx | Adds per-plan flag and cohort limits and revises pricing guidance. |
| docs/pricing.mdx | Removes Experiments from Enterprise-exclusive features and links to detailed availability. |
| troubleshooting/faqs.mdx | Adds a concise entry directing customers to plan-specific entitlements. |
Reviews (7): Last reviewed commit: "Merge branch 'main' into xp-ff-free-grow..." | Re-trigger Greptile
…guidance Four review passes (style, clarity, accuracy, consistency) surfaced: - "Experiments cannot be deleted" contradicted reference/delete-experiment.mdx; scoped to the Enterprise no-add-on allotment and moved to the creation flow as a Warning per style guide. - Enterprise rows read as a downgrade from Free and lost the "per project" grain; restored grain, added the unlimited-MEU cell, and restored the trial. - "API requests are unlimited on all plans" was false for standalone Feature Flags; qualified to the bundled case. - Over-cap behavior corrected against the enforcement code: reaching the cap without purchased volume pauses Experiments until the next calendar month, rather than only stopping metric computation. - Restored client and server-side API request estimation guidance dropped with the stale pricing framing; reframed for capacity planning. - Added the plan-availability prerequisite to the 10 SDK flag pages so they match their OpenFeature siblings. - Style: opening lines above Plan Availability, canonical table headers, #### FAQ headings, second person, escaped breadcrumbs, stale billing notes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
paid_line_exists_for_buyable (billing/agreements/tasks/usage.py:717) treats a line as paid when EITHER net_price > 0 OR custom_overage_rate > 0. The Growth plan-builder curve's included 5k MEU tier carries an explicit overage rate (EXPERIMENTS_FREE_TIER_OVERAGE_RATE = 0.07667), and AgreementLine inherits it from the point's overage_rate_default, so Growth always has a paid line and the usage_pct >= 1.0 blocking branch never fires. Free's line is custom_overage_rate = 0, so only Free pauses. Free pauses at the cap; Growth continues and is billed overage. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- featureflags.mdx opened by claiming API requests are unlimited without qualification, contradicting the standalone-Enterprise sentence 10 lines below and both FAQ answers. Moved the claim next to the standalone caveat. - experiments.mdx stated a user counts as one MEU regardless of experiment count, contradicting the 30-experiment divisor in the pricing FAQ. Added the cap and linked the calculation, so nobody budgets off the wrong rule. - Removed a verbatim duplicate of the Free cohort-targeting sentence, and reworded the page intros that repeated the Overview clause word for word. - Canonical 'MEU Allowance' column header; consistent number formatting on the cohort guardrail; plainer wording in the creation Warning. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
myronkaifung
approved these changes
Aug 24, 2026
Added legal notice regarding the 20M user cohort limit for feature flags.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Experiments and Feature Flags launch on Free and Growth plans on August 24, 2026. This PR replaces the Enterprise-only gating across the docs with the new per-plan entitlements. Hold merge until launch.
Entitlements published (quantities only, no dollar prices — per docs convention)
Over-cap behavior, verified against the billing enforcement code rather than the pricing sheet: Free pauses (all experiment API access 403s until the next calendar month or an upgrade; flags keep serving), Growth is billed overage and keeps working. The mechanism is
paid_line_exists_for_buyableinbilling/agreements/tasks/usage.py, which counts a line as paid whennet_price > 0orcustom_overage_rate > 0— Growth's included 5k tier carries an explicit overage rate, so its blocking branch never fires.Free plans get cohort targeting conditions in one rollout group and cannot save cohorts.
Changes
docs/experiments.mdx— Plan Availability table; over-cap section; pricing FAQ rewrittendocs/featureflags.mdx— Plan Availability table; pricing FAQ rewritten (API-request pricing unit removed for the bundled case, retained for standalone Enterprise); request-estimation guidance kept and reframed for capacity planningdocs/featureflags/runtime-events.mdx— inherits Feature Flags availabilitydocs/pricing.mdx— Experiments removed from the Enterprise-exclusives list; Free-plan cohort line correcteddocs/pricing/startup-program.mdx— Experiments no longer framed as a premium unlocktroubleshooting/faqs.mdx— plan-availability FAQ entrySources
Official Price List (2026-08-20), "FAQ: Self-serve XP + FF introduction" (Wait Harris, Aug 19), "FAQ: Feature Flag Pricing and Packaging" (Jun 17), analytics PRs #100402 / #100279 / #100569, Slack #xp-ff-self-serve-pricing.
Two numbers in the price list were not used, deliberately: the sheet's intro bullets say Free 5k / Growth 10k MEU (its own entitlement table, the plan-builder curve, and the overage FAQ all say 1k / 5k), and its "1 saved cohort" for Free is superseded by MULTI-861, which shipped one rollout group with cohort conditions and no saved cohorts.
Deliberately not published
MEU tier dollar prices, overage rates, and the Startup plan's caps (1.2M annual MEU / 120M API requests) — the pricing FAQ marks those as not stated in docs or ToS.
Reviewer notes
mint broken-linkspasses for every link this PR adds (8 pre-existing breaks elsewhere, none in touched files).Runtime Events was checked for separate gating and has none — no buyable, no entitlement check, no rollout gate.
🤖 Generated with Claude Code