flipt VS Flagr

Speaking as an open-source feature flag 'vendor' (https://github.com/flipt-io/flipt), the OpenFeature organization has been a joy to work with. They are very welcoming of new contributors (e.g., implementing a provider SDK in a new language).

If you're interested in this space I'd recommend lurking in their CNCF Slack Channel https://cloud-native.slack.com/archives/C0344AANLA1

Hey all,

I'm the founder of Flipt, an open-source (https://github.com/flipt-io/flipt) feature flag tool that I (and others) have been working on for the past few years.

About a year or two ago we added support for serving flag state from various non-relational declarative stores like Git, OCI, Object Store, etc.

Many of our users came to love the git-backed storage, as it allows them to keep their feature flags close to their code in there organization's repos. But they had one (rather large) ask, and that was the ability to use the UI to manage flag state changes and still use Git as the backend.

So today we're rolling out our hosted solution that does exactly that (and more soon).

I would love any feedback, questions, etc, or if anyone would give it a spin! Happy to extend the 14-day trial as well for anyone interested in providing product feedback.

Thanks!!

We at https://flipt.io are putting on a buy vs build webinar in a couple of weeks to discuss this very thing as it's a common question that engineering teams seem to have.

If you're interested in attending its taking place on LinkedIn on April 17: https://www.linkedin.com/events/buildvs-buy-pickingafeaturef...

We're currently evaluating OPA for adding RBAC to our open-source application [0]. We plan on using the Go API [1] and doing the policy eval directly in our app since our app is also written in Go.

The thinking is we'll have some basic built-in policies (like admins can do X, editors can do Y, etc) but also allow users to configure their own policies if they want by writing rego and loading their policy rules at startup time (via config). We'd document the inputs that we pass to the evaluation call such as request headers, IP, role, etc.

I'm curious if anyone has ever tried something like this or similar?

[0] https://github.com/flipt-io/flipt

[1] https://www.openpolicyagent.org/docs/latest/integration/#int...

Flipt - Clickhouse integration for flag eval analytics

At Flipt, we continually discuss technologies that can bring change to the industry. In this article, we delve into cutting-edge top trends and tools that can redefine DevOps and platform engineering this year.

In this article, I will share the DevOps tools that we've used at Flipt and in previous roles (such as at InfluxDB). These tools are relevant for any modern software project.

But after onboarding 50+ contributors to Flipt, I realized there are ways to make starts easy for newbies.

In this article, I will share the effort-based issue labeling system we use at Flipt to deal with this problem.

Flipt has reached 3k GitHub stars ⭐ this week.

Thanks, I'll evaluate Flagsmith as well!

Not totally sure Flipper is in the same category - that's more a Ruby-specific library, no? I know they have a cloud offering, but that isn't open source.

One more I found: https://github.com/checkr/flagr

FYI, the two libraries you linked are fairly the same. What I have done is used Flagr to create our experiments and do the heavy lifting for us. Along with that we use a custom react component to show the Flagr results. The custom package has been modeled heavily after the Pushtell's package you linked.