Flagsmith, from the company of the same name in London, allows users to manage feature flags across web, mobile and server side applications in order to deliver true Continuous Integration and get builds out faster, as well as control who has access to new features. Flagsmtih offers a hosted API, or it can be deployed to a private cloud, or run on-premise.
N/A
Statsig
Score 8.9 out of 10
N/A
Statsig is a feature management with feature flags, pulse, holdouts, from the company of the same name in Bellevue.
N/A
Pricing
Flagsmith
Statsig
Editions & Modules
No answers on this topic
Enterprise
Custom
annual pricing
Offerings
Pricing Offerings
Flagsmith
Statsig
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Flagsmith
Statsig
Considered Both Products
Flagsmith
No answer on this topic
Statsig
Verified User
Project Manager
Chose Statsig
Statsig is easier to use and has more tools for analysis, though we were working with the open source version of Flagsmith, merely to handle feature flags, and using Heap and homegrown tools for manual analysis, so the Cloud version may be different
Flagsmith is the best tool I worked with for feature flags, in terms of how easy and intuitive it is to use. On the other hand, it has all the features we need to effectively manage features.
This is clearly a platform built around experimentation first, and it shows. In this way Statsig is way ahead of the competition of products I've used previously! It's more data science focussed which makes configuration of new experiments complex with a learning curve.
For the most part it is pretty easy to use. - There are some quirks with the javascript SDK (getExperiment().getValue?). - The Events vs. Metrics design pattern is complex, and creating new Metrics from Events can be frustrating if you are trying to use event metadata - It's really frustrating not to be able to link Static IDs (before a user signs up) to User IDs, in order to follow users all the way through onboarding, or to log events that occur for signed in users when you are exposing the experiment to users before they've signed up