Argo Project (software)

Argo

Developer(s)	Argo Project contributors
Initial release	August 2017 (2017-08)
Repository	github.com/argoproj
Written in	Go
Engine
Platform	Kubernetes
Type	Continuous delivery, workflow orchestration
License	Apache License 2.0
Website	argoproj.github.io

Search Argo Project (software) on Amazon.

Argo, also called the Argo Project, is a family of open-source tools for running and delivering software on Kubernetes. It comprises four subprojects: Argo CD, a continuous delivery tool that implements GitOps; Argo Workflows, a container-native workflow engine; Argo Rollouts, a controller for progressive delivery strategies such as blue-green and canary releases; and Argo Events, which provides declarative management of event-based dependencies and triggers for Kubernetes resources. All four are written in Go and released under the Apache License 2.0.

The project began at Applatix, a startup in Sunnyvale, California co-founded and led by its chief executive, Pratik Wadher, which released the original Argo workflow engine as open source in August 2017. Intuit acquired Applatix in January 2018; Argo CD and Argo Rollouts were then created at Intuit, while Argo Events was developed at BlackRock and contributed to the project. Argo was accepted by the Cloud Native Computing Foundation (CNCF) at the incubating level in 2020 and graduated on December 6, 2022, reaching the foundation's highest maturity level.

Development is spread across several companies. The project recognizes Akuity, BlackRock, Intuit, Octopus Deploy, Pipekit and Red Hat as its corporate maintainers, and its maintainer roster also includes engineers at Adobe, Alibaba Cloud and other organizations as well as independent contributors. Argo CD is the most widely used GitOps tool for Kubernetes: telemetry published by Dynatrace in 2025, derived from observed Kubernetes workloads rather than survey responses, found that about a quarter of the organizations it measured were running Argo CD, up from 17% in 2022, and reporting on the CNCF's 2024 annual survey placed Argo second among all continuous-delivery and CI/CD platforms at 45% usage. Argo CD has also been the subject of repeated vulnerability research, including a critical JSON Web Token flaw in 2022 and a dispute in 2026 over an unpatched report.

History

Origins at Applatix (2015–2017)

Pratik Wadher shares origins of Argo name at ArgoCon '21

Applatix was founded in 2015 in Sunnyvale, California by Pratik Wadher, its chief executive, together with Saradhi Sreegiriraju (chief product officer) and Ed Lee (chief technology officer); trade coverage described the founding team collectively as former leaders of Data Domain, Nicira, Bebop, Tintri and Apigee. The company was backed by Lightspeed Venture Partners and sold a DevOps automation product for public-cloud environments; according to one of its early engineers, the team began building on Mesosphere before moving to Kubernetes.

In August 2017 Applatix announced Argo in a post written by Wadher, describing it as "an open source container-native workflow engine for Kubernetes" and naming early users including RocksDB Cloud, Apache Pulsar, Apache BookKeeper and AppDynamics. Applatix joined the CNCF as a member company in October 2017. Later that year the engine was re-implemented as a Kubernetes custom resource definition (CRD); the first CRD-based build, v2.0.0-alpha1, was tagged on November 16, 2017, and demonstrated at a Bay Area Kubernetes meetup, and version 2.0.0 followed on February 6, 2018.

Sources differ on when work on Argo Workflows began, because the project's own records distinguish the pre-Kubernetes Applatix product from the git history of the CRD rewrite. The project changelog records a version 1.0.0 dated July 23, 2017; the CNCF's project page lists a first commit of July 27, 2017; the CNCF's Argo Project Journey Report states that Jesse Suen made the first commit to the repository on October 17, 2017; and the public launch announcement is dated August 31, 2017.

Acquisition by Intuit and the growth of the suite (2018–2019)

Applatix announced on January 22, 2018, that it was joining Intuit, and Intuit published its own announcement on January 29. Intuit's quarterly report for the following quarter disclosed approximately $412 million in combined consideration for three acquisitions completed in the quarter ended January 31, 2018 — TSheets.com, Exactor and Applatix — and no price was disclosed for Applatix alone. Wadher went on to serve as senior vice-president of product development at Intuit.

Intuit was in the middle of a large migration to Kubernetes — a CNCF case study records the company going "from zero to about 2,000 services running on Kubernetes" in eighteen months — and needed a way to keep cluster state in step with configuration held in Git. Jesse Suen made the first commit to the argo-cd repository on February 15, 2018, and version 0.1.0 was released the following month, initially supporting only the ksonnet configuration tool; Helm, Kustomize and other formats were added later. A June 2018 post by Intuit's Mukulika Kapas described Argo CD as "a new project to deliver GitOps-style, declarative, continuous delivery (CD) service based on Ksonnet/Jsonnet with a Kubernetes native experience", already "powering the deployment of multiple services at Intuit". Red Hat later summarized Intuit's motivation as the absence of "a purpose-built enterprise toolset for GitOps on Kubernetes".

