Plans and Limits: What Each Featureflip Plan Includes
Featureflip has four plans you can sign up for yourself (Free, Team, Pro and Business) and an Enterprise plan arranged with our team. This page lists what each one allows and what changes when you move between them. Prices are on the pricing page.
Limits by plan
Section titled “Limits by plan”| Free | Team | Pro | Business | Enterprise | |
|---|---|---|---|---|---|
| Team members | 3 | 5 | 10 | 25 | Unlimited |
| Projects | 1 | 3 | 10 | 25 | Unlimited |
| Environments per project | 2 | 3 | 5 | Unlimited | Unlimited |
| Flags per project | 10 | Unlimited | Unlimited | Unlimited | Unlimited |
| Webhook endpoints | 1 | 3 | 3 | Unlimited | Unlimited |
| Audit log retention | 7 days | 30 days | 30 days | 90 days | 365 days |
Features that depend on the plan
Section titled “Features that depend on the plan”| Feature | Available on |
|---|---|
| Scheduled changes | Team, Pro, Business, Enterprise |
| Cleanup notice emails | Team, Pro, Business, Enterprise |
| Requiring two-factor authentication for every member | Team, Pro, Business, Enterprise |
| Flag owners | Pro, Business, Enterprise |
| Single sign-on through your own OIDC identity provider, with Require single sign-on | Business, Enterprise |
| Maximum personal access token lifetime | Business, Enterprise |
| Required change reasons on critical environments | Business, Enterprise |
| SAML and SCIM | Enterprise |
Everything else is on every plan, Free included: targeting rules, segments, percentage rollouts, prerequisites, all 14 SDKs, the Management API, the MCP server, the Terraform provider, the audit log, flag expiration dates, stale flag detection, flag evaluation analytics, the flag cleanup Action, two-factor authentication, typing the environment key before a change to a critical environment, and sign-in with Google or GitHub.
How the limits are counted
Section titled “How the limits are counted”Four of them need a word of explanation.
- Team members include pending invitations. An invite you’ve sent holds a seat until it’s accepted, revoked or expires. Revoke stale invites to get the seat back.
- Environments are counted per project. Each project has its own allowance, so on Team all three of your projects can have three environments each. A new project starts with Development, Staging and Production, trimmed to fit the plan. On Free that leaves Development and Production, and the project has no room for a third.
- Flags per project counts active flags only. Archiving a flag frees its place, and the archived flag keeps its key. Restoring it takes a place again, so on Free a project that already has 10 active flags can’t restore another until you archive or delete one.
- Webhook endpoints are the subscriptions in Organization Settings, whichever events and projects each one covers.
When you reach a limit, Featureflip refuses to create the next item and tells you which limit you hit, for example “Project limit of 3 reached for Team plan. Upgrade to create more projects.”
Upgrading
Section titled “Upgrading”A higher plan’s limits and features apply as soon as the upgrade goes through. Plans are managed in the Billing section of Organization Settings, and only the organization’s Owner can open it. Enterprise isn’t sold there. For that, use the address on the pricing page.
Downgrading or cancelling
Section titled “Downgrading or cancelling”Clean up first. A move to a smaller plan goes through only once the organization fits it. If you have more projects, members (pending invitations count), environments in a project, active flags in a project or webhook subscriptions than the target plan allows, the change is refused, and the plan dialog lists what to remove. Archived flags don’t count. Cancelling runs the same check against Free. The audit log is the one limit that doesn’t block: before you confirm, Featureflip warns you how much history the new plan keeps.
Once the organization fits, a move to a smaller paid plan applies right away, prorated. Cancelling keeps your paid plan until the end of the period you’ve paid for, then moves the organization to Free.
When the plan changes without you choosing it. A payment whose retries run out, a cancellation or plan change made in the Stripe billing portal, or a scheduled cancellation that lands after the organization grew past Free can all leave it over its new plan’s limits. It then becomes read-only. Nothing is deleted and nobody loses access. Flags keep serving exactly as before, and you can still turn them on and off, clean up and manage billing. Every other change is refused with organization_read_only until the organization fits a plan again, either by cleaning up or by choosing a plan it fits. Webhook subscriptions over the cap don’t hold it read-only. The oldest ones up to the cap keep delivering, and the rest are suspended until a slot frees up, as plan_limit_reached describes. Organizations that were already over a limit before this policy are left as they are.
Whichever way the organization lands on a smaller plan, its features follow the plan:
Scheduled changes (below Team). Pending changes still run, and they stay listed on the flag’s page, where you can cancel any you no longer want. You can’t schedule new ones.
Cleanup notices (below Team). The emails stop. Expired and dead flags keep their markers in the flags list. Upgrade again and notices resume with flags that qualify from that day on, so whatever piled up in the meantime never arrives as one batch.
Flag owners (below Pro). Owners stay stored but are hidden in the dashboard, and you can’t name new ones. On Team, cleanup notices go to your Owners and Admins rather than to each flag’s owner. Upgrade again and the stored owners reappear. Flag owners has the details.
Single sign-on (below Business). Sign-in through your identity provider stops, Require single sign-on is no longer enforced, and your connection settings are kept for when you come back. Anyone who only ever signed in through SSO needs to set a password first, and the single sign-on guide shows how to do that from the sign-in page.
Required change reasons (below Business). Environments that require a reason stop enforcing it, so changes go through without one. The setting stays on where it was, and an Admin or Owner can still switch it off. It can’t be switched back on until you move up again. Critical environments has the details.
Audit log. Retention follows the new plan. Entries older than its window are removed in the next daily cleanup, so on Free anything older than 7 days goes. If you need that history, review or copy what you need from the audit log before your plan changes.
Prices for existing subscribers
Section titled “Prices for existing subscribers”If your subscription started before the current prices, it keeps the price you signed up at. It moves to the current price when you change plans or switch between monthly and annual billing.
Deleting an organization
Section titled “Deleting an organization”Only the Owner can delete an organization, and only while it’s on Free. On a paid plan, cancel the subscription first and wait for the billing period to run out, at which point the organization drops to Free and the delete goes through.
Next steps
Section titled “Next steps”- Pricing: current prices, monthly and annual
- Team Management: invite members and manage roles
- Flag Owners: the Pro feature for naming who is responsible for each flag
- Single Sign-On: connect your identity provider on Business and Enterprise