Hypertune
Type-safe feature flags platform with A/B testing, analytics, and app configuration optimized for TypeScript
Flipt
Git-native feature management platform for modern development teams
Store feature flags in Git repositories, deploy them with your code, and manage multi-environment configurations using familiar Git workflows—no database required.
Overview
Git-Native Feature Management
Flipt v2 is an enterprise-ready feature management platform that treats feature flags as code. Unlike traditional database-backed solutions, Flipt stores flags directly in your Git repositories, enabling teams to version, branch, merge, and deploy flags using existing Git workflows and CI/CD pipelines.
Built for Modern Engineering Teams
Designed for organizations practicing trunk-based development and GitOps, Flipt eliminates the friction between feature flag management and code deployment. Map environments to Git branches, directories, or separate repositories for complete flexibility. The platform requires zero infrastructure by default—no databases or external dependencies—and runs as a single binary that co-locates with your services.
Enterprise Security Without Compromise
Self-host Flipt to keep sensitive flag data within your infrastructure. Built-in secrets management supports file-based providers in the open-source edition, with HashiCorp Vault integration and cloud provider support (AWS, GCP, Azure) available in Pro. Authentication options include OIDC, JWT, OAuth, and Kubernetes service tokens. Real-time flag updates via Server-Sent Events eliminate polling overhead while maintaining instant propagation to client SDKs.
Highlights
Store feature flags in Git repositories with full version control and blame history
Multi-environment support via Git branches, directories, or separate repositories
Zero-dependency deployment as a single binary with no database required
Real-time flag updates using Server-Sent Events streaming API
Pros
- Flags deploy alongside code using existing CI/CD pipelines and Git workflows
- Complete data ownership with self-hosted infrastructure and Git storage
- No external dependencies or database setup required for basic operation
- Native GitOps integration with branching, merging, and code review workflows
Considerations
- Git-native approach requires teams comfortable with Git-based workflows
- Advanced features like GPG signing and merge proposals require Pro license
- Nightly builds from v2 branch are not stable for production use
- Cloud secrets management (AWS, GCP, Azure) not yet available
Managed products teams compare with
When teams consider Flipt, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Teams practicing trunk-based development and GitOps methodologies
- Organizations requiring self-hosted solutions with complete data ownership
- Engineering teams wanting feature flags versioned alongside application code
- Companies needing multi-environment flag management with Git flexibility
Not ideal when
- Teams unfamiliar with Git workflows or preferring GUI-only flag management
- Organizations requiring cloud-hosted SaaS solutions without self-hosting
- Projects needing advanced cloud secrets management immediately (AWS/GCP/Azure coming soon)
- Teams wanting database-backed storage with traditional RDBMS (use Flipt v1 instead)
How teams use it
Trunk-Based Development with Feature Flags
Merge incomplete features to main branch behind flags, enabling continuous integration without blocking releases or requiring long-lived feature branches
GitOps-Driven Multi-Environment Deployments
Map dev, staging, and production environments to Git branches, deploying flag changes through pull requests with code review and automated CI/CD pipelines
Microservices Flag Organization
Organize feature flags by microservice or team using directory-based environments within a single repository, maintaining clear ownership and isolation
Secure Enterprise Flag Management
Self-host Flipt with OIDC authentication and HashiCorp Vault secrets management, keeping sensitive flag data within corporate infrastructure while maintaining audit trails
Tech snapshot
Go70%
TypeScript28%
CUE1%
Shell1%
CSS1%
HTML1%
Frequently asked questions
What's the difference between Flipt v1 and v2?
Flipt v2 is Git-native, storing flags in Git repositories instead of databases. It supports multi-environment configurations, full Git branching workflows, and requires no database setup. V1 remains available on the main branch for teams preferring database-backed storage (MySQL, PostgreSQL, SQLite).
Does Flipt v2 require a database?
No. Flipt v2 uses Git repositories for storage by default and runs as a single binary with zero external dependencies. This eliminates database setup and maintenance overhead.
How do environments work in Flipt v2?
Environments can map to Git branches (e.g., main for production, staging branch for staging), directories within a repository (e.g., per microservice), or separate repositories (e.g., per product). Each environment has isolated namespaces, flags, and configurations.
What secrets management options are available?
The open-source edition includes file-based secrets providers. Pro features add HashiCorp Vault integration. Cloud provider support for AWS Secrets Manager, GCP Secret Manager, and Azure Key Vault is coming soon.
How do flag updates propagate to applications?
Flipt v2 uses Server-Sent Events (SSE) streaming API for real-time flag updates to client SDKs, eliminating the need for polling and ensuring instant propagation when flags change.
Project at a glance
Active- Stars
- 4,689
- Watchers
- 4,689
- Forks
- 278
Repo age9 years old
Last commityesterday
Self-hostingSupported
Primary languageGo
Last synced yesterday