Run a staged rollout with the permissions and environment approvals you use in production. Check whether approval and audit capabilities are in the quoted tier.
Foundation $12 per service connection a month billed monthly, or $10 billed yearly. Enterprise custom.Compare feature flag software
Platforms that let engineers ship code behind a switch, then turn it on for chosen users, percentages, or segments without a new deploy, and switch it off again when something breaks. A local run of GrowthBook, LaunchDarkly and Unleash assigned the same 1,000 customers differently. Statsig was not run.
What to compare first
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.
Where to start
Compare how the product connects flag exposure, assignment and metrics. Test one guardrail metric before moving the team's next launch into the platform.
Developer free. Pro $150 a month. Enterprise custom.Budget for operating the service and SDK reliability. Try the last-known flag configuration when an environment loses its network connection.
Start-Up $45 a month billed monthly, or $40 billed annually. Scale-Up $300 or $250. Enterprise custom.Local SDK check, no vendor account
On 2026-11-19 a script in research/feature-flag-rollback evaluated one flag, checkout-redesign, for 1,000 customer ids and 5 staff ids. GrowthBook 2.2.0 used an in-memory payload. LaunchDarkly Node server SDK 9.17.0 read flags/rollout.json and flags/killed.json, with events disabled and a dummy SDK key. Unleash client 6.12.2 loaded a bootstrap document and did not start its poller. The script repeats. The second pass turned on the same ids as the first.
| SDK | Customers on at 10% | Staff forced on | On after the kill | Failure behavior in this run |
|---|---|---|---|---|
| GrowthBook 2.2.0 | 106 of 1,000. Same 106 on the second pass. | 5 of 5 | 0 of 1,005 | Empty client value was null, source unknownFeature. getFeatureValue returned the fallback false. init against 127.0.0.1:9 returned success false and fetch failed, then the fallback payload turned on the same 106 ids. |
| LaunchDarkly 9.17.0 | 93 of 1,000. Reason FALLTHROUGH. Same 93 on the second pass. | 5 of 5. Reason RULE_MATCH. | 0 of 1,005. Reason OFF. | Offline mode returned false with reason ERROR and errorKind CLIENT_NOT_READY. A missing flag file failed init with ENOENT and returned the same fallback. |
| Unleash 6.12.2 | 103 of 1,000. Same 103 on the second pass. | 5 of 5 | 0 of 1,005, even when the caller passed fallback true. | Before start, the caller fallback was used. An unknown flag name still used that fallback. A disabled flag did not. |
GrowthBook 2.2.0
- Customers on at 10%
- 106 of 1,000. Same 106 on the second pass.
- Staff forced on
- 5 of 5
- On after the kill
- 0 of 1,005
- Failure behavior in this run
- Empty client value was null, source unknownFeature. getFeatureValue returned the fallback false. init against 127.0.0.1:9 returned success false and fetch failed, then the fallback payload turned on the same 106 ids.
LaunchDarkly 9.17.0
- Customers on at 10%
- 93 of 1,000. Reason FALLTHROUGH. Same 93 on the second pass.
- Staff forced on
- 5 of 5. Reason RULE_MATCH.
- On after the kill
- 0 of 1,005. Reason OFF.
- Failure behavior in this run
- Offline mode returned false with reason ERROR and errorKind CLIENT_NOT_READY. A missing flag file failed init with ENOENT and returned the same fallback.
Unleash 6.12.2
- Customers on at 10%
- 103 of 1,000. Same 103 on the second pass.
- Staff forced on
- 5 of 5
- On after the kill
- 0 of 1,005, even when the caller passed fallback true.
- Failure behavior in this run
- Before start, the caller fallback was used. An unknown flag name still used that fallback. A disabled flag did not.
The three SDKs did not pick the same customers. GrowthBook coverage 0.1, a LaunchDarkly fallthrough weighted 10,000 of 100,000, and an Unleash flexibleRollout of 10 are all about 10 percent, and the counts were 106, 93 and 103. Stickiness held inside each SDK. It did not carry across SDKs.
GrowthBook treated the rollout and the experiment differently. The rollout fired the tracking callback 0 times and marked 106 results as force and 894 as defaultValue. A separate 50/50 rule marked all 1,000 results as experiment, fired the callback 1,000 times, and put 492 customers on the treatment. A flag that only controls access did not produce an exposure record in this SDK.
LaunchDarkly's offline-mode page says a server SDK in offline mode returns the fallback value passed into variation, not the flag's own default rule. The value in this run matches that. The reason code on this SDK version was CLIENT_NOT_READY. Their file-data page says a missing or invalid file means the SDK uses none of the file data. The missing-file client did that.
Unleash documents the need for synchronization or bootstrap data. The cold client used the caller's fallback. In a separate local refresh test, the poller got a connection-refused error. The client still reported synchronized and kept 103 of 1,000 customers on from the bootstrap data.
Open this section in the worksheet · Download the full table as CSV
What the published rates charge for this sample
The figures below are arithmetic on the rates published on 2026-11-19. They are not invoices. The sample is 8 service connections, 25,000 client-side monthly active users, 12 people who can log in, 8 million events and 4 million flag API requests. LaunchDarkly's own page uses a smaller example: 10 connections and 2,000 client MAU come to $58.33 a month on yearly billing. That matches 5 connections over the free 5 at $10, plus 1,000 MAU over the free 1,000 at $8.33.
| Product | Published meter | This sample | Seat note |
|---|---|---|---|
| LaunchDarkly Foundation | 5 service connections and 1,000 client MAU free, then $10 per connection and $8.33 per 1,000 MAU on the yearly card. Monthly card rates are $12 and $10. The compare table also prints client MAU as $10 per 1,000 a month. | $229.92 a month on the yearly card: 3 times $10 plus 24 times $8.33. The monthly card is $276: 3 times $12 plus 24 times $10. | The pricing page says there is no per-seat price. Developer does not bill overages. The page says to upgrade when a limit is hit. This sample is past both free limits. |
| Statsig Pro | $150 a month, 5 million metered events included, then $0.05 per 1,000. Developer is free for 2 million metered events. | $300 if all 8 million events are metered: $150 plus $150 of overage. A 0% or 100% flag check is not a metered exposure unless metric lifts are on. | The pricing page shows no per-seat price. SSO, role-based access and teams are listed on Enterprise, which is a quote. Event or experiment contracts are also Enterprise. |
| Unleash pay as you go | $75 per seat a month by credit card. Cloud includes 53 million API requests, then $5 per million. Client MAU and service connections are listed as unlimited. | 12 seats are $900. 4 million API requests stay inside 53 million, so the request overage is $0. | Self-hosted pay-as-you-go has a 5-seat minimum, $375, and 12 seats are still $900. Open source has no seat fee and the docs cap it at 1 project and 2 environments. |
| GrowthBook Pro | $40 per seat a month, up to 30 users and 3 projects. Managed warehouse is 2 million events, then $30 per million. CDN is 2 million requests, then $10 per million. | 12 seats are $480. Sending all 8 million events to the managed warehouse adds $180, for $660. A self-hosted open-source install does not use that warehouse meter. | A seat is one login. Starter is free up to 3 users, so 12 people do not fit. The FAQ says self-hosted open source has unlimited users. |
| Flagsmith Scale-Up | Free is 50,000 requests and 1 member. Start-Up is 1 million requests and 3 members. Scale-Up is 5 million or more requests, 5 members included and up to 20. The page shows extra members at $60 and $50 per member a month beside the monthly and yearly toggle. | 4 million requests fit the Scale-Up request line. 12 members are 7 extra seats. At $50 that is $350 before the plan sticker. At $60 it is $420. | This pass did not get a plan sticker price out of the page text. The project catalog checked the same day records Start-Up at $45 a month or $40 yearly and Scale-Up at $300 or $250. Treat those stickers as a prior read, and re-check the toggle before budgeting. |
LaunchDarkly Foundation
- Published meter
- 5 service connections and 1,000 client MAU free, then $10 per connection and $8.33 per 1,000 MAU on the yearly card. Monthly card rates are $12 and $10. The compare table also prints client MAU as $10 per 1,000 a month.
- This sample
- $229.92 a month on the yearly card: 3 times $10 plus 24 times $8.33. The monthly card is $276: 3 times $12 plus 24 times $10.
- Seat note
- The pricing page says there is no per-seat price. Developer does not bill overages. The page says to upgrade when a limit is hit. This sample is past both free limits.
Statsig Pro
- Published meter
- $150 a month, 5 million metered events included, then $0.05 per 1,000. Developer is free for 2 million metered events.
- This sample
- $300 if all 8 million events are metered: $150 plus $150 of overage. A 0% or 100% flag check is not a metered exposure unless metric lifts are on.
- Seat note
- The pricing page shows no per-seat price. SSO, role-based access and teams are listed on Enterprise, which is a quote. Event or experiment contracts are also Enterprise.
Unleash pay as you go
- Published meter
- $75 per seat a month by credit card. Cloud includes 53 million API requests, then $5 per million. Client MAU and service connections are listed as unlimited.
- This sample
- 12 seats are $900. 4 million API requests stay inside 53 million, so the request overage is $0.
- Seat note
- Self-hosted pay-as-you-go has a 5-seat minimum, $375, and 12 seats are still $900. Open source has no seat fee and the docs cap it at 1 project and 2 environments.
GrowthBook Pro
- Published meter
- $40 per seat a month, up to 30 users and 3 projects. Managed warehouse is 2 million events, then $30 per million. CDN is 2 million requests, then $10 per million.
- This sample
- 12 seats are $480. Sending all 8 million events to the managed warehouse adds $180, for $660. A self-hosted open-source install does not use that warehouse meter.
- Seat note
- A seat is one login. Starter is free up to 3 users, so 12 people do not fit. The FAQ says self-hosted open source has unlimited users.
Flagsmith Scale-Up
- Published meter
- Free is 50,000 requests and 1 member. Start-Up is 1 million requests and 3 members. Scale-Up is 5 million or more requests, 5 members included and up to 20. The page shows extra members at $60 and $50 per member a month beside the monthly and yearly toggle.
- This sample
- 4 million requests fit the Scale-Up request line. 12 members are 7 extra seats. At $50 that is $350 before the plan sticker. At $60 it is $420.
- Seat note
- This pass did not get a plan sticker price out of the page text. The project catalog checked the same day records Start-Up at $45 a month or $40 yearly and Scale-Up at $300 or $250. Treat those stickers as a prior read, and re-check the toggle before budgeting.
Statsig defines a metered event as an exposure on a partial rollout with metric lifts, a logged or imported event, an ingested warehouse metric, or a custom metric. Client SDKs dedupe the same user and feature for 60 minutes. Server SDKs dedupe for 1 minute. An extra event dimension is another logged event. Past the Developer allowance, the FAQ says targeting keeps working and metric-lift math stops until you move to Pro.
Flagsmith counts /flags, /identities, /traits and server-side /environment-document. The FAQ says a first paid overage inside 200 percent of the plan gets 30 days before a bill, and that Start-Up overage after that is $7 per 100,000 requests. The free plan gives 7 days to upgrade. Flags keep being served during that window.
LaunchDarkly counts a service connection as one server-side SDK connected to one environment, averaged over the month. Every replica, worker, and dev or staging environment counts. Client MAU is a unique client-side user or device. Those are separate meters from the 8 million product events in the sample.
Software shortlist
| Software | Pricing | Good fit for | Research |
|---|---|---|---|
| Foundation $12 per service connection a month billed monthly, or $10 billed yearly. Enterprise custom.Published price | Deep targeting and governance, and adding teammates does not add a seat charge. | Profile | |
| Developer free. Pro $150 a month. Enterprise custom.Published price | Flags and experimentation together. The free plan does not meter flag checks. | Profile | |
| 1 million flag requests free each month, then pay as you go.Usage-based | Flags next to PostHog analytics and replays. | Profile | |
| Contact sales. Harness has a free plan, but its pricing page doesn't say whether Feature Management and Experimentation are part of it.Quote required | For teams that already run Harness for delivery and want flags and experiments tied into the same pipeline platform. | Profile | |
| Start-Up $45 a month billed monthly, or $40 billed annually. Scale-Up $300 or $250. Enterprise custom.Published price | Self-hosted, including on-premise or air-gapped, with a managed option still available. | Profile | |
| Open source free. Enterprise $75 per seat a month billed monthly.Published price | An open-source core you can run yourself, and a paid Enterprise tier for support and governance. | Profile | |
| Starter free. Pro $40 per seat a month. Enterprise custom.Published price | Experimentation alongside flags, with the data kept in your warehouse. | Profile | |
| Pro $110 a month. Smart $325. Enterprise $900. Dedicated $4,500. Forever Free $0.Published price | The free plan includes the paid feature set, with startup and student discounts. | Profile | |
| Free $0. Business $500 a month billed annually. Enterprise custom.Published price | A free plan to try, and a team plan when more people need permissions. | Profile | |
| Open source free. Pro $200 a month. Enterprise custom.Published price | Git-native flags you host yourself. | Profile | |
| Quote only. Optimizely says every plan is individually packaged.Quote required | Flags, experiments and an uptime SLA, from a vendor with a long experimentation history. | Profile | |
| $55 per million monthly flag configuration requests billed annually. $89 billed monthly. $100 on demand.Published price | Rollouts read against the APM and RUM you already have in Datadog. | Profile | |
| Request a custom CloudBees Unify pricing quote.Quote required | Flags inside a CloudBees CI delivery setup. | Profile |
What to check before buying
What the price is metered on
Vendors charge by monthly users, by service connections, by flag requests, or by seat, and the same traffic gives very different bills across them.
Estimate your client users, backend services and flag evaluations for a month, then price each tool in its own unit.
Free tier ceiling
Free tiers differ a lot: unlimited flags with small request limits at some vendors, usage allowances at others.
Read the free tier limits in the vendor's unit and compare them with what a single real app generates.
Self-hosting and data location
Open-source and self-hosted options change cost, and some teams cannot send flag data to a vendor cloud.
Check whether self-hosting is offered, which tier includes it, and whether it carries a seat minimum.
Experimentation and analytics in the box
If product teams run A/B tests, an included stats engine saves a second tool, while pure flag tools need one.
Confirm whether the plan includes experiments and the statistical methods it uses.
Governance and cleanup
Stale flags pile up, and larger teams need approvals, audit logs and role-based access.
Look for audit logs, change requests and stale-flag detection on the tier you would buy.
Staff-only flag, percentage rollout, flag service down
Create a staff-only flag in staging, expand it to a percentage and simulate a rollback under load. Inspect SDK behavior when the flag service is unreachable. Cached flags and safe application defaults matter as much as how fast a toggle looks in the dashboard.
Exposure events and whether the assignment sticks
A flag can control access without providing valid experiment assignment or metric attribution. If both jobs matter, compare exposure events, assignment persistence and the time it takes to connect the analysis to your event store.
Who can change production, and which unit the bill uses
Count how many environments and permission boundaries the team needs. Test the approval path, audit export and service identity that a real deployment uses. Ask which features are included and whether the limit is based on seats, traffic, services or another unit.