Flagsmith

Name: Flagsmith
Brand: Flagsmith
Price: 040 USD

Open source feature flags you can host yourself without asking permission

Flagsmith is an open source feature flag and remote configuration platform that lets engineering teams turn features on and off per environment, per segment, or per individual user without redeploying, using SDKs for roughly a dozen languages plus a globally replicated Edge API; it runs as a hosted service starting free for 50,000 API requests a month or as a self-hosted deployment you operate on your own infrastructure.

Visit website

Overview

Flagsmith does one job in this category and does not pretend otherwise: it is a feature flag and remote config service, not a product analytics tool and not a session replay tool. You define a flag, you decide which environments and which users see it, and your application asks Flagsmith at runtime what the answer is. That covers dark launches, percentage rollouts, kill switches for a misbehaving feature, per-customer entitlements, and remote configuration values you want to change without shipping a new mobile binary through app review.

The reason it shows up on small-company shortlists rather than only enterprise ones is the combination of price and licensing. The hosted free tier gives one seat unlimited flags, environments, identities, and segments with 50,000 API requests a month, and the Start-Up tier at $40 a month billed yearly raises that to a million requests and three seats. Under that sits an open source codebase you can run yourself on Docker or Kubernetes, which matters both for teams with data residency constraints and for teams who simply refuse to make a runtime dependency out of a vendor they cannot inspect.

The company behind it is unusual for the category. Flagsmith was founded in London in 2018 by Ben Rometsch and Kyle Johnson as a spin-out from their digital agency, originally under the name Bullet Train, and it has stayed bootstrapped rather than taking venture money. Headcount sits somewhere around 26 to 30 people. That shapes the roadmap: Flagsmith adds flag infrastructure and governance features, and it has not tried to become an experimentation platform, an analytics warehouse, or a suite.

The honest limitation follows from that focus. Flagsmith can split traffic across multivariate flag values, but it does not compute experiment results for you. There is no sequential testing engine, no CUPED variance reduction, no automatic guardrail metric. Instead it integrates with Mixpanel, Amplitude, Segment, and similar tools so your analytics vendor does the measurement. If you want the flag and the statistics in one system, GrowthBook, Statsig, and PostHog are built that way and Flagsmith is not.

Best for

Engineering teams at small software companies who want a dependable feature flag and remote config service with published pricing that starts at zero, and especially teams who want the option to self-host the same product on their own infrastructure rather than take a hard runtime dependency on a vendor.

Not the right fit for

Teams who want the experiment statistics in the same tool as the flag; Flagsmith splits traffic but does not compute significance, so if you want sequential testing or variance reduction you should be looking at GrowthBook, Statsig, or PostHog instead.
Product managers who want to run tests without engineering involvement; there is no visual editor and no WYSIWYG page variant builder, so every change is a code path that a developer wrote.
Anyone shopping for session replay or heatmaps; Flagsmith has no recording product at all and never will, so this is the wrong shelf entirely if that is the requirement.
Small teams with no operations capacity who are attracted to the self-hosted option for cost reasons; running Postgres, Redis, and the API yourself will cost more in engineering hours than the $40 a month plan.
Buyers who need a single vendor covering analytics, flags, replay, and error tracking on one invoice; Flagsmith is deliberately a component and expects you to own the integration work.

How it works

