What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Flagsmith for four years.
What do I think about the stability of the solution?
Flagsmith is quite stable.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is quite smooth.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other