finds.dev

flipt-io/flipt

Enterprise-ready, Git native feature management solution

View on GitHubHomepage ↗

★ 4,822GoNOASSERTIONupdated Jun 2026

// the take

Flipt v2 is a self-hosted feature flag server that stores flags as YAML/JSON in your Git repo instead of a database. The v2 rewrite is a significant architectural shift from v1's database-centric model — flags now live alongside your code, get committed with the rest of your changes, and environments map to Git branches or directories. Aimed at teams already doing GitOps who don't want to hand flag data to a SaaS vendor.

Single binary with zero runtime dependencies by default — no Postgres, no Redis, just a binary pointed at a Git repo. The Git storage model is genuinely useful: you get blame, history, and the ability to diff flag changes in your existing PR review flow. gRPC + REST APIs with OpenFeature OFREP support means you're not locked into Flipt-specific SDKs. SSE streaming for real-time flag propagation is a better story than polling, especially for client-side evaluation.

The server is under the Fair Core License, not MIT — it restricts competing managed services, which is fine for internal use but worth knowing before you build something on top of it. Several features that feel like table stakes (merge proposals, GPG commit signing, cloud secrets management) are paywalled at $200/month, so the OSS tier is more limited than the README makes it appear. The Git polling interval (30s default) means flag changes aren't instantaneous in the common case — SSE helps for connected clients but the write path still goes through a Git commit cycle. Migration from v1 is a full storage model change, not an upgrade — v1 users are effectively starting over.

We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
4,822
Forks
296
Language
Go
License
NOASSERTION
Last commit
11 Jun 2026

// nearby

If flipt isn't quite it.

All repos →