1
You create an organisation, a project, and then environments inside that project, typically development, staging, and production. A flag created in the project exists in every environment with an independent value, which is why the same feature can be on for your team and off for customers without any branching in code.
2
Your application installs an SDK. Client-side SDKs cover JavaScript, React, React Native, Flutter, Android and Kotlin, Swift and iOS; server-side SDKs cover Node, Python, Java, .NET, Go, PHP, Ruby, and Rust, and Flagsmith is compatible with the vendor-neutral OpenFeature specification if you would rather program against that interface.
3
At runtime the SDK asks for flags either anonymously, which returns the environment defaults, or for a named identity with traits attached, which runs the segmentation rules and returns that user's answers. Segments are rule sets over traits, so you can express things like beta testers, accounts on a particular plan, users in a given country, or a percentage bucket that stays consistent for the same identity.
4
Client requests go to the Edge API, which replicates the rules engine across eight AWS regions using Lambda@Edge and DynamoDB global tables with latency-based routing and regional failover, so a flag evaluation from Sydney does not round trip to London. Server-side SDKs can instead poll and cache the whole environment document locally, which removes the network call from the hot path entirely, and a self-hostable Edge Proxy does the same job for a fleet of services.
5
Around the flags sit the governance features: scheduled flag changes, change requests with approvals, role based access control, audit logs, and webhooks. Integrations push flag state outward to analytics and observability tools so a chart can be split by which variant a user saw, and a Terraform provider lets flag configuration live in the same repository as the rest of your infrastructure.

Feature breakdown

28 features in 5 modules

Flags and remote configuration

The core primitives, and the part that is free and unlimited.

Boolean flags: The basic on and off switch per environment, with unlimited flags on every tier including the free one, so nobody is ever rationing flags to stay under a plan limit.
Remote config values: A flag can carry a string, integer, or JSON payload as well as an enabled state, which is how teams change copy, thresholds, and feature parameters in a shipped mobile app without an app store release.
Multivariate flags: A single flag can hold several values with percentage weights, giving you consistent bucketing per identity for A/B/n rollouts. Flagsmith splits the traffic; the measurement happens in your analytics tool.
Environments: Development, staging, and production each hold independent values for the same flag, and environments are unlimited on every tier including free.
Scheduled flag changes: Set a flag to flip at a future time, available from the Start-Up tier, which covers timed launches without someone staying up to press a button.
Kill switches: Because evaluation is a runtime lookup rather than a deploy, disabling a broken feature is a single toggle that propagates to clients in seconds rather than a rollback and redeploy cycle.

Targeting, identities, and segments

How a flag becomes a per-user decision rather than a global one.

Identities and traits: Send a user identifier with arbitrary key and value traits, and Flagsmith stores them so targeting rules can be written against plan, signup date, country, or anything else you attach. Unlimited on all tiers.
Segments: Reusable rule sets over traits, combined with and and or logic, so beta testers or enterprise accounts are defined once and referenced by many flags.
Percentage rollouts: Deterministic bucketing by identity means the same user keeps the same answer as you ramp from 1 percent to 100 percent, which is the difference between a rollout and a random flicker.
Per-identity overrides: Force a specific user into a specific flag state, which is how support unblocks one customer without changing anything for everyone else.
Feature-specific segment overrides: A segment can override a flag value only for that flag, so the same segment behaves differently across features without duplicating the rules.

Delivery architecture

The engineering that decides whether flags add latency to your app.

Global Edge API: The rules engine runs on Lambda@Edge with DynamoDB global tables replicated across eight AWS regions including London, Ohio, Northern California, Mumbai, Sydney, Seoul, Singapore, and Sao Paulo, with latency-based routing and failover if a region goes down.
Local evaluation in server SDKs: Server-side SDKs can pull the whole environment document and evaluate rules in process, so flag checks cost microseconds and a Flagsmith outage does not stall your request path.
Edge Proxy: A self-hostable proxy that caches environment documents and serves your own fleet, useful when you have many services or want evaluation to stay inside your network perimeter.
Real-time flag updates: Clients can be notified when an environment changes rather than waiting for the next poll, which is what makes a kill switch feel instant.
OpenFeature compatibility: Flagsmith supports the vendor-neutral OpenFeature specification, so application code can be written against a standard interface and the provider swapped later without rewriting call sites.
REST API and Terraform provider: Everything the dashboard does is available over the API, and a Terraform provider lets flags and segments be declared as code alongside the rest of your infrastructure.

Governance and administration

The features that gate the jump from $40 to $250 a month.

