Skip to content

Experiments & Feature Flags: Free/Growth plan availability - #192

Open
tylergoerzen-mxp wants to merge 7 commits into
mainfrom
xp-ff-free-growth
Open

Experiments & Feature Flags: Free/Growth plan availability#192
tylergoerzen-mxp wants to merge 7 commits into
mainfrom
xp-ff-free-growth

Conversation

@tylergoerzen-mxp

@tylergoerzen-mxp tylergoerzen-mxp commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

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)

Included Free Growth Enterprise (no purchase) With purchased Experiments
Created experiments Unlimited Unlimited 3 per project Unlimited
MEU / month 1k 5k Unlimited Per purchased tier (Growth: up to 100k self-serve)
Active flags (per org) 10 50 3 500
Max cohort size 100k 20M 20M 20M
FF API requests Unlimited Unlimited Unlimited Unlimited (standalone FF is request-priced)

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_buyable in billing/agreements/tasks/usage.py, which counts a line as paid when net_price > 0 or custom_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 rewritten
  • docs/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 planning
  • docs/featureflags/runtime-events.mdx — inherits Feature Flags availability
  • 10 SDK flag pages + 8 OpenFeature pages — Enterprise prerequisite replaced with a plan-availability pointer (also fixed two double-spaces and python's unbalanced link paren)
  • docs/pricing.mdx — Experiments removed from the Enterprise-exclusives list; Free-plan cohort line corrected
  • docs/pricing/startup-program.mdx — Experiments no longer framed as a premium unlock
  • troubleshooting/faqs.mdx — plan-availability FAQ entry

Sources

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

  1. Enterprise is unchanged by this launch — 3 experiments per project, 3 active flags, both raised by purchasing Experiments. Worth a sanity check that the table reads that way rather than as a downgrade.
  2. "Analyze prior to purchase date" is kept and re-scoped to purchased volume; included-MEU usage is explicitly exempted. Cut it if that's no longer accurate.
  3. Historical changelog entries are intentionally untouched; the launch changelog is owned separately.
  4. mint broken-links passes 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

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>
@tylergoerzen-mxp
tylergoerzen-mxp requested a review from a team as a code owner August 24, 2026 05:14
@mintlify

mintlify Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
mixpanel-docs 🟢 Ready View Preview Aug 24, 2026, 5:17 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@greptile-apps

greptile-apps Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

The 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.

Important Files Changed

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

Comment thread docs/experiments.mdx Outdated
…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>
@linear-code

linear-code Bot commented Aug 24, 2026

Copy link
Copy Markdown

MON-296

Added legal notice regarding the 20M user cohort limit for feature flags.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants