GO Feature Flag
Release a feature to five percent of users today, everyone on Friday, and only beta testers in between, all by editing one file: that is the job GO Feature Flag does for your applications. Flags live in a YAML, JSON, or TOML configuration you store in Git, S3, Kubernetes, or any retriever you already trust, and a lightweight relay proxy serves evaluations to every service through the standard OpenFeature SDKs in many languages. Targeting rules aim flags at specific users, segments, or contexts, progressive rollouts raise percentages on a schedule, experimentation splits traffic for A/B tests, and scheduled changes flip flags while the team sleeps. Every evaluation can be exported to files, S3, Google Cloud Storage, or Kafka for analysis, and webhook or Slack notifiers announce the moment a flag changes. Because the data plane is your proxy and your file, any language your stack speaks, from mobile apps to backends, evaluates the same flags with identity, variation, and rollout logic decided centrally. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Deploy