Change requests and approvals: Flag changes can require review before they take effect, which is the control most auditors ask about once production toggles exist. Scale-Up tier and above.
Role based access control: Roles and granular permissions across projects and environments, so a contractor can change development but not production. Scale-Up tier and above.
Audit logs: A record of who changed which flag and when, exportable and available to webhooks, which is the other half of the compliance answer.
SAML and SSO: Single sign on arrives at the Scale-Up tier at $250 a month, with LDAP and SCIM reserved for Enterprise.
Two factor authentication: Available from the Start-Up tier, which is unusually low for this category.

Self-hosting and integrations

The open source escape hatch and the tools that do your measurement.

Open source self-hosted deployment: The codebase is public and deployable with Docker Compose for evaluation or Helm charts and Kubernetes operators for production, with Postgres as the primary datastore and Redis for caching. Guides exist for AWS, Google Cloud, and Aptible.
Private cloud and on-premises hosting: Flagsmith will run a fully managed private deployment or support an on-premises install under the Enterprise tier, which is how regulated buyers get the product without the shared cloud.
Analytics integrations: Flag state and events push to analytics tools including Mixpanel, Amplitude, Segment, and Heap, which is where any actual experiment analysis happens since Flagsmith does not compute results itself.
Observability integrations: Connections to APM and error tools such as Datadog, New Relic, and Sentry so an exception can be correlated with the flag configuration that produced it.
Workflow integrations: GitHub, Jira, Slack, and webhooks connect flag changes to the systems where the rest of the release conversation happens.
Flag analytics: Usage tracking shows which flags are actually being evaluated, which is the practical way to find the stale flags that should have been deleted eighteen months ago.

Use cases

4 documented

Four-person engineering team shipping to production daily

Long-lived feature branches keep colliding, and every risky change turns into a release day where somebody watches dashboards with a rollback plan.

Features merge to main behind flags that default to off, get enabled for the team first, then a percentage of users, and a kill switch replaces the rollback plan. The Start-Up plan at $40 a month covers a million evaluations.

Mobile team stuck behind app review

A hardcoded API timeout and a piece of onboarding copy are wrong in the shipped iOS build, and fixing them means a new binary and a multi-day review queue.

Both values move into Flagsmith remote config, so they change from the dashboard and take effect on the next app launch with no release at all.

B2B SaaS gating features by plan

Entitlement logic is scattered through the codebase as plan name comparisons, and every new tier means touching a dozen files.

Plan becomes a trait on the identity, entitlements become segments, and the code asks Flagsmith whether the feature is on rather than reasoning about plan names.

Team with a data residency requirement

A customer contract forbids user identifiers leaving the company's own infrastructure, which rules out most hosted flag vendors.

Flagsmith is deployed self-hosted on the team's Kubernetes cluster with the same SDKs, or server-side SDKs run in local evaluation mode so identities never leave the application process.

Pricing

from $0 (Free), then $40 per month billed yearly (Start-Up)

Freemium subscription metered on API requests per month with a seat cap per tier, plus a free open source self-hosted edition and an Enterprise tier for private or on-premises hosting.

Plan	Price	Includes
Free	$0 per month	50,000 API requests per month 1 team member Unlimited flags, environments, identities, and segments Full REST API access Overage from $50 per additional million requests Genuinely usable for a solo developer or a side project; the single seat is what forces the upgrade, not the request cap.
Start-Up	$40 per month billed yearly ($45 monthly)	1,000,000 API requests per month 3 team members Unlimited projects Scheduled flags, A/B and multivariate testing, two factor authentication Third-party integrations and email support The tier most small teams should be on. A million requests is a lot when server SDKs evaluate locally.
Scale-Up	$250 per month billed yearly ($300 monthly)	5,000,000 or more API requests per month 5 team members included, expandable to 20 at $50 to $60 per member per month SAML and SSO Roles, permissions, change requests, and audit logs Priority support The jump from $40 to $250 buys governance and SSO rather than capability; be honest about whether you need approvals yet.
Enterprise	Custom quoted	Tailored hosting: cloud, private cloud, or on-premises 20 or more team members LDAP and SCIM provisioning Real-time priority support with an SLA Onboarding assistance
Open source self-hosted	$0 plus your own infrastructure cost	Full codebase deployable via Docker Compose, Helm, or Kubernetes operators No request metering Postgres plus Redis to operate Community support only Some governance features reserved for the commercial Enterprise edition Free in licence terms, not in engineering hours; budget an ongoing operational cost, not a one-off setup.

Billing notes

The meter is API requests, not seats and not monthly tracked users, so a chatty client-side integration costs more than a well-cached server-side one for exactly the same user base.
Overage is charged at $50 per additional million requests across the paid tiers, which is predictable but adds up if you poll aggressively from the browser.
Annual billing saves roughly 11 percent on Start-Up and 17 percent on Scale-Up compared with paying monthly.
Seats are capped rather than unlimited, and Scale-Up charges $50 to $60 per member per month beyond the five included, so a ten-person engineering team should model the seat cost as well as the request cost.
Flagsmith states that special rates are available for open source projects and nonprofits on request.
Self-hosting removes the request meter entirely, which is why high-volume consumer apps with operations staff often end up there.

Value assessment: At $40 a month for a million requests and three seats, Flagsmith is among the cheapest credible flag services available, and the free tier is a real product rather than a teaser. Modelling a bill is straightforward once you understand the meter. A product with 10,000 monthly users evaluated through server-side SDKs in local evaluation mode generates almost no billed requests at all and sits comfortably on Start-Up at $40. The same product at 100,000 monthly users, evaluated from the browser at a handful of requests per user per month, plausibly lands between 1 and 5 million requests, which means Start-Up plus overage at $50 per million or a move to Scale-Up at $250. The uncomfortable part of the curve is not volume, it is governance: SSO, change requests, and audit logs all sit behind the $250 tier, so a team that needs approvals pays six times more for the same flags. Compared with LaunchDarkly's per-seat and per-connection model the total is usually far lower, and compared with GrowthBook you are paying less but getting no statistics engine.

Strengths & limitations

Strengths

Unlimited flags, environments, identities, and segments on every tier including free, so the plan limit is a request meter rather than an artificial cap on how you model your product.
A genuine open source self-hosted edition with Docker, Helm, and Kubernetes operator paths, which gives you an exit and satisfies data residency requirements no hosted-only vendor can meet.
The Edge API is real infrastructure rather than a marketing claim: eight AWS regions, Lambda@Edge, DynamoDB global tables, latency routing, and regional failover.
Local evaluation in server-side SDKs removes Flagsmith from your request path entirely, which is the correct answer to the availability objection every engineer raises about flag services.
OpenFeature compatibility and a Terraform provider mean flag configuration can live as code and the vendor can be swapped without rewriting application call sites.
Bootstrapped and profitable with roughly 26 to 30 staff, which makes for a vendor with no pressure to reprice around a funding round.
Pricing is fully published including overage rates, and both paid tiers can be bought with a card and a 14 day trial rather than a sales call.

Limitations

No experiment analysis engine. Flagsmith splits traffic and stops there; there is no sequential testing, no CUPED, no automatic significance calculation, and no guardrail metrics, so measurement lives in another vendor.
The free tier is limited to a single team member, which means any collaboration at all requires the paid plan regardless of how few requests you make.
SSO, change requests, role based access control, and audit logs are gated to the $250 Scale-Up tier, a six times price increase over Start-Up for governance features rather than product capability.
The self-hosted edition is free to license but requires you to run and upgrade Postgres, Redis, and the API, and some enterprise governance features are not in the open source build.
No visual editor or no-code targeting UI, so this is a tool for engineering teams and a product manager cannot run anything without a developer.
Data residency on the hosted Edge API is about latency across eight regions rather than a contractual guarantee that data stays in one of them; buyers with strict residency terms should assume self-hosting is the answer.
Seat caps on every tier make it more expensive than the headline suggests for teams above five engineers.

Head-to-head comparisons

5 alternatives

Flagsmith vs GrowthBook

from $0 (Starter, 3 seats), then $40 per seat per month (Pro)

