Our companies
Is Flagger.gg the same as Flux Flagger?
No. They are unrelated projects that share a name. Flagger.gg is a hosted feature-flag service from North Bay Ventures, built for teams whose code is written by AI agents. Flagger from the Flux project is an open-source Kubernetes operator that shifts traffic to a new version of a service gradually. One switches features inside your code; the other routes traffic between deployments.
Updated November 3, 2026
What is Flux Flagger?
Flagger is a progressive delivery tool that automates releases for applications running on Kubernetes. Its documentation says it reduces the risk of a new version by gradually shifting traffic to it while measuring metrics and running conformance tests, and that it implements canary releases, A/B testing and blue/green mirroring using a service mesh or an ingress controller. It is a Cloud Native Computing Foundation graduated project and part of Flux, and its code is at github.com/fluxcd/flagger.
What is Flagger.gg?
Flagger.gg is a hosted feature-flag service. Apps check flags with its Go and Node SDKs, which evaluate them in memory, so a check never makes a network call. Agents create, flip, roll out and kill flags through an MCP server, the flagger CLI and the API, using agent tokens scoped to one project, chosen environments and specific actions, which last 90 days at most. Every agent write needs a note, every change lands in an audit log, and agents have no approve tool. It is not open source. Sign up at app.flagger.gg; there is no public pricing.
How do they differ?
| Flagger.gg | Flux Flagger | |
|---|---|---|
| What it is | A hosted feature-flag service | A Kubernetes operator for progressive delivery |
| What it switches | Features inside your code, per user, workspace or percentage | Traffic between versions of a deployment |
| Where it runs | Hosted; flags evaluated in your app by the Go or Node SDK | Inside your Kubernetes cluster |
| Who drives it | People in a console and AI agents over MCP, the CLI and the API | Kubernetes resources, with a service mesh or ingress controller |
| Source | Not open source | Open source, a CNCF graduated project |
| From | North Bay Ventures | The Flux project |
Which one do you need?
Use Flux Flagger when you deploy on Kubernetes and want new versions of a service to take traffic step by step, with automatic analysis of metrics. Use Flagger.gg when you want to turn individual features on for some users and off for others without a deploy, and when AI agents should be able to create and roll back those flags themselves, within limits a person sets. They solve different problems, so a team could use both.
Automatic rollback tied to metrics is something Flagger.gg lists as in development, not available yet. For Flagger.gg's own explanation, see what a feature flag is.
Why the shared name?
Both names come from the idea of a flag. The .gg is part of the product's name, which is why North Bay Ventures always writes it as Flagger.gg. Flagger.gg's own site says plainly that it is not the Flux/CNCF Flagger, and not a Discord bot. To see where Flagger.gg fits alongside the studio's other products, read how Sandboxer, Flagger.gg and Transformer work together.
Frequently asked questions
Is Flagger.gg related to Flux or the CNCF?
No. Flagger.gg is a separate hosted service from North Bay Ventures. The Flux/CNCF Flagger is an unrelated open-source Kubernetes operator.
Does Flagger.gg need Kubernetes?
No. It works with any app that can use its Go or Node SDK, wherever the app runs.
Is Flagger.gg open source?
No. It is a hosted service.
Is Flagger.gg a Discord bot?
No. It is a feature-flag service for teams whose code is written by AI agents.