A third component followed in November 2018, when Danny Thomson created the argo-rollouts repository; its first release, 0.1.0, arrived on February 1, 2019, with a blue-green deployment strategy. The maintainers have described its purpose as restoring the blue-green and canary deployment strategies that Intuit teams had used with Spinnaker before migrating to Kubernetes.

The fourth component originated outside Intuit. Argo Events was developed at BlackRock for the firm's Aladdin investment-technology platform and contributed to the Argo Project; its first release, v0.5-alpha1, was published in June 2018. Michael Francis, then head of platform engineering for Aladdin, said that BlackRock "were already using Argo Workflows, and we decided to contribute Argo Events, an event-based dependency manager for Kubernetes, to the Argo project".

Argo CD reached version 1.0 on May 16, 2019, a release announced two weeks later as introducing API stability and a custom resource definition for the application specification; version 1.1.0 followed on July 24, 2019.

The Argo Flux initiative and GitOps Engine (2019–2020)

On November 14, 2019, the maintainers of Argo CD and the competing GitOps tool Flux announced that they would "join forces", extracting shared reconciliation logic into a new repository called GitOps Engine and eventually shipping a combined tool to be named Argo Flux. The combined tool was never released. According to the GitOps Engine documentation, the Flux team produced a proof of concept on top of the engine in March 2020, judged the breaking changes too disruptive, and instead published the GitOps Toolkit as a request for comments in June 2020; the document adds that "the Argo and Flux teams decided all of this on good terms". Argo CD shipped GitOps Engine in version 1.6 in June 2020 and continued to use it.

Writing in TechTarget in December 2022, Beth Pariseau reported that "there was an effort in 2020 to merge the underlying reconciliation mechanism of the two projects into a utility called GitOps Engine … but while Argo CD still uses GitOps Engine, Flux CD opted for its own approach with GitOps Toolkit." In the same article Henrik Blixt, Intuit's group product manager for platform and open source, attributed the difficulty to the projects' different sponsors: "The fact that one project is led by an end user company and the other by a vendor makes it hard to combine them, because you have one company that's actually making a living out of the project and another that just wants to build a community around it and use it themselves." The GitOps Engine repository was later archived, and its code and history moved into the Argo CD repository.

Donation to the CNCF (2019–2020)

Ed Lee, by then an Intuit distinguished engineer, filed a proposal on September 24, 2019, for Argo to join the CNCF at the incubating level; the project did not pass through the foundation's sandbox stage. The CNCF's SIG App Delivery completed its review in February 2020, concluding unanimously that "Argo fulfills all the formal criteria and has the required maturity", while also observing that "the project still seems to be very driven by Intuit". The Technical Oversight Committee voted to accept the project, with the outcome announced on April 7, 2020; the CNCF's own project record gives the acceptance date as March 26, 2020. All four subprojects moved to the foundation together.

At the time of incubation the CNCF reported roughly 8,300 GitHub stars across the project, 425 contributors, more than 4,000 commits and about 110 known end users. SiliconANGLE and DevClass covered the acceptance, the latter noting that the project "was initially created at Applatix, a Kubernetes development shop that started in 2015, before being acquired by finance software giant Intuit in 2018".

Governance was formalized over the same period. Until July 2020 the project's community documentation stated that "as custodian of the Argo project, Intuit will be responsible for the overall administration of the argoproj organization on GitHub"; that sentence was removed when governance documents were rewritten that month. A bootstrap committee was constituted to oversee the transition to open governance; the roster committed to the community repository on August 4, 2020, named seven members from four companies — Ben Browning and Shoubhik Bose of Red Hat, Edward Lee, Jesse Suen and Mukulika Kapas of Intuit, Lei Zhang of Alibaba and Mike Bowen of BlackRock — and required that the committee "represent a cross-section of interests, not just one company". Red Hat announced its participation publicly on August 17, 2020, committing development resources and describing itself as "joining the Argo community as a member of the bootstrap steering committee"; it had evaluated GitOps tooling in late 2019 and chosen Argo CD partly because a single instance could serve multiple Git repositories.