Both are open source with a free hosted tier, but they draw the line in different places. GrowthBook computes experiment results against your own warehouse with Bayesian and sequential analysis and charges $40 per seat; Flagsmith charges $40 for the whole team at Start-Up but leaves measurement to your analytics vendor. Pick GrowthBook if experiments are the reason you want flags; pick Flagsmith if you want release control and already have analytics you trust.

Full Flagsmith vs GrowthBook comparison

Flagsmith vs Unleash

from $75 per seat per month (Pay-As-You-Go cloud)

The two closest open source rivals. Unleash charges $75 per seat on its pay-as-you-go cloud with 53 million monthly requests included and puts SSO, RBAC, and approvals in the base plan; Flagsmith starts far cheaper at $40 for three seats but gates that same governance behind the $250 tier. A three-person team saves a lot with Flagsmith; a team that needs approvals and SSO on day one may find Unleash's bundle simpler.

Full Flagsmith vs Unleash comparison

Flagsmith vs LaunchDarkly

from $0 (Developer), then pay-as-you-go from $8.33 per 1,000 client-side monthly active users per month billed yearly (Foundation)

LaunchDarkly is the enterprise default and now ships observability, session replay, and error tracking alongside flags, with unlimited seats and metering on monthly active users and service connections. Flagsmith is the smaller, cheaper, inspectable alternative with a self-hosting path LaunchDarkly does not offer at the low end. Choose LaunchDarkly for breadth and ecosystem, Flagsmith for cost control and sovereignty.

Full Flagsmith vs LaunchDarkly comparison

Flagsmith vs Statsig

from $0 (Developer), then $150 per month (Pro)

Statsig is an experimentation platform that happens to include flags, with a serious statistics engine covering sequential testing and CUPED, priced on analytics events. Flagsmith is a flag service with no statistics at all. If your organisation runs real experiments and needs defensible results, Statsig is a different class of product; if you just need to control releases, Flagsmith costs a fraction of it.

Full Flagsmith vs Statsig comparison

Flagsmith vs PostHog

from $0 (generous monthly free tiers; pay only past the allowance)

PostHog bundles product analytics, session replay, flags, and experiments on one usage-based bill, and its flag product is competent and free at low volume. Flagsmith is better as flag infrastructure specifically: an Edge API across eight regions, local evaluation, an Edge Proxy, and a self-hosting story. Teams who want one invoice should take PostHog; teams for whom flag delivery is a production concern rather than a convenience should take Flagsmith.

Full Flagsmith vs PostHog comparison

Implementation & onboarding

Setup time: An hour to a first flag in production. Create a project and environments, install the SDK, wrap one code path, and ship. The work that takes longer is deciding on naming conventions and who is allowed to change production.
Learning curve: Low for developers and effectively unavailable to non-developers. The mental model is small: environments hold values, identities carry traits, segments are rules over traits. The subtlety worth learning early is the difference between remote and local evaluation, because it determines both your latency and your bill.
Onboarding: Entirely self-serve including the paid tiers, with a 14 day trial on Start-Up and Scale-Up. Enterprise adds onboarding assistance. Documentation includes per-language quick starts for React, Flutter, Android, iOS, Go, PHP, Ruby, .NET, Java, and Spring Boot.
Migration notes: Because Flagsmith supports OpenFeature, teams already programming against that interface can switch providers by changing configuration rather than code. Coming from another vendor, flags themselves are trivial to recreate through the REST API or Terraform provider; the real migration cost is the targeting rules and the identity traits behind them, which have to be re-expressed as Flagsmith segments. Moving between Flagsmith Cloud and a self-hosted install is supported and is the more common migration in practice.

Platform, API & security

