Featurevisor
Git-native feature flags and experiments: YAML in a repo, PRs as the approval flow, JSON datafiles at runtime.
About
Featurevisor is an open-source (MIT) feature-management system by Fahad Heylaal that runs entirely on GitOps: you define feature flags, experiments, and remote config as YAML files in a Git repository, review changes via pull requests, and a CI/CD pipeline compiles them into static JSON datafiles served from your CDN. Applications fetch the datafiles and evaluate flags with SDKs (JavaScript for Node and browser, Swift, React hooks).
The design is deliberately minimal: no backend database, no admin UI beyond a read-only status site generator, no vendor dependency. Version 1.0 stable shipped with experiments (A/B and multivariate), segmentation, gradual rollouts, consistent bucketing, and multiple environments. The trade-off is that experimentation analysis (statistics, dashboards) is yours to build on your own analytics stack, and non-technical stakeholders are locked out of the Git-only workflow. The repo is actively maintained with recent commits.
What it can do
- Git-based flag, experiment, and remote-config definitions (YAML)
- PR-reviewed changes; static JSON datafiles via CI/CD
- A/B and multivariate experiment definitions with consistent bucketing
- Segmentation, gradual rollouts, multiple environments
- JavaScript, Swift, and React SDKs
- Status-site generator for read-only visibility
Setup
Create a Featurevisor project repo, define features in YAML, add the build step to CI to publish datafiles to your CDN, and evaluate with an SDK.
Prerequisites
A Git repo, a CDN or static host for datafiles, and comfort with YAML/PR workflows.
Use cases
Works with
Trust score — 7/10
Scored 7/10 (VERIFIED tier, metrics-v1). Evidence: MIT-licensed open source, v1.0 stable shipped, actively maintained (recent commits, ~16 contributors at v1.0), repo stars verified via GitHub API. Strengths: zero infrastructure and zero vendor lock-in — flags live in your Git repo and CDN; PR review doubles as the approval workflow; genuinely free forever. Docked for: (1) effectively a single-maintainer project, which is a bus-factor risk; (2) no runtime admin UI and no built-in experiment analysis — you bring your own stats; (3) Git-only workflow excludes non-technical teammates. License: MIT (fully open, no paid tier).
★ 812 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 6.0/10
- Maintenance · recency, releases, issue load
- 7.5/10
- Openness · license + docs
- 9.5/10
- Manual review · sanity read + red-flag check
- 7.0/10
- · MIT-licensed; v1.0 stable; actively maintained
- · Single-maintainer project (bus-factor risk)
- · GitOps-only workflow; no admin UI or built-in analysis
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.