A feature flags client library for Go
Alternatives To Goforit
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
a day ago12February 08, 202255apache-2.0Java
A tool for refactoring code related to feature flag APIs
5 days ago26apache-2.0TypeScript
FeatureProbe is an open source feature management service. 开源的高效可视化『特性』管理平台,提供特性开关、灰度发布、AB实验全功能。
a month ago8December 27, 202131mitRust
A native implementation of ØMQ in Rust
3 days ago31July 04, 20228mitTypeScript
⛳️ Feature Flags for Next.js
Fun_with_flags8681512 days ago36February 27, 20225mitElixir
Feature Flags/Toggles for Elixir
Togglz83743154 days ago38June 07, 202257apache-2.0Java
Feature Flags for the Java platform
Featuremanagement Dotnet762
3 days ago48mitC#
Microsoft.FeatureManagement provides standardized APIs for enabling feature flags within applications. Utilize this library to secure a consistent experience when developing applications that use patterns such as beta access, rollout, dark deployments, and more.
Go Feature Flag714
a day ago94July 07, 202217mitGo
GO Feature Flag is a simple, complete and lightweight feature flag solution 100% Open Source. 🎛️
12 months ago33January 07, 2020mitSwift
🚩 Allows developers to configure feature flags, run multiple A/B tests or phase feature roll out using a JSON configuration file.
Feature Flags54313 months ago11September 18, 2022mitPHP
A Laravel package for handling feature flags
Alternatives To Goforit
Select To Compare

Alternative Project Comparisons

Build Status GoDoc

goforit is an experimental, quick-and-dirty client library for feature flags in Go.


Feature flags can be stored in any desired backend. goforit provides a several flatfile implementations out-of-the-box, so feature flags can be defined in a JSON or CSV file. See below for details.

Alternatively, flags can be stored in a key-value store like Consul or Redis.


Create a CSV file that defines the flag names and sampling rates:

func main() {
	ctx := context.Background()

	// flags.csv contains comma-separated flag names and sample rates.
	// See: testdata/flags_example.csv
	backend := goforit.BackendFromFile("flags.csv")
	goforit.Init(30*time.Second, backend)

	if goforit.Enabled(ctx, "go.sun.mercury", nil) {
		fmt.Println("The go.sun.mercury feature is enabled for 100% of requests")

	if goforit.Enabled(ctx, "go.stars.money", nil) {
		fmt.Println("The go.stars.money feature is enabled for 50% of requests")


Included flatfile backends are:


This is a very simple backend, where every row defines a flag name and a rate at which it should be enabled, between zero and one. Initialize this backend with BackendFromFile. See an example.


This backend allows each flag to have multiple rules, like a series of if-statements. Each call to .Enabled() takes a map of properties, which rules can match against. Each rule's matching or non-matching can cause the overall flag to be on or off, or can fallthrough to the next rule. See the proposal for this system or an example JSON file. It's a bit confusing to understand.


In this format, each flag can have a number of rules, and each rule can contain a number of predicates for matching properties. When a flag is evaluated, it uses the first rule whose predicates match the given properties. See an example JSON file, that also includes test cases.


goforit is in an experimental state and may introduce breaking changes without notice.


goforit is available under the MIT license.

Popular Flags Projects
Popular Feature Flags Projects
Popular Text Processing Categories

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Feature Flags