Flagger
flagger.app
- Free plan
- Self-hosted
What Flagger is
Flagger is a self-hosted Kubernetes operator that automates progressive delivery for applications running on Kubernetes. It gradually shifts traffic to a new version while measuring release signals such as HTTP or gRPC request success rates and latency. Supported strategies include canary releases, A/B testing, and blue/green deployments. Routing uses an ingress controller or a service mesh compatible with the Kubernetes Gateway API. Built-in checks cover HTTP request success rate and duration; teams can add custom metrics and webhooks for acceptance tests, load tests, or other validation. If SLO analysis finds a performance drop, Flagger can roll back a release automatically. Release analysis can query tools including Prometheus, Datadog, CloudWatch, New Relic, Graphite, Dynatrace, InfluxDB, and Google Cloud Monitoring. Manual controls allow deployments to be approved, paused, or resumed. Notifications can go to Slack, Microsoft Teams, Discord, or Rocket. Flagger uses Kubernetes custom resources and can work with Kubernetes-focused CI/CD solutions; it can also pair with Flux for GitOps canary pipelines. It is Apache 2.0 licensed.
Who it suits
Flagger suits teams delivering applications on Kubernetes who want automated traffic shifting, release checks, and rollback. Its self-hosted model and Kubernetes configuration make it relevant to teams using Kubernetes-compatible delivery workflows.
Good to know, and what to watch
- Supports canary, A/B, and blue/green strategies
- Automatically rolls back after detected performance drops
- Allows manual deployment approval and pause controls
- Integrates with multiple metric query systems
- Apache 2.0 licensed
- Requires applications running on Kubernetes
- Uses a self-hosted deployment model
- Routing requires an ingress controller or compatible service mesh
Plans
Every plan and priceFlagger
Open source
The verdict
Flagger brings traffic management, metric validation, and rollback into Kubernetes release workflows. Teams should confirm their routing and monitoring setup fits its supported integrations.
What the maker publishes
- Built-in metrics
- The built-in checks are HTTP request success rate and request duration. source
- Compatibility
- Flagger is configured with Kubernetes custom resources and is compatible with CI/CD solutions made for Kubernetes. source
- Configuration
- Flagger is configured using Kubernetes custom resources and works with CI/CD solutions made for Kubernetes. source
- Deployment strategies
- It supports canary releases, A/B testing, and blue/green deployments. source
- Deployment strategies
- It supports canary releases, A/B testing, and blue/green deployments. source
- Founded
- 2018 source
- GitOps
- Flagger can be used with Flux to build automated GitOps pipelines for canary deployments. source
- GitOps
- Flagger can be used in GitOps pipelines with tools such as Flux CD. source
- History
- Flagger was initially developed in 2018 at Weaveworks by Stefan Prodan and became a CNCF project in 2020. source
- License
- Flagger is licensed under Apache 2.0. source
- Manual controls
- The feature matrix lists manual gating to approve, pause, or resume deployments across supported routing integrations. source
- Metrics
- Release analysis can query Prometheus, InfluxDB, Datadog, New Relic, CloudWatch, Stackdriver, or Graphite. source
- Metrics integrations
- Metric query integrations listed include Prometheus, Datadog, CloudWatch, New Relic, Graphite, Dynatrace, InfluxDB, and Google Cloud Monitoring. source
- Notifications
- It can send deployment and canary result notifications to Slack, Microsoft Teams, Discord, and Rocket. source
- Product
- Flagger is a progressive delivery Kubernetes operator that automates application releases on Kubernetes. source
- Project history
- Flagger was initially developed at Weaveworks in 2018 by Stefan Prodan and became a CNCF project in 2020. source
- Project status
- Flagger is a graduated Cloud Native Computing Foundation project and part of the Flux family of GitOps tools. source
- Purpose
- Flagger automates progressive delivery for applications running on Kubernetes by shifting traffic gradually while measuring metrics and running conformance tests. source
- Rollback
- If SLO analysis detects a performance drop, Flagger automatically rolls back the release. source
- Routing
- Traffic routing uses an ingress controller or a service mesh compatible with the Kubernetes Gateway API. source
- Support
- The project directs users to its documentation, the CNCF community Slack #flagger channel, Flux talks, and GitHub issues for help. source
- Traffic shifting
- It gradually shifts traffic to a new version while measuring metrics such as HTTP or gRPC request success rate and latency. source
- Validation
- Built-in metric checks can be extended with custom metrics and webhooks for acceptance tests, load tests, or other validation. source
Checked against the maker's pages on 8 Oct 2026.