Codefresh (now Octopus Deploy), a continuous-integration company, was the first to ship commercial software built on Argo CD. It presented Argo-based delivery through a CNCF community program in July 2020 and in November 2020, at KubeCon + CloudNativeCon North America, launched a GitOps dashboard powered by Argo CD as part of an initiative it branded GitOps 2.0; the company has since described itself as the first commercial vendor for Argo. Red Hat followed with Red Hat OpenShift GitOps, built on Argo CD, released as a technology preview in February 2021 and generally available on May 3, 2021. Codefresh subsequently rebuilt its flagship platform around Argo, a shift SiliconANGLE reported in February 2022. By the Argo CD 2.0 release in April 2021 the maintainers were crediting Intuit, Red Hat and Codefresh with "significant involvement" in the release.

Maturity and graduation (2021–2022)

2021 brought major releases across the suite: Argo Workflows 3.0 on March 30, Argo CD 2.0 on April 7, and Argo Rollouts 1.0 on May 20. As part of the 3.0 cycle the argoproj/argo repository was renamed argoproj/argo-workflows, a change the maintainers said "makes it clear that this is the repo for Argo Workflows and not the overall Argo Project".

In 2021 three engineers who had worked on Argo at Applatix and Intuit — Hong Wang, Jesse Suen and Alexander Matyushentsev — founded Akuity, a company selling a managed Argo service. The first ArgoCon, a one-day virtual conference hosted by Codefresh together with Red Hat and Intuit, was held on December 8, 2021; the CNCF later reported that it drew more than 4,000 attendees and 25 speakers.

The CNCF's 2021 annual survey recorded a 115% year-on-year increase in Argo's use in production, and its 2022 survey put Argo among the fastest-growing projects in the foundation, rising from 10% to 28% usage between 2020 and 2022. A second ArgoCon was held in Mountain View, California, on September 19–21, 2022, with sponsorship from Adobe, Akuity, Codefresh, Harness, Intuit and Red Hat; the CNCF's post-event report recorded 236 in-person check-ins and 1,296 virtual participants.

Argo graduated from the CNCF incubator on December 6, 2022. The announcement reported production use by more than 350 organizations, a 250% increase since incubation, and contributions from about 2,300 companies and 8,000 individuals; it also noted that the project held an OpenSSF Best Practices badge and had completed a third-party security audit in July 2022. TechTarget observed that Argo had "a wider breadth of maintainers" than comparable projects, with roughly a third of its forty core maintainers employed by Intuit and the remainder spread across other organizations.

Later developments (2023–2026)

The commercial ecosystem around the project consolidated in 2024. Weaveworks, the company that had coined the term GitOps and sponsored Flux, ceased operations that February. Later the same month Octopus Deploy acquired Codefresh, bringing Codefresh's Argo-based commercial platform and staff, including Argo maintainers, into one company; terms were not disclosed.

In November 2024 the CNCF released Inside Argo: Automating the Future, a documentary film about the project produced with Speakeasy Productions, which premiered at KubeCon + CloudNativeCon North America in Salt Lake City on November 14 and features participants from Akuity, the CNCF, Intuit, Octopus Deploy and Red Hat.

Argo CD 3.0, released on May 6, 2025, was the project's first major version change in four years; it altered default behavior for fine-grained RBAC, resource tracking and logs authorization, and ended 2.x minor releases. In November 2025 Amazon Web Services made a managed Argo CD service generally available as one of three launch capabilities in Amazon EKS Capabilities. Argo Workflows reached version 4.0 in February 2026, removing its bundled Python SDK in favor of the community project Hera.

Timeline

Selected milestones

Date	Event
2015	Applatix founded in Sunnyvale, California
August 2017	Argo released as open source by Applatix as a container-native workflow engine
November 2017	Engine re-implemented as a Kubernetes custom resource definition
January 2018	Intuit acquires Applatix
February 2018	First commit to the Argo CD repository; version 0.1.0 released in March
June 2018	First release of Argo Events, developed at BlackRock
November 2018	Argo Rollouts created; version 0.1.0 released February 2019
May 16, 2019	Argo CD 1.0 released
November 2019	Argo CD and Flux announce the Argo Flux initiative, later abandoned
Spring 2020	Argo accepted as a CNCF incubating project, with all four subprojects
July–August 2020	Intuit's custodianship of the GitHub organization is removed from the governance documents; a bootstrap committee is constituted with members from Red Hat, Intuit, Alibaba and BlackRock
September 2020	Argo Events 1.0 released, consolidating on the EventBus, EventSource and Sensor resources
November 2020	GitOps Working Group founded by Amazon, Codefresh, GitHub, Microsoft and Weaveworks; Codefresh launches the first commercial product built on Argo CD
March–May 2021	Argo Workflows 3.0, Argo CD 2.0 and Argo Rollouts 1.0 released
May 2021	Red Hat OpenShift GitOps, built on Argo CD, becomes generally available
July 2021	The project's website begins listing corporate maintainers, naming Codefresh, Intuit, BlackRock and Red Hat
October 2021	GitOps Principles v1.0.0 published by the GitOps Working Group; Akuity added to the corporate maintainer list
December 8, 2021	First ArgoCon held virtually
July 2022	CNCF-funded third-party security audit completed by Ada Logics
December 6, 2022	Argo graduates from the CNCF
2023	ArgoCon becomes a CNCF-hosted event co-located with KubeCon
February 2024	Octopus Deploy acquires Codefresh
November 2024	CNCF documentary Inside Argo: Automating the Future premieres at KubeCon North America
May 2025	Argo CD 3.0 released
November 2025	AWS makes a managed Argo CD service generally available in Amazon EKS
February 2026	Argo Workflows 4.0 released

