Flagsmith

Overview

Flagsmith lets teams control feature availability by environment, user, segment, or a percentage of users. That makes it useful for gradually widening a release instead of exposing a feature to everyone at once. Multivariate flags add percentage splits for A/B and multivariate testing, while remote configuration lets teams change properties such as text, colors, and behavior without deploying new code.

Teams can choose hosted cloud, private cloud, or self-hosted deployment. The maker says core feature-flag functionality is open source and most of the product is under the BSD-3 licence. It also states that Flagsmith is SOC 2 Type 2 accredited and that its self-hosted instance supports HIPAA, FedRAMP, and ISO 27001. Bullet Train Ltd., the company behind Flagsmith, is based in London, England.

Key features

• Targeted rollouts: Environment, user, segment, and percentage targeting give teams several ways to limit exposure during a release. This is useful for staged launches, though the value depends on having a team ready to define and manage those targeting rules.
• Experiments and remote configuration: Multivariate flags support traffic splits across variations; remote configuration covers changes to selected feature properties without a new code deployment. Together they suit teams managing both feature availability and variations in product behavior.
• Integrations and webhooks: Listed integrations include Amplitude, Datadog, GitHub, GitLab, Grafana, Jira, Mixpanel, OpenFeature, Segment, Sentry, Slack, and Terraform. Environment-level webhooks can send events to a team’s own infrastructure, giving teams ways to connect Flagsmith with existing tools and systems.
• Deployment and governance: Hosted cloud, private cloud, and self-hosting provide deployment choice. Scale-Up adds SAML/SSO, roles, permissions, change requests, and audit logs, which are more relevant to teams that need access controls and a record of changes than to small teams starting out.

SDK languages include JavaScript, React, Next.js, Android/Kotlin, iOS/Swift, Flutter, Python, Java, .NET, Node.js, Ruby, PHP, Go, Rust, and Elixir. That breadth makes Flagsmith relevant to teams working across a range of common application stacks.

Pricing

Flagsmith has a free plan, paid plans from $40.00 USD per month on yearly pricing, and a 14-day trial. Both paid plans require 12 months to be paid up front, so the monthly price is not a month-to-month commitment.

Free is a practical way for one person to start, with generous flexibility around flags and environments, but its 50,000 monthly requests, single project, and single-member limit constrain shared or higher-traffic work. Users who exceed the request limit have seven days to upgrade before action is taken. Start-Up raises the request allowance and supports three members, making it a better fit for a small team; its trade-offs are the annual upfront bill and the absence of the governance and priority-support features included at higher tiers. Scale-Up is aimed at teams that need those controls, higher request capacity, and room for up to 20 members. Enterprise suits larger or infrastructure-specific deployments, but requires a sales conversation for pricing.

Platforms

Flagsmith supports Android, iOS, Linux, macOS, Windows, web, API, and self-hosted deployments. Its SDK language coverage spans client and server environments, so teams can use the platform across mobile, web, and backend projects.

Who it's for

Flagsmith is a strong fit for development teams that want staged feature releases, user targeting, experiments, and remote configuration in one product. Teams with specific hosting requirements may value the private-cloud and self-hosted choices, while organizations needing SSO, change requests, and audit logs should consider Scale-Up or Enterprise. It is less compelling for a team that needs multiple collaborators on a free plan or cannot commit to annual upfront billing for paid service.

Pros and cons

• Pro: Targeting by environment, user, segment, or percentage supports controlled rollouts at different levels of granularity.
• Pro: Remote configuration and multivariate testing extend the product beyond simple on/off feature flags.
• Pro: Hosted, private-cloud, and self-hosted deployment give teams different infrastructure options.
• Pro: The free plan includes unlimited flags, environments, identities, and segments, despite caps on requests, projects, and team members.
• Con: Free is restricted to one team member and one project, limiting collaboration and project breadth.
• Con: Start-Up and Scale-Up are billed for 12 months upfront, which raises the commitment compared with a monthly payment option.
• Con: Governance features and priority support sit at Scale-Up, so teams needing those capabilities face a substantially higher listed monthly price than Start-Up.

Alternatives

Consider ConfigCat if its free plan’s 10 flags, two environments, two products, and allowance of 5 million config JSON downloads per month better match your needs. Choose feat if a free plan with 7,500 MAU, 100 server connections, two projects, unlimited environments, and unlimited flags is a better fit. Featureflow is another freemium option, with a free tier that includes up to five seats, one project, two environments, 1 million SDK requests per month, and a seven-day audit trail.

Flipt may suit teams looking for a free open-source option with Git-native workflows, Git sync, and real-time updates. Bucketeer is a free, open-source, self-hosted alternative without per-seat pricing. DevCycle has a free plan with separate client-side MAU and cloud and server config request allowances. GrowthBook offers a free self-hosted option with one project, unlimited feature flags, experiments, and traffic. LaunchDarkly Experimentation is another freemium option, with a free Developer plan that includes 100K experimentation MAU per month, one project, three environments, and A/B tests and experiments.

Browse Feature Flag Software or Release Management Software for more options in those categories.

Verdict

Choose Flagsmith if your team needs controlled rollouts and remote configuration, particularly if deployment flexibility or later-stage governance matters. The free plan offers a useful starting point for an individual, but its one-member cap and request limit make it a poor choice for a growing team; paid plans add capacity at the cost of an annual upfront commitment.