Flagsmith Reviews

Flagsmith has been a very useful tool for me over the past years, and I have used it for more than 10 projects based on different tech stacks including Java, Python, Go, and JavaScript. The integration was extremely seamless, and these are large-size projects with multiple features. The best part about it is the extremely low latency and high availability of the system. Local feature flag evaluation mode proved to be a game-changer, allowing me to quickly check all feature flag values without any additional delay. Overall, Flagsmith has made feature flagging and A/B testing mechanisms so simple to implement that it's the first name that comes to my mind when I hear about feature flagging. Flagsmith already supports most of the programming languages and is building so many new integrations that every time I visit their website, there is something new.

Flagsmith has positively impacted my organization because it has made feature toggling so easy that all my new feature rollouts are gated behind a Flagsmith feature flag. The toggling is easy to do, allowing the product and design teams to independently play around with A/B testing and gather metrics, thereby reducing developer involvement further. It has helped me avoid the whole burden of setting up a new server to manage my application's feature flag.

Flagsmith has improved development efficiency by allowing my team to release features gradually, test changes in a controlled manner, and disable problematic features without needing a full code deployment. This has reduced deployment risk, simplified troubleshooting, and given my developers more flexibility during releases.

The deployment efficiency and release flexibility has improved from 40% to 80% since using Flagsmith.

I love the Flagsmith user interface, which is so easy to understand and get onboarded, making it super convenient to use for both developers and non-technical folks.

Flagsmith offers support for a wide variety of programming languages, powerful segmentation for targeted rollouts, analytics to track feature performance, and security features such as audit logs and role-based controls.

The user interface is very intuitive and easy to navigate, making it easy for new people to learn or get onboarded quickly, both for technical and non-technical users.

Flagsmith provides useful governance and security capabilities for managing feature flags, including role-based access controls, permissions, and audit logging to help my team manage changes and maintain accountability.

Flagsmith's accuracy and reliability come primarily from its feature flag management and controlled release capabilities rather than dedicated AI functionality, helping my development team manage feature rollouts, target specific user groups, and quickly disable features when issues arise.

Flagsmith integrates well into my AWS-based development environments through its APIs, SDKs, and deployment flexibility.

The Flagsmith user interface and dashboard are very intuitive, but I wish the environment could be merged so that I can create a flag and decide the values for each environment without switching around.

I have been using Flagsmith for the past seven years.

Flagsmith is stable, especially when managing huge data. It helps teams control feature releases, manage configurations across environments, and roll out updates gradually while maintaining high performance with minimal downtime.

Flagsmith is very scalable because it offers good scalability for teams in my organization as my application users and feature management requirements have grown gradually.

The support experience with Flagsmith has been positive. The documentation and technical resources provide useful guidance for deployment, configuration, SDK integration, and troubleshooting.

Before using Flagsmith, I relied heavily on custom feature flag implementations and environment-based configurations to manage feature releases. I moved to Flagsmith to centralize feature flag management, simplify configuration, and gain better control over gradual rollouts and user targeting.

Deploying Flagsmith is relatively easy, aided by clear documentation and flexible deployment options that facilitate integration into my development environment.

The configuration process with Flagsmith is relatively straightforward and flexible. The user interface makes it easy to create and manage feature flags, configure environments, define targeting rules, and control feature availability for different user groups.

Using Flagsmith in my organization has definitely been a game-changer and an advantage for me because it has delivered a positive return on investment by improving my development efficiency, reducing the risks associated with software releases, and simplifying feature management.

Although I wasn't involved in the procurement process for Flagsmith, I found it to be relatively straightforward and convenient. The available pricing information and subscription options made it easier to evaluate the solution against my development requirements and budget.

The metering and billing experience with Flagsmith is very convenient for me, making it easy to understand the subscription cost and plan for ongoing usage.

Flagsmith offers flexible pricing and licensing options that accommodate different team sizes and project requirements. The setup cost is very manageable, especially when using the hosted option, while self-hosted deployments may require additional infrastructure and maintenance resources.

I would rate Flagsmith a five out of five.

I chose five out of five because working with Flagsmith has been a fantastic experience; everything has been good. The product is top-notch, high quality, reliable, and well-designed. The support team has also been incredibly responsive and helpful, making implementation smooth and hassle-free. It has been a pleasure collaborating with them, and I highly recommend Flagsmith to anyone looking for a robust feature flagging solution.

I recommend Flagsmith to teams looking to improve feature management, streamline software releases, and reduce deployment risk. Before getting started, take time to understand your feature management requirements, evaluate the available deployment options, and choose the plan that best fits your team's needs and budget. I also advise starting with a small project to learn how feature flags, environments, user targeting, and gradual rollouts work before expanding across multiple applications and larger projects.

My main use case for Flagsmith is to manage feature flags and control how new features are released to the team. We can enable and disable features without deploying new code for every new change and roll out functionality to selected users.

For example, we have a software platform that we manage, which enables and disables certain features like integration accessibility and white-label functions. We can enable and disable them directly from Flagsmith rather than implementing them manually.

Flagsmith has positively impacted my organization by helping us release new features in our software platform more safely and more frequently. We can also test new features with internal users before making them available to everyone.

I have noticed specific outcomes, such as reduced release risk and minimized unnecessary development work since I started using Flagsmith.

The best features Flagsmith offers are the feature flags and environment-specific configurations. Additionally, the ability to disable problematic features quickly is valuable.

Environment-specific configurations have helped my workflow because we have a sandbox environment and a live production environment. We can manage specific features in our sandbox environment and control both environments with Flagsmith before putting features into our production environment.

Regarding how Flagsmith can be improved, I think more advanced built-in analytics and experimentation capabilities would be beneficial for our development teams. Additionally, managing flags in different environments could be more streamlined.

The cleanup of obsolete feature flags once we have fully released those features would benefit from more attention to manage that process.

I have been using Flagsmith for four years.

Flagsmith is quite stable.

I consider Flagsmith to be quite scalable in terms of organizations that are growing from small projects into larger ones. It also supports multiple projects and environments.

The customer support is quite responsive and has very good technical knowledge, which is encouraging, especially when integrating and troubleshooting release management issues.

I would rate the customer support a 10 on a scale of one to 10.

I have seen a return on investment as we have saved a lot of time for our developers. Rather than requiring developers to switch on and turn off features in the platform, non-developers can also take control. In certain situations where developers are busy, our product team can also use Flagsmith to release features between environments. I would say we have saved a lot of time and effort.

My experience with pricing, setup cost, and licensing is quite smooth.

On a scale of one to 10, I would give Flagsmith a 10.

I chose 10 out of 10 because Flagsmith has made managing software releases for a platform as complicated as ours much easier. It has taken a lot of load off our developers and even product owner teams. We have reduced a lot of maintenance work for our developers. Flagsmith has really helped our teams save a lot of time and energy.

Flagsmith is deployed in my organization through a private cloud. We use Exna as our cloud provider.

My advice to others looking into using Flagsmith is to try Flagsmith with a real development project before committing to a paid plan. Test integrations and SDKs before going into it.