Flipt is an open-source, self-hosted feature-management platform that stores flag state in Git and evaluates it through streaming APIs and SDKs. It serves engineering teams who release behind flags, roll out gradually, and want every flag change reviewable like code.[1][2]
Quick verdict
Teams practicing GitOps who want self-hosted feature flags will get the most from Flipt. Its declarative Git-native storage plus real-time streaming evaluation removes the database and the vendor lock-in in one move. Teams without developers to integrate SDKs or operate the deployment should choose a managed flag service instead. If you can run a container and review a pull request, try Flipt; if you need flags without operating anything, pay for hosted.[1][2]
Key features
Declarative Git-native storage Keep flag state in GitHub, GitLab, Bitbucket, Azure DevOps, or Gitea, with OCI registries, S3-compatible storage, and local files as alternatives, so flag changes get diffs, history, and reverts.[1][2]
Environments and namespaces Isolate dev, staging, and production per branch, directory, or repository and scope flags per team or service so one flag set never leaks across boundaries.[1][2]
Segments with constraints and rules Target releases with ordered rules over user attributes, then split traffic with percentage rollouts and distributions across boolean and variant flags.[1]
Real-time streaming evaluation Push flag updates to SDKs over streaming REST and gRPC APIs instead of polling, so a toggle flips everywhere within moments of the merge.[1][2]
SDKs plus OpenFeature providers Evaluate flags from server-side and client-side SDKs in more than ten languages, or through OpenFeature providers if the team already standardized on that API.[1][2]
Console UI with approvals and audit Manage flags visually with an environments dashboard, change approvals, a full audit log, and Slack and webhook notifications on every update.[1]
Operator authentication and provisioning Gate console access with OIDC, GitHub, JWT, Kubernetes, or static-token authentication and provision teams through SCIM.[1][2]
Built-in observability Track flag evaluations with Prometheus metrics and traces through OpenTelemetry, keeping flag behavior visible in the stack the team already monitors.[1][2]
Who will love it
GitOps teams: flags versioned in Git with pull-request review match a workflow where infrastructure and config already ship that way, so flags stop being the unreviewed exception.[1][2]
Self-hosting shops: a single container with no database required, Kubernetes packaging, and offline and air-gapped support fit teams that must keep release tooling inside their own boundary.[1][2]
Polyglot engineering orgs: SDKs in more than ten languages plus OpenFeature providers mean each service evaluates flags natively instead of routing through one blessed stack.[1][2]
Who should avoid it
Teams without developers to spare: every flag needs SDK integration in application code, so a team with nobody to wire up evaluation gets a console with nothing behind it.[1][2]
Buyers wanting zero operations: self-hosting means owning upgrades, availability, and backups yourself, which is the wrong trade for teams that want flags without infrastructure.[1]
Experimentation-heavy product teams: analytics and workflow depth around product experimentation live mostly in managed platforms, so teams optimizing for that should compare managed options first.[1]
Reported experience
One inspected third-party practitioner guide with hands-on-style configuration examples; no Reddit or G2 user report located.
1 cited community source. Single vendor-adjacent practitioner guide, not a user sample; no sentiment or prevalence inference possible. No Reddit or G2 report located, and vendor-selected homepage quotes were excluded.
A third-party practitioner guide walks through install, YAML flag configs, a Go SDK evaluation example, and GitOps pull-request advice, presenting flag rollout as a one-line config change with flipt validate in CI. This is one vendor-adjacent guide, not a user sample, and it is analyzed here rather than quoted.[1]
Alternatives and compatibility
Flipt positions itself for teams escaping LaunchDarkly vendor lock-in toward self-hosted GitOps flags, naming that migration directly in its own FAQ.[1]
The catalogue lists FeatBit, Flagsmith, and Featurevisor as related projects; none was evaluated head to head in this pass, so they stay leads rather than recommendations. Choose Flipt when versioned self-hosted flags matter more than managed convenience.[1][2]
Questions worth asking
What is the best Flipt alternative for non-technical users?
Is Flipt really no-code?
How much does Flipt cost per month?
The open-source core costs nothing in license fees and self-hosts on your own infrastructure, checked October 9, 2026. Flipt Pro is $200 per month with an annual option stated at $2,000 per year that adds offline and air-gapped license validation, while Enterprise is quote-only. Hosting, operations, and support time remain your own costs on the free tier.[1]
Can you self-host Flipt?
Yes, self-hosting is the default: Flipt runs as a single Docker container or binary with no database required in declarative v2 mode, deploys on Kubernetes through Helm, Terraform, or Kustomize, and supports offline and air-gapped environments. Optional database storage covers Postgres, MySQL, SQLite, CockroachDB, libSQL, and YugabyteDB.[1][2]
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
One inspected third-party practitioner guide with hands-on-style configuration examples; no Reddit or G2 user report located. Single vendor-adjacent practitioner guide, not a user sample; no sentiment or prevalence inference possible. No Reddit or G2 report located, and vendor-selected homepage quotes were excluded.
- Flipt: Feature Flag Management for Safe Deployments
official · Observed October 9, 2026
Official homepage: Git-native open-source feature management; declarative storage across Git, OCI, S3, local files; environments and namespaces; segments, rollouts, real-time streaming evaluation; Console UI with audit log, approvals, notifications; OIDC, static tokens, Kubernetes, JWT, GitHub auth with SCIM; Pro $200 per month and annual $2,000 per year; Enterprise quote-only; server Fair Core License, clients MIT; v1 end of life December 2025; LaunchDarkly escape positioning.
- Git-Native Feature Flag Management with Flipt (Akmatori Blog)
community · Observed October 9, 2026
Third-party practitioner guide: Git-native YAML flag configs, install via script, Docker, and Helm, Go SDK evaluation example, GitOps pull-request workflow advice, GPG signing, Prometheus metrics, and flipt validate in CI. Vendor blog with an appended product pitch, so vendor-adjacent; analyzed here, never quoted.
- flipt-io/flipt repository
official · Observed October 9, 2026
Repository flipt-io/flipt: Go feature-flag solution, created 2016, snapshot 4,916 stars and 90 contributors; v2 declarative with Git, OCI, local file, S3 backends; client SDKs in 12 languages; OpenFeature providers; Console UI included; Fair Core License v1.0 server with client-side MIT; single Docker container, Helm, Terraform, Kustomize, offline support; Prometheus and OpenTelemetry; v2 feedback discussion 2692.
Compared with these products
No explicit proprietary baseline is recorded.