Components

The four subprojects can be used independently but are designed to work together; the CNCF describes them as tools that "can be used independently, but there is great benefit in using them together to create and operate complex applications at scale". Each defines custom resources in the argoproj.io API group and runs as one or more Kubernetes controllers.

Argo subprojects

Subproject	Purpose	Principal custom resources	Version (August 2026)
Argo CD	Declarative GitOps continuous delivery	Application, ApplicationSet, AppProject	3.5.1
Argo Workflows	Container-native workflow and pipeline engine	Workflow, WorkflowTemplate, ClusterWorkflowTemplate, CronWorkflow, WorkflowEventBinding	4.1.0
Argo Rollouts	Progressive delivery and experimentation	Rollout, AnalysisTemplate, ClusterAnalysisTemplate, AnalysisRun, Experiment	1.9.1
Argo Events	Event-driven automation	EventBus, EventSource, Sensor	1.9.11

Argo CD

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes, implemented as a Kubernetes controller that continuously compares the live state of running applications against a desired state held in a Git repository. An application whose live state diverges from the target is reported as OutOfSync.

Its core architecture has three parts: an API server exposing a gRPC and REST interface for the web interface, CLI and CI/CD systems; a repository server that caches Git repositories and renders Kubernetes manifests; and an application controller that reconciles live state against the desired state and runs user-defined lifecycle hooks. A deployment also includes Redis as a cache, an optional Dex instance for OpenID Connect authentication, and controllers for ApplicationSets and notifications.

Manifests may be supplied as Kustomize overlays, Helm charts, OCI images, directories of YAML, JSON or Jsonnet, or through a configuration-management plugin. Ordering within a deployment is controlled by "sync waves" and by hooks that run before, during and after synchronization. AppProjects provide multi-tenancy by grouping applications and restricting the clusters, repositories and resource kinds they may use.

Two formerly separate projects, ApplicationSets and Notifications, were merged into Argo CD in version 2.3 in March 2022. The ApplicationSet controller generates Applications programmatically from a range of generators, which the documentation presents as a way of "managing Argo CD Applications across a large number of clusters and within monorepos". Other notable additions include a lightweight "Argo CD Core" distribution in 2.1, server-side apply in 2.5, user-interface and proxy extensions in 2.5 and 2.6, multiple sources per Application in 2.6, and a source hydrator in 2.14. Since 2022 the project has followed a fixed quarterly release cadence, with minor versions in February, May, August and November and patches for the three most recent minor versions.

Argo Workflows

Argo Workflows is a container-native workflow engine for orchestrating parallel jobs on Kubernetes, implemented as a custom resource definition. Work may be expressed as a sequence of steps or as a directed acyclic graph of tasks, and the Workflow resource both defines the work and stores its state.

The system consists of two deployments — a workflow controller that performs reconciliation and an optional Argo Server that provides the API and web interface — with each step or task materializing as a pod. Historically several pod executors were available; since version 3.4 only the "emissary" executor remains. Artifacts can be stored in object stores such as Amazon S3, Google Cloud Storage and Azure Blob Storage, or in Git or HTTP endpoints, and completed workflows can be archived to PostgreSQL or MySQL.

Nine template types are available, divided into definitions (container, script, resource, suspend, plugin, container set and HTTP) and invocators (steps and DAG). Later versions added scheduled CronWorkflow resources, step-level memoization, artifact garbage collection, conditional retries, mutex and semaphore synchronization including database-backed locks shared between controllers, and OpenTelemetry tracing. Client libraries exist for Go, Java, Python and TypeScript; since the removal of the bundled Python SDK in version 4.0, the project recommends the community-maintained Hera library.

Argo Workflows is used as an execution engine by other projects, notably Kubeflow Pipelines, which "uses Argo Workflows by default under the hood to orchestrate Kubernetes resources", as well as Katib, Metaflow, Seldon and SQLFlow. Minor releases occur roughly every six months and the project explicitly does not follow semantic versioning.

