Featurevisor

Featurevisor is a Git-based feature management tool for teams that define flags, experiments and remote configuration in YAML. It is best suited to engineering teams already comfortable with Git, CI and operating their own delivery infrastructure. Its local evaluation model keeps the vendor out of application requests, in exchange for owning the datafile build-and-serve workflow.

Overview

Featurevisor makes feature changes part of the software delivery process: teams define them in a repository, build environment-specific datafiles, and deploy those files for SDKs to evaluate. Ordered targeting rules, percentage rollouts and weighted experiment variations cover common release and testing needs, while typed variables allow defaults and targeted overrides. Schema validation at build time helps catch configuration errors before deployment.

Applications fetch static JSON datafiles and evaluate features locally in memory, rather than making a network request for every decision. That keeps the decision path independent of a live evaluation service, but teams must build and serve the datafiles from their own CDN. This is a strong fit for teams that value control over infrastructure and change history; it is less suitable for those seeking a managed service to handle delivery.

Key features

• Targeting and experimentation: Ordered rules and percentage rollouts support gradual releases, while weighted variations enable A/B and multivariate experiments. Experiments can use the customer’s existing analytics tool; a Google Analytics tracking guide is provided.
• Typed configuration: Global and feature variables accept defaults and targeted overrides. Build-time schema validation makes configuration mistakes easier to catch in the same workflow as code changes.
• Local evaluation: SDKs evaluate fetched JSON datafiles in memory without a per-decision network request. This avoids putting a vendor service in the request path, but makes reliable datafile deployment the team’s responsibility.
• Git and CI controls: Pull requests, CI linting, tests and builds govern changes. Production values can be traced to commits, reviewers and builds, which suits teams that want feature changes to follow established review controls.
• Testable behavior: YAML test specifications assert expected feature behavior locally or in CI; a failed assertion returns a non-zero exit, so it can fail a pipeline.
• SDKs and integrations: SDK documentation covers JavaScript, Node.js, browsers, Go, Python, PHP, Ruby, Java, Kotlin, Swift, Rust and Elixir, alongside framework guides and optional OpenFeature providers. CI/CD guides cover GitHub Actions, GitHub Pages, Cloudflare Pages and PartyKit.

Pricing

Featurevisor costs nothing. The free offering is self-hosted, has no per-seat pricing and is MIT-licensed. There is no evaluation service to keep running, but teams do need to build and serve their own datafiles. That trade-off favors organizations able to operate their own delivery path over those that want a hosted control plane.

Platforms

Featurevisor is listed for Android, API, iOS, Linux, macOS, self-hosted, web and Windows. Its SDK language coverage includes JavaScript, Node.js, browser, React, React Native, Go, Python, PHP, Ruby, Java, Swift and Next.js.

Who it's for

Featurevisor fits teams using Git-based development who want flags, experiments and remote configuration reviewed and tested alongside application changes. It is particularly relevant for progressive delivery, trunk-based development, testing in production and microfrontends. Teams without capacity to build datafiles and serve them from their own CDN should favor a managed option instead.

Pros and cons

• Pro: Local in-memory evaluation avoids a network request for each flag decision and keeps a vendor service out of the application request path.
• Pro: Git pull requests, CI checks and build-time schema validation put feature changes under familiar review and testing controls.
• Pro: The self-hosted MIT-licensed offering has no per-seat charge or evaluation service that must stay alive.
• Con: Teams must build environment-specific datafiles and serve them from their own CDN, adding operational responsibility that a hosted product can absorb.
• Con: The workflow centers on YAML, Git and CI, so teams that need feature management without that engineering process are a poorer fit.

Alternatives

For a broader comparison, see Feature Flag Software. Consider Flagsmith if a freemium product with a free plan and free trial better suits your evaluation, or if you want its open-source core feature flag functionality. GO Feature Flag is another free, self-hosted choice, with an opensource plan that includes all features, unlimited flags and community support only.

ConfigCat may suit teams looking for a freemium plan with stated monthly download and traffic quotas: its Forever Free plan includes 10 flags, 2 environments, 2 products, 5 million config JSON downloads/month and 20 GB network traffic/month. Choose Flipt if a Git-native open-source workflow with a UI and Git sync is a closer match.

feat offers a free plan capped at 7,500 MAU, 100 server connections and 2 projects, with unlimited environments and flags; that may suit teams comfortable with those usage limits. Featureflow is worth considering for its free-forever plan, which includes up to 5 seats, 1 project, 2 environments and 1M SDK requests/month.

DevCycle has a free plan with caps on client-side MAUs and monthly cloud and server configuration requests, making it an option for teams that can work within those quotas. GrowthBook is another self-hosted alternative, with an open-source plan listing one project, unlimited flags, unlimited experiments and unlimited traffic.

Verdict

Choose Featurevisor if your team wants feature management governed through Git and CI, values local evaluation, and is prepared to build and serve its own datafiles. Its strongest advantage is keeping decisions local without per-seat costs or a live vendor evaluation service. Look elsewhere if you need a hosted delivery workflow or do not want to own the infrastructure that makes the configuration available to applications.