Platforms: JavaScript and ReactReact Native and FlutteriOS and SwiftAndroid and KotlinNodePythonJava and Spring Boot.NETGoPHPRubyRustOpenFeature providers
API: Full REST API covering everything in the dashboard, plus webhooks, a Terraform provider, and a self-hostable Edge Proxy. The Edge API endpoint runs the rules engine on Lambda@Edge across eight AWS regions.
Compliance: GDPREnterprise security review supported; confirm the current SOC 2 and ISO 27001 scope with the vendor during procurement
Data residency: The hosted Edge API replicates across eight AWS regions including Europe (London) with latency-based routing, which is a performance architecture rather than a residency guarantee. Buyers with contractual residency requirements should use the self-hosted or private cloud deployment, or run server-side SDKs in local evaluation mode so identity data never leaves their infrastructure.
SSO: SAML and SSO from the Scale-Up tier at $250 a month; LDAP and SCIM on Enterprise. Two factor authentication is available from Start-Up.
Security notes: Server-side local evaluation means user identifiers and traits can stay inside your own process rather than being sent to Flagsmith at all, which is the strongest privacy posture available from any hosted flag vendor. Audit logs, change requests, and role based access control provide the change-control trail, all from the Scale-Up tier.

Support & resources

Channels: Email support from the Start-Up tierPriority support on Scale-UpReal-time priority support with an SLA on EnterpriseCommunity Discord and GitHub issues
Documentation: Extensive documentation at docs.flagsmith.com covering per-language SDK guides, Edge API architecture, self-hosting on Docker, Kubernetes, AWS, Google Cloud and Aptible, integrations, and platform administration.
Community: Active open source community on GitHub with public issues and contributions, plus a Discord channel. The founders host a podcast about open source businesses, which is an unusually visible signal of where the company's attention sits.

Company

Founded: 2018
Headquarters: London, United Kingdom
Ownership: Bootstrapped, privately held (legal entity Bullet Train Ltd)
Founders: Ben Rometsch, Kyle Johnson
Employees: Approximately 26 to 30 (2026)
Funding: Bootstrapped with no meaningful venture capital; reported outside funding is under $250K and the company has been profitable rather than growth-funded.

Timeline

2018Founded in London by Ben Rometsch and Kyle Johnson as a spin-out from their digital agency, originally released as an open source project called Bullet Train because their own engineers needed self-hostable feature flags for client work.
2020The product is renamed Flagsmith while the legal entity remains Bullet Train Ltd, and the hosted cloud service is commercialised alongside the open source codebase.
2022The Edge API launches, moving flag evaluation onto Lambda@Edge with DynamoDB global tables replicated across eight AWS regions to cut evaluation latency outside Europe.
2023Governance features mature: change requests, role based access control, scheduled flags, and audit logs land on the higher tiers as the product moves upmarket without abandoning the free path.
2024OpenFeature provider support and a Terraform provider ship, making Flagsmith addressable as infrastructure as code and reducing the switching cost in both directions.
2026Still bootstrapped at roughly 26 to 30 people, with published pricing from free to a $250 Scale-Up tier and self-hosted, private cloud, and on-premises deployments offered alongside the eight-region cloud.

Integrations

Mixpanel
Amplitude
Segment
Heap
Datadog
New Relic
Sentry
Slack
GitHub
Jira
Webhooks
Terraform provider
OpenFeature

Frequently asked questions

10 questions

What is Flagsmith?

Flagsmith is an open source feature flag and remote configuration platform. It lets you turn features on and off per environment, per segment, or per individual user at runtime rather than by deploying new code, using SDKs for roughly a dozen languages. It is available as a hosted service starting free for 50,000 API requests a month, and as a self-hosted deployment you run yourself.

How much does Flagsmith cost?

The Free tier is $0 for one team member and 50,000 API requests a month. Start-Up is $40 a month billed yearly, or $45 monthly, for three members and a million requests. Scale-Up is $250 a month billed yearly, or $300 monthly, for five members and five million or more requests, and adds SSO, roles, change requests, and audit logs. Enterprise is quoted. The self-hosted open source edition has no licence fee.

Does Flagsmith run A/B tests?