Argo Rollouts

Argo Rollouts is a Kubernetes controller and set of custom resources providing deployment strategies including blue-green, canary, canary analysis and experimentation. Its documentation justifies the controller on the grounds that in "large scale high-volume production environments, a rolling update is often considered too risky of an update procedure since it provides no control over the blast radius".

The Rollout resource is a drop-in replacement for a Kubernetes Deployment with additional strategy fields; workloads must be migrated to it, and the controller does not modify ordinary Deployments. Blue-green updates switch an "active" service between ReplicaSets while exposing a "preview" service, with optional pre- and post-promotion analysis; canary updates advance through weighting and pause steps.

Traffic shaping can be delegated to ingress controllers and service meshes, including Istio, Nginx, the AWS Application Load Balancer, Gateway API, the Service Mesh Interface and Traefik, with further routers available as plugins. Automated analysis queries metric providers such as Prometheus, Datadog, New Relic, Amazon CloudWatch and InfluxDB, or arbitrary web endpoints and Kubernetes Jobs, promoting or rolling back a release according to the result; since version 1.5 the maintainers have directed new metric integrations to a plugin interface rather than the core controller. A kubectl plugin and an optional dashboard provide visualisation and manual control.

Argo Events

Argo Events is an event-driven automation framework that can trigger actions in response to events from external systems, and is CloudEvents-compliant. Since the re-architecture that culminated in version 1.0 it has defined three custom resources: an EventSource that consumes events from an external system and republishes them; an EventBus that acts as the transport layer; and a Sensor that resolves event dependencies and fires triggers. A separate Gateway resource used in earlier versions was merged into EventSource.

Supported event sources include webhooks, message brokers such as Apache Kafka, NATS, MQTT and Apache Pulsar, cloud messaging and object-storage services from Amazon, Google and Microsoft, source-code hosts including GitHub, GitLab and Bitbucket, and Kubernetes resources, calendars and files. Triggers can create arbitrary Kubernetes objects, submit or manipulate Argo Workflows, act on Argo Rollouts, invoke AWS Lambda or Apache OpenWhisk functions, make HTTP requests, publish messages to a broker, or send notifications. The EventBus can be backed by NATS JetStream or Kafka; the original NATS Streaming implementation is deprecated.

Interoperability

Argo CD ships Lua health checks and resource actions for the other subprojects' custom resources, so that a paused Argo Rollout is reported as suspended in Argo CD and can be promoted, aborted or retried from its interface; a separate extension embeds the Rollouts dashboard in the Argo CD web interface. Argo Events can submit, resubmit, retry, suspend or terminate Argo Workflows, and Argo Workflows provides the API and user interface used to observe them. Argo Workflows resources such as CronWorkflow can in turn be managed by Argo CD, and Argo Workflows can share Argo CD's Dex instance for single sign-on. Each subproject can also be run on its own; the Rollouts documentation states that it does not require Argo CD to be installed on the same cluster.

argoproj-labs

Alongside the four graduated subprojects, the maintainers run a separate GitHub organization, argoproj-labs, which is "managed by the Argo project maintainers and not part of the CNCF Argo umbrella projects" and exists "to quickly run experiments, POCs and possibly new features to be later incorporated in one of the Argo projects". Its repositories include Argo CD Image Updater, the Argo CD Operator, Argo CD Autopilot, the Hera Python SDK, a GitOps promoter, and argocd-agent, a pull-based multi-cluster architecture in which agents on workload clusters connect inward to a central control plane. Red Hat ships an Argo CD Agent as part of Red Hat OpenShift Platform Plus.

Governance and contributors

Governance model

Argo is governed by its subproject leads and approvers rather than by a steering committee. The project's membership document defines a ladder of roles — member, reviewer, approver and lead — with quantified thresholds, such as three months' membership and review or authorship of at least five substantial pull requests for reviewer, and three months as a reviewer plus at least ten substantial pull requests for approver. Reviewers, approvers and leads are all considered maintainers, and sponsorship of new members "must be from multiple member companies to demonstrate integration across community".

Where consensus fails, decisions go to a vote of all maintainers, requiring a simple majority and a quorum of 30% — two-thirds for changes to governance itself. The governance document also limits the influence of any one employer: "No organization should be allowed more than 40% of eligible votes. If any organization has more than 40% of the maintainers, the organization will have to decide which maintainers will cast votes." Three recurring public meetings — for maintainers, contributors and the wider community — are held on the CNCF's calendar. Each subproject is expected to have two co-leads, chosen by consensus of existing leads and approvers after the vacancy is announced to the maintainer community, and the membership document states that "leads should reflect and represent the diversity of the Argo Community"; maintainers are treated as inactive after twelve months without significant contribution, measured through the Linux Foundation's LFX Insights service.

