The Git-native, enterprise-ready feature management platform that developers love
Docs • Website • Blog • Contributing • Discord
Note
Looking for Flipt v1? You can find the v1 code on the main
branch and documentation at docs.flipt.io.
Finally, feature flags that work with your existing Git workflow.
Flipt v2 is the first truly Git-native feature management platform that treats your feature flags as code. Store your flags in your own Git repositories, use your existing branching strategy, and deploy flags alongside your code using the tools you already know and trust.
- Own your data: Store feature flags directly in your Git repositories
- Version control: Full history and blame for every flag change
- Branch and merge: Test flag changes in branches before merging to production
- Deploy together: Feature flags deploy with your code using existing CI/CD pipelines
- Environment per branch: Map environments to Git branches for seamless workflows
- Environment per directory: Organize flags by microservice or team within a single repo
- Environment per repository: Separate repos for different products or security domains
- Complete isolation: Each environment has its own namespaces, flags, and configurations
- Zero infrastructure: No databases, no external dependencies by default
- GitOps ready: Works with existing Git-based deployment workflows
- Real-time updates: Streaming API for instant flag propagation
- Modern UI: Intuitive interface with full Git integration and dark mode support
- Self-hosted: Keep sensitive flag data within your infrastructure
- Secrets management: Secure storage and retrieval of sensitive configuration data (OSS)
- GPG commit signing: Cryptographically sign all flag changes for enhanced security (Pro feature)
- Merge proposals: Code review workflow for flag changes (Pro feature)
- Audit trails: Complete history of who changed what and when
- OIDC/JWT/OAuth: Enterprise authentication methods supported
Important
V2 of Flipt is currently in beta release status. We may make breaking changes to the UI and API until we reach a stable release.
Feature | Flipt v1 | ✨ Flipt v2 |
---|---|---|
Storage | Database-centric (MySQL, PostgreSQL, SQLite) | Git-native with optional SCM sync (GitHub, GitLab, Gitea, etc.) |
Environments | Single namespace model | Multi-environment with Git flexibility |
Branching | Not supported | Full Git branching with environment branches |
Data Ownership | Stored in a database (MySQL, PostgreSQL, SQLite) | Stored in your Git repositories alongside your code |
GitOps | Read-only Git integration | Full read/write Git integration |
Deployment | Requires database setup | Zero dependencies - single binary |
Version Control | Basic audit logs | Full Git history and blame |
Merge Process | Direct flag changes | Merge proposals with code review |
Real-time Updates | Polling required | Streaming API for instant updates |
Multi-tenancy | Manual namespace management | Environment-based isolation |
Secrets Management | None | HashiCorp Vault and file-based providers available in OSS |
Perfect for engineering teams that want to:
- Ship faster with confidence: Deploy flags with your code using existing Git workflows
- Enable trunk-based development: Merge incomplete features behind flags without risk
- Implement proper GitOps: Treat infrastructure and feature flags as code
- Maintain security compliance: Keep sensitive flag data within your infrastructure
- Scale with multiple environments: Manage flags across dev, staging, and production seamlessly
- Enable team collaboration: Use familiar Git workflows for flag reviews and approvals
See our quickstart guide for more details.
# Install Flipt
curl -fsSL https://get.flipt.io/v2 | sh
# Wizard-driven setup to get you started quickly
flipt quickstart
# Run Flipt server
flipt server
docker run --rm -p 8080:8080 -p 9000:9000 -t docker.flipt.io/flipt/flipt:v2-beta
Flipt UI will be available at https://127.0.0.1:8080/.
# config.yml - Git-native setup with secrets management
secrets:
providers:
vault:
enabled: true
address: "https://vault.example.com"
auth_method: "token"
token: "hvs.your_token"
mount: "secret"
storage:
type: git
git:
repository: "https://github.com/your-org/feature-flags.git"
ref: "main"
poll_interval: "30s"
signature:
enabled: true
type: "gpg"
key_ref:
provider: "vault"
path: "flipt/signing-key"
key: "private_key"
name: "Flipt Bot"
email: "bot@example.com"
environments:
default:
storage: git
staging:
storage: git
directory: "staging"
For more setup options, see our configuration documentation.
- 🔒 Security - HTTPS, OIDC, JWT, OAuth, K8s Service Token, and API Token authentication methods supported out of the box
- 🗝️ Secrets Management - Secure storage and retrieval of sensitive data with HashiCorp Vault and file-based providers
- 🎛️ Control - Your data stays in your Git repositories within your infrastructure
- 🚀 Speed - Co-located with your services, no external API calls required
- ✅ Simplicity - Single binary with no external dependencies by default
- 🔄 GitOps Ready - Native Git integration that works with your existing workflows
- 👍 Compatibility - GRPC, REST, Redis, Prometheus, ClickHouse, OpenTelemetry, and more
- Store flags directly in Git repositories alongside your code
- Full version control with Git history, blame, and diff support
- Integrates with your SCM (GitHub, GitLab, Gitea, etc.)
- GPG commit signing for cryptographic verification of changes
- Environment per Git branch, directory, or repository
- Complete environment isolation with independent configurations
- Seamless environment promotion workflows
- Multi-provider secrets management: File-based and HashiCorp Vault providers available in OSS
- GPG commit signing: Cryptographically sign all flag changes with keys from secret providers (Pro feature)
- Secure key storage: Private keys and sensitive data stored securely in Vault or local files
- Multiple auth methods: Token, Kubernetes, and AppRole authentication for Vault
- Complex targeting rules and user segmentation
- Percentage-based rollouts
- Real-time flag evaluation with streaming updates
- Modern UI with Git integration and dark mode 🌙
- Declarative flag configuration with JSON/YAML schemas
- Comprehensive REST and gRPC APIs
- Secrets Management: Secure storage with HashiCorp Vault and file-based providers (OSS)
- GPG Commit Signing: Cryptographically sign all flag changes for enhanced security (Pro feature)
- Merge proposals: Code review workflow for flag changes (Pro feature)
- Authentication: OIDC, JWT, OAuth, and more authentication methods
- Observability: OpenTelemetry and Prometheus integration 🔋
Want to try Pro features? Get started with a free 14-day trial of Flipt v2 Pro – no credit card required initially. Includes merge proposals, GPG commit signing, premium support, and priority bug fixes.
Are we missing a feature that you'd like to see? Let us know by opening an issue!
Check out our integration documentation for comprehensive guides.
- REST API - Full HTTP API for any language
- gRPC API - High-performance binary protocol
- Local evaluation - Reduce latency with client-side flag evaluation, evaluate flags within your application for extreme speed and reliability.
Flipt supports the OpenFeature standard for vendor-neutral feature flag evaluation.
We would love your help! Before submitting a PR, please read over the Contributing guide.
No contribution is too small, whether it be bug reports/fixes, feature requests, documentation updates, or anything else that can help drive the project forward.
Not sure how to get started? You can:
- Join our Discord, and ask any questions there
- Dive into any of the open issues, here are some examples:
Review the Development documentation for more information on how to contribute to Flipt.
Ready to unlock the full potential of Git-native feature management? Flipt v2 Pro adds enterprise-grade features on top of our solid open-source foundation.
- 🔀 Merge Proposals - Code review workflow for feature flag changes, just like GitHub PRs
- ✍️ GPG Commit Signing - Cryptographically sign all changes using keys from secret providers for enhanced security and auditability
- 🏢 Premium Support - Shared Slack channel with same-day response times
- ⚡ Priority Development - Your bug reports and feature requests get prioritized
- 🔧 Enterprise Auth - Advanced authentication providers (coming soon)
- 📊 Advanced Analytics - Enhanced reporting and insights (coming soon)
- Free 14-day trial - No credit card required to start
- No instance limits on paid plans - run Flipt v2 Pro on as many servers as you need
- Cancel anytime - Prorated billing through our Stripe customer portal
Start Your Free 14-Day Trial →
Trial includes up to 5 instances. Upgrade seamlessly to unlimited instances with a paid subscription.
For help and discussion around Flipt, feature flag best practices, and more, join us on Discord.
Flipt follows semantic versioning for versioning.
We aim to release a new minor version of Flipt every 2-3 weeks. This allows us to quickly iterate on new features. Bug fixes and security patches (patch versions) will be released as needed.
Development documentation is available for those interested in contributing to Flipt.
We welcome contributions of any kind, including but not limited to bug fixes, feature requests, documentation improvements, and more. Just open an issue or pull request and we'll be happy to help out!
There are currently two types of licenses in place for Flipt:
- Client License
- Server License
All of the code required to generate GRPC clients in other languages as well as the Go SDK are licensed under the MIT License.
This code exists in the rpc/ directory.
The client code is the code that you would integrate into your applications, which is why a more permissive license is used.
The server code is licensed under the Fair Core License, Version 1.0, MIT Future License.
See our licensing docs and fcl.dev for more information.