Self-Hosting Feature Flags: A Practical Look at FeatBit

You've probably been there—a feature is ready to ship, but you're not entirely sure how it'll behave in production. Do you deploy and hope for the best, or do you hold off until you can be more certain? Feature flags solve this problem, and FeatBit is an open-source tool that lets you manage them on your own infrastructure.

What It Does

FeatBit is a feature flags management tool that's designed to be self-hosted. At its core, it decouples code deployments from feature releases—meaning you can deploy code whenever you want, but control when (and to whom) features actually appear.

The project is built with .NET 8.0 on the backend, Python 3.9 or higher, and React 19 for the frontend. It's MIT licensed, so you can use it freely in your own projects. The README emphasizes a few key capabilities: you can roll out features to a small percentage of users initially and expand progressively, target specific users with particular features, and recover from errors instantly without redeploying. The idea is that you control feature visibility through simple if/else statements in your code, rather than through complex DevOps workflows.

Why It's Cool

There are a few things about FeatBit that stand out, especially if you've looked at other feature flag tools before.

• Self-hosting is a first-class option. The README is explicit about this—FeatBit allows you to host your feature flags service wherever your business needs it. For teams with compliance requirements or data protection concerns, this matters. You're not locked into someone else's cloud.

• It's built for developers, not just ops teams. The pitch here is that you use simple if/else statements to control and release features. That's a deliberate design choice—it means developers can directly drive business value without waiting on infrastructure changes or navigating complex deployment pipelines.

• Progressive rollouts and instant recovery. The ability to roll out to 1% of users first and then expand is a practical way to mitigate risk. And if something goes wrong, you can turn off the feature instantly without redeploying. That's a meaningful safety net.

• Targeted experiences. You're not just turning features on or off globally—you can release features to specific target users. This opens up possibilities for beta testing, gradual rollouts to particular customer segments, or measuring impact before a full release.

• Docker-based setup. The self-hosting story is straightforward: clone the repo, run docker compose up -d, and you're up and running. No Kubernetes cluster required to get started.

The combination of self-hosting, developer-friendly controls, and progressive rollout features makes FeatBit worth a look if you're evaluating feature flag tools.

How to Try It

The README lays out a three-step process. Here's the first step—getting FeatBit running locally:

git clone --branch 6.0.0 --depth 1 https://github.com/featbit/featbit.git
cd featbit
docker compose up -d

Once the containers are up, you can access the portal at http://localhost:8081. The default credentials are:

• Username: [email protected]
• Password: 123456

One thing to note: by default, the portal is only accessible from the machine running Docker Compose. If you want to make it publicly accessible, the README points to a FAQ entry in the documentation for instructions.

The second step is connecting an SDK. The README mentions finding your preferred SDK, though the content is truncated in what's provided here. You'll want to check the documentation for the full list of available SDKs and integration details.

If you'd rather not self-host right away, there's an online demo at app.featbit.co where you can try it out immediately. The repository also includes a video showing how to get started quickly.

You can find the full project at github.com/featbit/featbit.

Final Thoughts

FeatBit is a solid option if you're looking for a feature flags tool that you can run on your own infrastructure. The Docker-based setup makes it accessible, and the focus on developer-friendly controls means you won't need to hand off feature management to a separate team. It's particularly well-suited for teams that have compliance requirements or want to keep their feature flag data in-house. If you're already using a hosted solution and you're happy with it, there's no urgent reason to switch—but if self-hosting is a priority, FeatBit is worth checking out.

Follow @githubprojects for more developer tools and open source projects.