Maintainers and corporate participation

The project distinguishes its corporate maintainers — Akuity, BlackRock, Intuit, Octopus Deploy, Pipekit and Red Hat — from the wider body of contributors. Its MAINTAINERS.md file records the employer of each individual maintainer: Intuit has the largest group, followed by Akuity, Red Hat, Codefresh and Pipekit, together with about twenty maintainers at other organizations — among them Adobe, Acquia, Alibaba Cloud, Atlan, BlackRock, Chainguard, DaoCloud, Databricks, GetYourGuide, GoTo, Hyundai Autoever, Sage Intacct, Swiss Post, The Scale Factory and Verkada — and several who are listed as independent. That file's affiliation column lags the website, still recording Codefresh for maintainers whose employer became Octopus Deploy on the 2024 acquisition while listing other Octopus Deploy staff under that name. Alumni maintainers have been employed by Airbnb, Capital One, GitLab, Lacework, Red Hat and Salesforce, among others.

Argo's proposal for CNCF graduation records that "since joining the CNCF in April 2020 as an incubation-level project, the Argo Project has made great progress in growing the community of contributors and users including the addition of Red Hat and Codefresh along-side BlackRock as partners in governing and running the project". The same document lists the CNCF, Intuit, Akuity, BlackRock, Codefresh and Red Hat as the project's sponsors, and states that "the Argo governance committee consists of members from Intuit, Red Hat, Blackrock, and Codefresh".

The project has also recognized companies as corporate maintainers on its website. That list was introduced in a redesign in July 2021 with four names — Codefresh, Intuit, BlackRock and Red Hat — and Akuity was added in October 2021 and Pipekit in June 2024. In January 2026 the Codefresh entry was replaced by Octopus Deploy, which had acquired the company, giving the current list of Akuity, BlackRock, Intuit, Octopus Deploy, Pipekit and Red Hat.

Every subproject except Argo Events is led by two people employed by different companies: Argo CD by Michael Crenshaw of Intuit and Alexander Matyushentsev of Akuity; Argo Rollouts by Jesse Suen of Akuity and Zach Aller of Intuit; and Argo Workflows by Alan Clucas of Pipekit and Yuan Tang of Red Hat. Argo Events is led by Derek Wang of Intuit. Suen, whom the CNCF describes as an Argo co-creator, wrote the first Argo CD code at Intuit before co-founding Akuity; Danny Thomson, who created Argo Rollouts, is no longer listed as a maintainer.

The CNCF's 2022 Argo Project Journey Report identified Intuit, Codefresh, Akuity and Red Hat as the project's active vendor contributors and noted that "end users like Blackrock have contributed entire projects — Argo Events — and dozens more organizations like Swiss Post, Dyno, Alibaba.com, and Commonwealth Computer Research actively contribute today"; the report recorded contributions from more than 1,900 organizations since the project joined the foundation and stated that "the Argo team diligently maintains a healthy balance between the communities and their often disparate needs". Ed Lee framed end-user participation as the mechanism preventing single-vendor control: "I don't think you could have a vibrant, multi-vendor product like Argo without end-user participation. Without them, it would be a project that's primarily sponsored or dominated by one vendor."

The Argo Workflows maintainers have publicly sought additional reviewers. The subproject's contributing guide asks for more community involvement to keep it viable, and a sustainability initiative documented in the 3.6 release branch offered contributors prioritized review of their pull requests in exchange for a pledge of weekly hours.

ArgoCon

ArgoCon is the project's conference. The first edition was a one-day virtual event on December 8, 2021, hosted by Codefresh with Red Hat and Intuit, which the CNCF reported drew more than 4,000 attendees and 25 speakers. A second edition was held in Mountain View, California, on September 19–21, 2022 as a hybrid event organized by the CNCF Argo community. From 2023 the conference has run as a CNCF-hosted event co-located with KubeCon + CloudNativeCon; the first such edition was held during KubeCon Europe in Amsterdam in 2023, followed by a North American edition in Chicago on November 6, 2023, and the series has since continued in Europe, North America and, from 2026, Japan.

When the CNCF recognized Intuit as its Top End User in 2022, the citation noted that the company, "having contributed Argo … is a co-organizer of the ArgoCon conferences, which bring together thousands of Argo community members each year".

Relationship to GitOps

