A simple, complete, and lightweight self-hosted feature flag solution that supports multiple languages via OpenFeature.
GO Feature Flag is an open-source, self-hosted feature flag management system that allows developers to safely deploy and test new features by controlling their release through flags. It solves the problem of risky deployments by enabling gradual rollouts, A/B testing, and instant feature toggling without code changes. The system supports multiple programming languages via the OpenFeature standard and stores flag configurations in various backends like S3, GitHub, and Kubernetes.
Development and DevOps teams building applications in Go, Java, JavaScript, Python, .NET, or other supported languages who need a lightweight, self-hosted feature flag solution. It's ideal for organizations practicing continuous deployment and seeking to avoid vendor lock-in.
Developers choose GO Feature Flag for its simplicity, adherence to the OpenFeature standard, and ability to self-host without complex infrastructure. Its unique selling point is providing a complete, vendor-neutral feature flagging solution with multi-language support and flexible storage options, all while being 100% open-source.
GO Feature Flag is a simple, complete and lightweight self-hosted feature flag solution 100% Open Source. 🎛️
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides SDKs for Go, Java, JavaScript, Python, .NET, Ruby, Swift, and PHP via OpenFeature providers, enabling consistent flag evaluation across diverse tech stacks.
Built on the OpenFeature specification, ensuring no vendor lock-in and compatibility with a growing ecosystem of tools and libraries.
Supports storing flag files in various backends like S3, GitHub, Kubernetes, and MongoDB, allowing seamless integration with existing infrastructure.
Offers percentage-based, progressive, scheduled, and A/B testing rollouts, facilitating controlled feature releases and experimentation as detailed in the documentation.
Being self-hosted, teams must deploy, scale, and maintain the relay proxy server, adding complexity compared to managed SaaS solutions.
Uses polling to update flag configurations (default every 60 seconds), so changes aren't reflected in real-time, potentially causing delays in flag updates.
Primary configuration is via YAML/JSON files with a basic online editor; lacks a comprehensive GUI for non-developers, making advanced management cumbersome.