Flipt

Flipt v2 keeps feature flags in Git rather than in a database. Flag definitions live in your repositories next to the code they gate, which brings full history and blame on every change, branches for testing flag edits before production, and deployment through the CI/CD pipeline you already have.

That choice removes a lot of infrastructure. There is no database and no external dependency by default, just a single binary started by an install script or a Docker image. Flags reach client-side SDKs over a server-sent events streaming API, so updates propagate instantly without polling.

Environments map onto Git in whichever shape fits the organization.

• Environment per branch: development, staging and production each track their own branch.
• Environment per directory: flags are organized by microservice or team inside one repository.
• Environment per repository: separate repositories for different products or security domains.
• Complete isolation: every environment carries its own namespaces, flags and configuration.

Self-hosting keeps flag data inside your own infrastructure, with OIDC, JWT and OAuth authentication, audit trails and file-based secrets management in the open source build. GPG commit signing, merge proposals for reviewing flag changes and Vault or cloud secret manager integration are Pro features. Flipt v1, the database-backed release, still lives on the main branch for anyone not ready to move.