Verify before you commit
Use this page to sanity-check Flipt quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 21, 2026
Freshness
Updated 2026-03-21T01:11:43.948669+00:00
Mar 21, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 7.1 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 6.6 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 6.9 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
The REST API covers flags, segments, rules, and distributions for management operations, and an evaluation API for flag state retrieval. The evaluation API is the runtime surface agents use most frequently — retrieving flag states for specific entities (users, requests, contexts) to control feature visibility. The gRPC API provides lower-latency evaluation for performance-sensitive use cases.
Reliability for self-hosted Flipt is the team's operational responsibility. The lightweight design (single binary with SQLite or PostgreSQL backend) makes Flipt deployable in resource-constrained environments. Teams running Flipt for production feature flag evaluation should implement appropriate monitoring and backup for the flag database.
Flipt is a self-hosted-only open-source feature flag platform with both gRPC and REST APIs for flag evaluation and management. Unlike GrowthBook or Flagsmith which offer cloud options, Flipt is exclusively self-hosted — making it the option for teams with strict data sovereignty requirements, regulated environments, or air-gapped deployments where cloud-hosted feature flag services are not acceptable. For agents in those environments, Flipt provides the feature flag evaluation infrastructure without any external data egress.
Authentication uses token-based auth for the management API. Self-hosted deployments manage their own token infrastructure. Teams should configure authentication appropriate for their deployment environment — Flipt running on internal infrastructure still requires proper auth to prevent unauthorized flag manipulation.
Documentation covers the REST and gRPC APIs clearly. The self-hosting setup documentation is practical for the range of deployment targets (Docker, Kubernetes, bare metal). Teams deploying Flipt for compliance-driven feature flag isolation will find the documentation covers the operational considerations specific to self-hosted deployments.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
6.9 / 10.0
No alternatives captured yet.