flagsmith VS awesome-priceops

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

I'd love your feedback on https://priceops.org

We recently open sourced Tier http://github.com/tierrun/tier which combines metering, feature flags and a nice client side SDK to simplify things.

I don't see why you want to avoid grandparenting. If the pricing model [2] is versioned and immutable, then keeping customers on their existing Customer Schedule [3] and then using specific migrations to move customers to new schedules makes sense and is easier than either not doing anything, or trying to track customer specific discounts and the accounting related to that.

1: https://priceops.org/

2: https://priceops.org/1-model

3: https://priceops.org/2-schedule

I've been working on putting together a (curated) list here. https://github.com/priceops/awesome-priceops