Flagsmith

Best Self Hosted Alternatives to Flagsmith

A curated collection of the 3 best self hosted alternatives to Flagsmith.

Hosted feature-flag and remote-configuration platform for managing feature releases, A/B tests, and application settings across environments. Provides SDKs, APIs and integrations for controlled rollouts, targeting, and runtime flag evaluation.

Alternatives List

#1
Flipt

Flipt

Flipt is a self-hostable, Git-native feature flag management platform with UI, APIs, and real-time updates for controlled rollouts across multiple environments.

Flipt screenshot

Flipt is a Git-native feature management platform for creating, reviewing, and deploying feature flags using the same workflows you use for code. It provides a modern UI and APIs to manage flags, while keeping source-of-truth and history in your own Git repositories.

Key Features

  • Git-backed flag storage with full version control (history, diffs, blame)
  • Multi-environment isolation mapped to Git branches, directories, or repositories
  • Modern web UI that can translate changes into Git commits
  • Real-time flag updates via Server-Sent Events (SSE) streaming (no polling)
  • REST and gRPC APIs for server-side evaluation and integrations
  • Support for complex targeting rules and percentage-based rollouts
  • Authentication options including OIDC/OAuth2/JWT
  • Observability integrations with OpenTelemetry and Prometheus

Use Cases

  • Progressive delivery with safe rollouts and fast rollbacks
  • GitOps-style flag management with reviews and CI/CD-driven promotion
  • Centralized feature flagging for microservices and multi-team environments

Flipt is well-suited for teams that want feature flags as code, strong auditability through Git history, and low operational overhead. It can be deployed as a single binary and integrated into existing delivery pipelines and developer workflows.

4.7kstars
277forks
#2
GO Feature Flag

GO Feature Flag

Lightweight open-source feature flag system with a relay proxy, OpenFeature support, file/cloud retrievers, and exporters for usage data.

GO Feature Flag screenshot

GO Feature Flag is an open-source feature flag solution that provides a Go module and a relay-proxy API server to evaluate and manage flags across languages. It supports file and cloud retrievers, progressive rollouts, A/B testing and event export for flag usage tracking. (gofeatureflag.org)

Key Features

  • Relay proxy (HTTP API) for multi-language support and central evaluation. (github.com)
  • Native Go module for in-process evaluation when using Go projects. (github.com)
  • Multiple retrievers: local file, HTTP, S3, Google Cloud Storage, Kubernetes ConfigMap, Git providers, Redis, MongoDB, PostgreSQL, and others. (gofeatureflag.org)
  • Advanced rollout strategies: targeted rules, canary releases, progressive (percentage) rollouts, scheduled changes, and A/B testing. (gofeatureflag.org)
  • Data exporters and notifiers to persist or forward evaluation events (file, S3/GCS, webhook, log) and notify via Slack/webhooks. (github.com)
  • Built to integrate with the OpenFeature standard to provide providers/SDKs across many languages. (gofeatureflag.org)

Use Cases

  • Add centralized feature flag evaluation for polyglot architectures using the relay proxy (HTTP API) and OpenFeature providers. (github.com)
  • Run progressive rollouts and A/B experiments with percentage-based and rule-based targeting while exporting evaluation events for analysis. (gofeatureflag.org)
  • Store flag configuration in existing infrastructure (S3, Git, Kubernetes, Redis, MongoDB, PostgreSQL) and deliver fast local or remote evaluations. (gofeatureflag.org)

Limitations and Considerations

  • OpenFeature integration is a cornerstone of multi-language support; users should validate current provider coverage and compatibility for their target language since OpenFeature is evolving. (github.com)

GO Feature Flag is geared toward teams that want a lightweight, auditable, and extensible self-hosted feature flag system with first-class Go support and a language-agnostic HTTP relay. The project provides editor tooling for composing and testing flags and is maintained as an open-source project with community contributions. (editor.gofeatureflag.org)

1.9kstars
192forks
#3
FeatBit

FeatBit

Open-source, self-hosted feature flag management platform with progressive rollouts, targeting rules, A/B testing, audit logs, and APIs for automated releases.

FeatBit screenshot

FeatBit is an open-source feature flag management and experimentation platform designed to help teams release features safely and run controlled rollouts. It provides a web portal, SDKs for multiple languages, and deployment options for both small and production-scale environments.

Key Features

  • Feature flag creation and management with environments and projects
  • Targeting rules and user segmentation for controlled exposure
  • Progressive rollouts (percentage-based) and fast rollback without redeploying
  • Experimentation and A/B testing to measure impact of changes
  • Insights and flag usage visibility during rollouts
  • IAM features for managing access by project/environment/team
  • Audit logs for tracking changes to flags and segments
  • Web APIs and webhooks for automation and integrations
  • Optional relay proxy/agent to reduce latency or run flags in customer environments

Use Cases

  • Gradual release of risky features with quick rollback and minimal operational overhead
  • Running A/B tests for product changes and measuring outcomes across user cohorts
  • Centralized feature control for multi-environment delivery workflows (dev, staging, prod)

Limitations and Considerations

  • Open-core licensing: some enterprise capabilities (for example SSO and certain workflow features) require a commercial license key

FeatBit is a strong fit for teams that want developer-friendly feature toggles plus experimentation in a deployable platform. It supports both quick Docker-based setups and production-oriented deployments with Kubernetes tooling.

1.7kstars
132forks

Why choose an open source alternative?

  • Data ownership: Keep your data on your own servers
  • No vendor lock-in: Freedom to switch or modify at any time
  • Cost savings: Reduce or eliminate subscription fees
  • Transparency: Audit the code and know exactly what's running