The term GitOps was coined by Alexis Richardson, co-founder and chief executive of Weaveworks, before the first Argo CD release; Argo CD is an implementation of the pattern rather than its origin. Gartner analyst Paul Delory later observed that "the initial definition of 'GitOps' was basically 'how Weaveworks works' … They deserve a lot of credit for creating this category."

A vendor-neutral definition came later. On November 19, 2020, Amazon, Codefresh, GitHub, Microsoft and Weaveworks announced the creation of the GitOps Working Group under the CNCF's App Delivery technical advisory group; the group's charter set out to "clearly define a vendor-neutral, principle-led meaning of GitOps" and listed the recommendation or endorsement of "specific projects, vendors or approaches to GitOps" among its explicit non-goals. The group's output, the OpenGitOps project, was accepted into the CNCF sandbox in January 2021. Version 1.0.0 of the GitOps Principles was tagged on October 8, 2021, and announced the following month, defining GitOps as declarative, versioned and immutable, pulled automatically, and continuously reconciled; the announcement, written by Codefresh's Dan Garfield — an Argo maintainer — and Scott Rigby, credited "over 60 companies, 96 interested parties, and 34 co-authors". The working group merged into the OpenGitOps project in March 2024.

The Argo maintainers separately drafted an Argo Conformance Program, intended to certify that third-party products interoperate and to "protect the Argo brand", but the document remains marked "currently in draft and non-binding".

Adoption

Each subproject maintains a USERS.md file to which organizations add themselves. In August 2026 these listed roughly 450 organizations for Argo CD, more than 200 for Argo Workflows, about 85 for Argo Rollouts and about 60 for Argo Events. Names on those lists include Adobe, Alibaba Group, Ant Group, BMW, Bosch, Capital One, CERN, Cisco, Deutsche Bank, Deutsche Telekom, Electronic Arts, GitHub, Google, IBM, Intuit, Major League Baseball, Mercedes-Benz, Mozilla, Nvidia, Peloton, Red Hat, Splunk, Swisscom, Tesla, Ticketmaster and Volvo Cars, although the entries are self-reported and each applies only to the subproject whose file lists it. The CNCF's graduation announcement in December 2022 reported production use by more than 350 organizations, citing Adobe, BlackRock, Capital One, Google, Intuit, PagerDuty, Peloton, Snyk, Swisscom, Tesla and Volvo, together with attributed statements from Adobe, BlackRock and CERN.

CNCF annual surveys, which measure "Argo" as a family rather than Argo CD alone, recorded a rise in reported usage from 10% in 2020 to 28% in 2022, and a 16% year-on-year rise in Argo's use as a tool for managing CI/CD pipelines in the 2024 edition; the survey published in January 2026 put Argo at 52% production use, with a further 20% of respondents evaluating it. Reporting on the 2024 survey, Cloud Native Now listed Argo as the second most widely used CI/CD platform at 45%, behind GitHub Actions.

Dynatrace's Kubernetes in the Wild report, which is based on observed telemetry from "billions of Kubernetes pods across thousands of Dynatrace customers" rather than self-reporting, found in its 2025 edition that Argo CD led continuous-delivery tooling and "saw the most significant increase in usage since 2022, with about a quarter of organizations now using the solution (up from 17% in 2022)".

Measured by contributors, Argo is among the largest CNCF projects. The CNCF stated in November 2024 that Argo "ranked in the top 3 CNCF projects and top 5 Linux Foundation projects" in its most recent project-velocity assessment, and TechTarget, citing the CNCF's 2023 annual report, recorded 927 code authors working on Argo that year. The CNCF's Argo project page reported 15,613 total contributors and 3,352 contributing organizations in August 2026.

Reporting Octopus Deploy's 2025 State of GitOps survey of 660 respondents, The New Stack wrote that "about 50% of companies that adhere to GitOps practices use Argo CD", noting that the figure was consistent with the CNCF's own survey findings while cautioning that "the survey respondents probably oversampled mature GitOps practitioners". An annual user survey run through Argo's own channels reported 269 responses in 2026 and described its sample as "heavily weighted towards the experiences of small to mid-sized companies".

Security

Audits and supply-chain assessments

Argo has been the subject of four published external assessments. Trail of Bits reviewed all four subprojects over three person-weeks between 1 and March 9, 2021, in an engagement commissioned by Intuit and the Linux Foundation, and reported 35 findings — none of high severity, three medium, sixteen low and sixteen informational. In February 2022 Ada Logics onboarded the project to OSS-Fuzz, developing 41 fuzzers and finding ten bugs, in work written up jointly by Ada Logics researchers and maintainers from Akuity, Red Hat and Intuit.

