Hypertune
Type-safe feature flags platform with A/B testing, analytics, and app configuration optimized for TypeScript
Featurevisor
Git-based feature flags and experimentation for developers
Manage feature flags, A/B tests, and remote config declaratively from your Git repository. Build static datafiles via CI/CD and evaluate them with lightweight SDKs.
Overview
GitOps for Feature Management
Featurevisor brings feature flags, experimentation, and remote configuration into your Git workflow. Define flags, segments, and rollout rules as YAML files in version control, then generate static JSON datafiles through your CI/CD pipeline and serve them from any CDN.
Developer-First Architecture
Built for teams who value code review, auditability, and declarative infrastructure, Featurevisor eliminates vendor lock-in and third-party dependencies at runtime. The SDK fetches pre-built datafiles from your CDN—no external API calls during evaluation. Support spans JavaScript, TypeScript, React, Vue.js, Go, PHP, Ruby, Java, and Swift, with consistent bucketing ensuring users see the same variation across sessions and devices.
Production-Ready Capabilities
Gradual rollouts let you move from 0% to 100% safely. Reusable segments simplify targeting logic. Tagging keeps bundle sizes lean by loading only relevant features. Multi-environment support extends beyond staging and production, while built-in tracking hooks integrate with your analytics stack. Whether you're toggling a UI element or running multivariate experiments, Featurevisor scales from side projects to enterprise deployments—all from the comfort of your existing Git workflow.
Highlights
Declarative YAML definitions in Git with full version control and code review
Static JSON datafiles served from your CDN—no runtime vendor dependencies
Consistent bucketing across devices and sessions for reliable experimentation
Multi-language SDK support: JavaScript, React, Vue, Go, PHP, Ruby, Java, Swift
Pros
- No vendor lock-in; you own the data and infrastructure
- Familiar Git workflow with pull requests, diffs, and audit trails
- Lightweight SDKs with offline-first evaluation from static files
- Free to deploy using GitHub Actions and CDNs like Cloudflare
Considerations
- Requires CI/CD pipeline setup and CDN configuration
- No built-in UI dashboard for non-technical stakeholders
- Datafile propagation delay between build and CDN availability
- Manual YAML editing may be less intuitive than GUI-based tools
Managed products teams compare with
When teams consider Featurevisor, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Engineering teams comfortable with GitOps and infrastructure-as-code
- Organizations prioritizing data sovereignty and avoiding SaaS dependencies
- Projects needing multi-language SDK support across web and backend
- Teams running experiments with consistent bucketing requirements
Not ideal when
- Non-technical users requiring a point-and-click dashboard
- Teams needing real-time flag updates without CI/CD cycles
- Organizations lacking existing CDN or static hosting infrastructure
- Projects requiring advanced analytics or built-in reporting dashboards
How teams use it
Gradual Feature Rollout
Deploy a new checkout flow to 10% of users, monitor metrics, then ramp to 100% over two weeks—all via pull requests and automated datafile builds.
A/B Testing Pricing Pages
Run a multivariate experiment comparing three pricing tiers, with consistent bucketing ensuring users see the same variant across mobile and desktop.
Remote Config for Mobile Apps
Store API endpoints, feature thresholds, and UI copy as variables under feature keys, updating values without app store releases.
Multi-Environment Segmentation
Define reusable audience segments (beta users, enterprise accounts) and apply different rollout rules across dev, staging, and production environments.
Tech snapshot
TypeScript98%
JavaScript2%
Makefile1%
HTML1%
CSS1%
Frequently asked questions
How does Featurevisor differ from hosted feature flag services?
Featurevisor is self-hosted and Git-native. You define flags as YAML, build static JSON datafiles via CI/CD, and serve them from your own CDN—eliminating runtime dependencies on third-party APIs.
Do I need a CDN to use Featurevisor?
Yes, datafiles must be hosted somewhere accessible to your applications. Any CDN or static file host works; examples include Cloudflare, AWS S3, or GitHub Pages.
Can non-developers update feature flags?
Flags are managed as YAML files in Git, so updates require pull requests. Teams can use GitHub's web editor or build custom tooling, but there's no built-in GUI dashboard.
How quickly do flag changes take effect?
Changes require a Git commit, CI/CD build, and CDN propagation. Typical latency ranges from seconds to a few minutes, depending on your pipeline and CDN cache settings.
Which SDKs are available?
Official SDKs exist for JavaScript (Node.js and browser), React, Vue.js, React Native, Next.js, Go, PHP, Ruby, Java, and Swift, with consistent APIs across languages.
Project at a glance
Active- Stars
- 781
- Watchers
- 781
- Forks
- 36
LicenseMIT
Repo age2 years old
Last commit2 days ago
Primary languageTypeScript
Last synced 2 hours ago