Only halfway, and this is the most important thing to understand before buying. Flagsmith can split traffic across multivariate flag values with consistent per-identity bucketing, so it can serve an experiment. It does not compute results: there is no significance calculation, no sequential testing, no CUPED variance reduction, and no guardrail metrics. Analysis happens in whatever you integrate with, typically Mixpanel, Amplitude, Segment, or Heap. If you want flags and statistics in one product, look at GrowthBook, Statsig, or PostHog.

What exactly counts as an API request?

A call from an SDK asking Flagsmith for flag values. This matters because architecture changes your bill more than user count does. A browser SDK asking on every page load generates many requests per user; a server-side SDK running in local evaluation mode pulls the environment document periodically and evaluates rules in process, generating almost none. Two products with identical traffic can differ by an order of magnitude on the meter.

What would Flagsmith cost at 10,000 or 100,000 monthly users?

At 10,000 monthly users with server-side local evaluation, you are effectively paying for seats: the Start-Up tier at $40 a month, with request volume nowhere near the million included. At 100,000 monthly users evaluated from the browser at a few requests each per month, expect somewhere between one and five million requests, which means Start-Up plus overage at $50 per million, or Scale-Up at $250. Caching and local evaluation are the levers that decide which end of that range you land on.

Is self-hosting Flagsmith actually free?

Free in licence terms, not in cost. You deploy the open source codebase with Docker Compose, Helm, or the Kubernetes operator, and then you own a Postgres database, a Redis cache, the API processes, upgrades, backups, and monitoring for as long as you use it. For most small teams that operational load is worth more than the $40 a month plan. Self-hosting makes sense when data residency, request volume, or a policy against external runtime dependencies makes it a requirement rather than an economy.

Does Flagsmith add latency to my application?

It does not have to. Client-side SDKs hit the Edge API, where the rules engine runs on Lambda@Edge with DynamoDB global tables replicated across eight AWS regions with latency-based routing, so evaluations resolve near the user. Server-side SDKs can go further and evaluate locally in process after pulling the environment document, which removes the network call from the request path entirely and means a Flagsmith outage does not stop your application from serving traffic.

Can I keep user data out of Flagsmith for GDPR reasons?

Yes, and this is one of its better answers. Running server-side SDKs in local evaluation mode means identity traits are evaluated inside your own process and never sent to Flagsmith. If you need a stronger guarantee, the self-hosted or private cloud deployment keeps everything on your infrastructure. The eight-region hosted Edge API is a latency architecture rather than a residency contract, so do not read regional replication as a residency commitment.

How does Flagsmith compare with LaunchDarkly?

LaunchDarkly is the larger, broader product, now bundling observability, session replay, and error tracking with flags and metering on monthly active users and service connections with unlimited seats. Flagsmith is narrower, considerably cheaper at the small end, open source, and self-hostable. Teams that want an enterprise ecosystem with deep integrations take LaunchDarkly; teams that want cost control, inspectable code, and the option to run it themselves take Flagsmith.

Who owns Flagsmith and is it a stable vendor?

Flagsmith was founded in London in 2018 by Ben Rometsch and Kyle Johnson, spun out of their digital agency, and trades through Bullet Train Ltd. It is bootstrapped rather than venture-backed, with roughly 26 to 30 staff. That means no funding-round repricing risk and no pressure to chase a growth curve, but also a smaller company than most of its competitors. The open source codebase is the practical hedge: if the company disappeared tomorrow, you could keep running it.

Editorial verdict

Flagsmith is the sensible feature flag purchase for a small engineering team that wants release control without an enterprise contract. Unlimited flags and environments on every tier, a real Edge API across eight regions, local evaluation that keeps the vendor out of your request path, and an open source codebase you can run yourself add up to more infrastructure quality than the $40 a month price suggests. Buy it if your problem is shipping safely: dark launches, percentage rollouts, kill switches, remote config for mobile. Do not buy it expecting experimentation, because the statistics simply are not there and pretending otherwise leads to teams shipping on gut feel with a flag as decoration. Watch two things during evaluation: whether your integration is chatty enough to blow past the request meter, and whether you will need SSO and approvals soon, because that governance jump takes you from $40 to $250 without adding a single product capability.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.