The principal audit followed in July 2022: funded by the CNCF and facilitated by the Open Source Technology Improvement Fund, Ada Logics reported 26 issues including one critical and four high-severity bugs, and added seven further fuzzers. The most serious was a cross-site scripting injection in Argo CD that "could allow an attacker to take admin control of the kubernetes cluster". In a retrospective, Argo CD lead Michael Crenshaw wrote that the audit had produced twenty-six issues — "seven in Argo CD, six in Argo Workflows, and thirteen in Argo Events" — of which seven led to CVEs for Argo CD and two for Argo Events, and that it had changed the project's threat model: "we used to consider source files from git as trusted. But due to the possibility of an adversarial tenant exploiting path traversal, we now must treat source files as potentially-malicious." In April 2023 Chainguard, working with the CNCF, assessed Argo CD's supply chain and concluded that its source, build and provenance met SLSA level 3. Argo CD holds a "passing" OpenSSF Best Practices badge, a self-certification cited by the CNCF as a graduation criterion.

Notable vulnerabilities and incidents

Argo CD and Argo Workflows have each been the subject of numerous published security advisories, while the Argo Rollouts repository had published none as of August 2026. The most widely reported was CVE-2022-24348, disclosed in February 2022: a directory traversal flaw in Argo CD's Helm handling, rated 7.7 (high), that let a user able to create or update Applications read arbitrary values files — and potentially credentials — from the repository server. It was found by Moshe Zioni of the application-security firm Apiiro and drew coverage in The Register, BleepingComputer and The New Stack. A JSON Web Token flaw scored 10.0 (critical), CVE-2022-29165, followed in May 2022, though it affected only instances on which anonymous access had been enabled, which is not the default. Separately, in July 2021 the security firm Intezer found misconfigured, internet-exposed Argo Workflows instances being used to run cryptocurrency miners; no CVE was assigned, as the exposure stemmed from configuration rather than a code defect, but the maintainers issued an advisory and changed the Argo Server's default authentication mode in version 3.0. The project's disclosure process has itself drawn criticism: TechTarget reported in March 2024 that three vulnerabilities found by the security firm KTrust took longer than the customary 90 days to disclose, and in July 2026 the French firm Synacktiv published an unpatched remote code execution path through the Argo CD repository server's gRPC interface that it said it had reported eighteen months earlier.

Commercial ecosystem

Several companies sell products and services built on Argo. Akuity, founded by three engineers who worked on Argo at Applatix and Intuit, offers a managed Argo platform and also develops Kargo, an environment-promotion tool that is not part of the Argo Project. Red Hat ships Argo CD as Red Hat OpenShift GitOps and integrates Argo Rollouts into the OpenShift user experience. Octopus Deploy, which acquired Codefresh in 2024, offers enterprise support for all four subprojects and an Argo CD integration in its own delivery platform. Pipekit provides managed Argo Workflows and employs two of that subproject's maintainers, including its lead. Among the major cloud providers, AWS offers a managed Argo CD service in Amazon EKS, while Microsoft Azure and Google Cloud ship Flux and Config Sync respectively as their GitOps options.

Codefresh launched a GitOps certification course based on Argo in January 2022; the CNCF's Journey Report stated that the program had passed 10,000 students by that August.

Building a business on GitOps tooling has proved difficult. Reviewing the closure of Weaveworks in 2024, Gartner analyst Paul Delory said of the company that had created the category that "a good idea doesn't always translate to a viable business model".

Reception

Third-party assessments of Argo CD grew more favorable as it matured. Thoughtworks placed it in the "Trial" ring of its technology radar in May 2020, recommending readers "give Argo CD a try", and the CNCF's own end-user technology radar on continuous delivery that year — based on 151 data points from 26 companies — placed it in the lowest "Assess" ring. A CNCF radar on DevSecOps published fifteen months later placed Argo CD in "Adopt", its highest ring.

Commentators have attributed Argo CD's popularity largely to its graphical interface and its breadth. TechTarget reported that the presence of a GUI was "a deciding factor for shops such as American Express", and The New Stack described Argo CD as "a full, opinionated platform with a web interface". InfoQ covered the 3.3 release in 2026 as bringing "safer GitOps deletions and smoother day-to-day operations". Gartner's Paul Delory cautioned in 2022 that GitOps in general remained an advanced practice: "You have to already be at a very, very advanced stage in your platform automation and your delivery pipelines before you can do something like GitOps right."

See also

• GitOps
• Flux
• Progressive delivery
• Kubeflow

External links

• Official website
• Argoproj on GitHub
• Argo at the Cloud Native Computing Foundation
• Inside Argo: Automating the Future – documentary produced by the CNCF, 2024

This article "Argo Project (software)" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Argo Project (software). Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.

---