flagsmith VS featbit

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

Feature flags, also known as feature toggles, have become an essential tool for modern software development. They enable developers to control the release of new features and updates in a flexible and controlled manner. In this blog post, we'll explore what feature flags are, their classical and modern use cases, and how to implement them effectively in front-end, mobile, and server-side applications. We'll also delve into the concept of overlapping design A/B testing and how feature flags play a crucial role in building robust experimentation.

Here's our issue link: [Good First Issues]: Configuring Serilog through appsettings.json file · Issue #520 · featbit/featbit (github.com)

featbit/featbit: A scalable, fast and 100% open-source feature flag tool written in C# .NET (github.com)

You can find the tool at: https://github.com/featbit/featbit

Hi everyone, I wanted to introduce a new open-source feature flag management tool that we recently discovered and implemented in our production environment. You can find the tool at: https://github.com/featbit/featbit We tested several other tools, but what convinced us to choose this particular tool were the following reasons: 1. It offers all the necessary functionalities we require. Additionally, it seems that they continue to open-source additional functions that other tools don't provide, such as Audit Logs, Reusable Segments, Permission Control, and even Single Sign-On (SSO) in the future. 2. I joined their community, and I found the core team to be friendly and responsive (perhaps because they are relatively new). 3. The tool is developed using a programming language that aligns well with our daily work. 4. Although they open-sourced the project only 7 months ago, they have been working on its development for two years. 5. It is licensed under the MIT license. I thought it would be helpful to share this tool here for anyone who may need it or wants to add it to your wishing list. Enjoy!

It's MIT for those interested in such things