Split
A weekend of work, and real gaps remain.
Feature flags with measurement attached: a flag rollout is treated as an experiment, with metrics, significance and automatic alerts if a treatment makes something worse.
Build me feature flags with local evaluation and an honest measurement story. STACK - Node service, SQLite for definitions, a CDN-cached JSON snapshot for delivery - Client SDK evaluates locally; no network call per flag check, ever THE FLAG - Key, default, and a list of rules: match by attribute, or by percentage bucket - Bucketing by a murmur hash of key plus subject id, so a subject stays in the same bucket across releases and across services - Every change appended to an audit table: who, when, before, after DELIVERY - The whole ruleset published as one JSON document to object storage on every change - SDKs poll with an ETag, and fall back to the last good snapshot if the fetch fails - A flag must resolve to its default when everything is unreachable EXPOSURE EVENTS - Log an event the first time a subject is exposed to a treatment, not on every evaluation - Batch and send asynchronously; a dropped exposure must never block the request MEASUREMENT, WHERE PEOPLE FOOL THEMSELVES - Join exposures to your own metrics table by subject id - Report the difference with a confidence interval, not a p-value, and refuse to declare a winner before a preset sample size - Write the minimum detectable effect in the README, so nobody reads noise as a result Include a README on the hashing scheme, the snapshot cadence and the stopping rule.
What you lose
- Feature flags joined to metrics, so a rollout is measured rather than watched
- Statistical significance computed properly, including sequential testing
- Automatic alerting when a treatment degrades a guardrail metric
- SDKs for a dozen languages with local evaluation and no network in the hot path
- Audit trails a regulated team can show an auditor
If you would rather not build
- Flagsmith — open-source flags and remote config
The escape hatch
open source · no votes, no paid placement
Unleash
$0Feature flag server with gradual rollouts, segments and SDKs for most languages.
Unleash/unleashfree · open source
GrowthBook
$0Feature flags with experiment analysis run against your own warehouse.
growthbook/growthbookfree · open source
Why this verdict
our own opinion · changed only by a person
47/100
Verdict kinda at 47: flags with stable bucketing and local evaluation are a weekend. Measurement is where this gets its score capped — the statistics are easy to write and easy to get wrong, and the prompt spends its last section refusing to let you peek.
History
tracked since 9 Aug 2026 · nothing is ever overwritten
Questions about Split
answered from the record above
Is Split free?
No — the plan we track is $33 a month. Team plans start around $33 per seat per month billed annually; usage is metered on monthly tracked keys, and enterprise is quoted.
Can you replace Split by building your own?
ALMOST. A weekend of work, and real gaps remain. Replacement score 47 out of 100, build time a weekend. Read what you lose before you decide.
How much does Split cost?
$33 a month on Team — $396 a year. Recorded 9 Aug 2026.
What do you lose by replacing Split?
Feature flags joined to metrics, so a rollout is measured rather than watched; Statistical significance computed properly, including sequential testing; Automatic alerting when a treatment degrades a guardrail metric; SDKs for a dozen languages with local evaluation and no network in the hot path; Audit trails a regulated team can show an auditor. If any of those carry weight for you, keep paying.
Is there an open-source alternative to Split?
Yes: Unleash, GrowthBook. The prompt on this page is for when you want it your way instead.
Related entries
same category first, most replaced first
Every week, something stops being worth paying for.
New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click.
free forever · no tracking pixel · every prompt stays free on the site