Our take
Activeregular commits and releases- Activity
- 85
- Community
- 93
- Issues
- 46
- Pull requests
- 80
+67 stars in the last 30 days
- Merges more pull requests than 88% of the projects we track
- Releases more often than 87% of the projects we track
- More contributors than 78% of the projects we track
Argo Workflows is a mature, actively maintained choice for teams that want container-based workflow orchestration built directly around Kubernetes.
Good fit if
- Your workloads already run on Kubernetes and can be packaged as containers.
- You need step- or DAG-based orchestration for batch, data, machine-learning, or CI/CD pipelines.
- You value an active project with frequent commits and releases, contributions from many contributors, and an Apache-2.0 license.
Look elsewhere if
- You need a workflow engine that runs independently of Kubernetes.
- Your tasks cannot run in containers or you do not want to operate Kubernetes infrastructure.
- Your workflow needs are not a good match for a Kubernetes CRD-based execution model.
All health signals
| Last commit | 2026-10-13 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 50 (latest v4.1.5, 2026-10-09) |
| Contributors | 100+ (top contributor: 15% of commits) |
| Issues closed, last 90 days | 1+ |
| Pull requests merged, last 90 days | 82 (typically merged in 0 days) |
| Project age | 9 years |
Checked on 2026-10-14 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
17,105Forks
3,736Change since Nov 17, 2026: +5 stars·+3 forks
Overview
Argo Workflows is a Kubernetes-native engine for defining and executing workflows made of containers. It lets teams express tasks as ordered steps or as a directed acyclic graph (DAG), then run independent work in parallel on a Kubernetes cluster.
It is aimed at engineers and platform teams that want workflow orchestration alongside their Kubernetes workloads, particularly for batch processing, data engineering, machine learning, and CI/CD. The project is a CNCF graduated project and is licensed under Apache-2.0.
Key Features
- Define workflows using sequential steps or DAG dependencies.
- Pass parameters and artifacts between tasks, with support for several storage and artifact backends.
- Control execution with retries, timeouts, conditionals, loops, suspend and resume, and cancellation.
- Run scheduled workflows and trigger workflows through webhooks or events.
- Use a web UI, CLI, and REST or gRPC server interface to manage executions.
- Archive completed workflows, collect workflow and pod resources, and expose Prometheus metrics.
- Integrate with Kubernetes scheduling, volumes, and resource orchestration.
Use Cases
- Data engineering teams can coordinate containerized data processing and batch jobs, including workflows with parallel tasks.
- Machine-learning teams can run multi-stage training or experiment pipelines on Kubernetes.
- Platform engineers can automate infrastructure tasks that need to run as Kubernetes jobs with dependencies and retries.
- DevOps teams can model CI/CD jobs as container steps and manage their execution in an existing Kubernetes environment.
What you need
Detected in the repository
- Go 1.26.5 or newer (from go.mod)
- A Dockerfile, so it can run in a container
- A test suite and automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Start with the quick-start guide and walk-through examples. See the README and documentation for setup details.
Alternatives
- flyte: Flyte focuses on Python-first machine-learning and data workflows, while Argo Workflows provides general-purpose container workflow orchestration on Kubernetes.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| argo-workflows | Go | Apache-2.0 | 17k | Active |
| flyte | Go | Apache-2.0 | 7.8k | Active |
Considerations
Argo Workflows requires Kubernetes, and its workflow definitions are Kubernetes custom resources, so adopting it means operating within that ecosystem. The repository identifies Go as its runtime and requires Docker; check the project documentation for the version and deployment requirements that match your environment. The project is actively maintained, with regular commits and releases and a broad contributor base; the available issue-handling data is limited, so it does not establish how quickly issues are typically resolved. Apache-2.0 permits broad use, subject to its license terms.
Found this useful?
Share it with someone who would like argo-workflows.