FeatBit

FeatBit separates deploying code from releasing features. Something ships dark, goes to one percent of users, expands as it holds, and switches off without a redeployment when it does not, all controlled by a simple if or else in your own code rather than a DevOps task.

Getting running takes a git clone and a docker compose up, after which the portal answers on port 8081. You then import an official SDK and call a variation function with a user object; the SDK returns that user's value and the code branches on it. SDKs cover .NET, JavaScript, React, Node.js, Java, Python, and Go, alongside OpenFeature providers.

Around the flags themselves sits the machinery a team needs.

• Targeting and segments: assign users to specific variations, or include and exclude them by attribute through reusable segments.
• Experimentation: run feature-level A/B tests anywhere in the stack and read usage insights during a rollout.
• Feature workflow: flag triggers, scheduled changes, and change approval requests automate how a flag moves.
• Access control: define access levels per project, environment, or team, with an audit log of flag changes.
• Integrations: webhooks reach DataDog, New Relic, Grafana, Growthbook, and Slack, while OpenTelemetry carries traces and metrics.
• Relay proxy: host a flag service in a customer's private environment or nearer end users.

Deployment runs from docker compose to Kubernetes manifests and Helm charts. FeatBit is open core: the bulk of the code is MIT, certain features need a valid license key, and a professional edition targets teams past millions of daily users.