Featurevisor

What is GitOps?

Manage feature configuration through Git review, automated checks and datafile deployment. GitOps makes each proposed change part of your team's review process.

Git

Git tracks changes to files and supports reviewing and merging work from several contributors. Services such as GitHub and GitLab host repositories and provide review workflows.

GitOps

GitOps stores desired configuration in Git and uses automation to apply reviewed changes. It builds on infrastructure as code, making operational changes versioned and auditable.

Why should you care?

Every change is a file in review, so the team sees exactly what will change before it ships. Git records who changed each definition and when, the same checks run on a laptop and in CI, and publishing goes through the pipeline you already have.

How does it affect Featurevisor?

Featurevisor applies this workflow to feature flags, experiment variations and global variables. Their definitions live in files that your team reviews alongside tests.

How does it work?

  1. Contributors with repository access change definitions in files.
  2. They open a pull request, which follows your team's approval rules.
  3. CI lints the definitions and runs the tests, and after the merge it builds the datafiles and publishes them.

See deployment strategies for publishing your datafiles.

Once deployed, your applications can fetch the datafiles and pass them to their Featurevisor SDKs. Your application owns fetching and refresh timing. The SDK evaluates the datafile locally.

Does it limit non-technical users?

Product managers and other team members can browse definitions and propose changes without a local development setup.

For browsing, Catalog lets your team inspect features, global variables, targeting rules and test specs in a read only website generated from the project.

Git hosts such as GitHub support editing files in the browser. To raise checkout from 25% to 50% of everyone else:

  1. Open checkout in Catalog and choose Propose change, which opens its file in your Git host's editor.
  2. Change percentage: 25 under the everyone rule to percentage: 50.
  3. Commit it to a new branch and open a pull request.
  4. CI runs lint and the tests, a reviewer approves, and the merge publishes the change.

Contributors still need to learn the definition format and your team's review process. Test descriptions written in plain words, and the skill for AI agents, help with both.

Learning resources

Use these GitHub guides to propose changes from your browser: