flagsmith VS flipper

Considering all these points, the team at Flagsmith has developed a feature flag management platform Flagsmith and made it open source. The core functionality is open and you can check out the GitHub repository here. I have utilized and authored several blogs discussing their excellent offerings and strategies.

It’s also open source! Check out the repo here and don't forget to give it a star to show your support and join their amazing community to get technical support.

In this guide, we've chosen Flagsmith as our feature flagging solution. Flagsmith is an open-source platform that offers a user-friendly interface for managing feature flags, A/B testing, and segment overrides. You can control feature behaviour without modifying code, making it a powerful tool for managing complex projects with multiple feature variations.

Looks good. My friend launched Flagsmith a few years back too -https://github.com/Flagsmith/flagsmith. I have used it on a few of my own projects and it’s been great/easy to integrate

Is Flagsmith not the de-facto OSS LaunchDarkly?

What are the differences to Flagr, GrowthBook or Flagsmith?

If you are curious about our performance, please check out our status page. If you want to support us, please give us a star on Github! If you need feature flags and want to partner with a team that is in it for the reasons I outlined above; feel free to sign up for a free account and give it a try!

I believe the idea is that you run feature flag management as a separate service. It's not meant for desktop software but rather as a component of a microservices architecture. This is not uncommon - I know at least one of the FAANGs has something like this internally.

Flagsmith [1] (formerly Bullet Train) is another open source feature-flags-as-a-service software, and they have their own SaaS offering now.

1. https://github.com/Flagsmith/flagsmith

That’s it! You now have a fully configured feature flagging system in your Rails app. Notice we didn’t cover some more advanced features that Flipper offers, including enabling features for a user group or individual users. For that, check out Flipper on Github. We also didn’t cover feature flagging frontend features in this post - if that becomes a requirement we could easily create an endpoint that uses the FeaturesRepo  and sends enabled features to the frontend to toggle. If you learned something new consider following me here - I’ll be putting out more content on Ruby on Rails and software development as I work on Firecode.io. Preparing for a coding interview? Check out Firecode.io.

I think you are calling it Runtime Controls: https://github.com/jnunemaker/flipper/issues/162

Flipper is a gem that makes feature flags and different ways to toggle them available in Rails. It is highly modular. Apart from the main gem, you'll also have to pick a storage adapter — but more on that later. Let's use the ActiveRecord adapter for now.

Since Honeybadger is a Ruby shop, we use the flipper gem.

The next step came about when I learned more about our use of Flipper; a Ruby gem for dynamically toggling on and off features. I didn’t know when the feature would roll out, but I wanted control over the feature. I also wanted admins of other Forems to have control as well. This was trivial with Flipper. Once I deployed the code, Forem’s got the original behavior unless they turned “flipped” on the feature.

flipper with Flipper UI to enable flag management

What advantages does your gem have over Flipper?