flagsmith VS spec

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

Less Vendor Lock-in: Open source means less vendor lock-in by nature. Many open source feature flag solutions are also partnered with OpenFeature to promote open standards, community, and less lock-in at the code level.

Instead of returning a static value, the code above uses OpenFeature and the Flagd provider (feature flag backend) to retrieve flag values (we will see how flagd reads the JSON file soon). If the feature flag system is offline or unavailable for whatever reason, a safe fallback value of #FFFFFF is returned.

Open-source & standardise interfaces - DevCycle tries to make every piece of software that their clients install open source. With CNCF, they are leading a project called OpenFeature - a vendor-agnostic interface for feature flagging.

The trend in feature flag implementation is to standardize with solutions like OpenFeature that provide SDKs and templates to streamline the process. Standardization is beneficial for 2 reasons:

For those that dont know about the project, check out Open Feature https://openfeature.dev/ which is sort of like Open Telemetry but for feature flags. Helps avoid vendor lock in. We're a young project and looking for help and to build the community!

What is the OpenFeature Standard?

Shameless plug here for openfeature - a CNCF standard for managing and implementing feature flags: https://openfeature.dev/