← Back to home
Comparison · DevOps

Argo CD vs HashiCorp

Side-by-side trajectory, velocity, and editorial themes.

A
Argo CD
DEVOPS
6.3

Argo CD's 3.5 line is in release-candidate hardening after a feature-heavy rc1 (Helm 4, supply-chain, Gateway API).

◆ Current state

Argo CD shipped 3.4.0 to GA and has moved the 3.5 line into release candidates. The 3.5.0-rc1 carried a large feature set: Helm 3-to-4 migration, opt-in source-integrity verification for the hydrator, Gateway API support in the network view, mTLS in the repo-server, server-operation impersonation, and ApplicationSet UI work, while rc2 is bug-fix stabilization. The project keeps a strong supply-chain posture with cosign-signed images and SLSA Level 3 provenance.

◆ Where it's heading

Argo CD is converging 3.5 toward GA, so expect further rc bug-fix rounds until it stabilizes. The 3.5 theme blends supply-chain security (source integrity, provenance, mTLS), ecosystem currency (Helm 4, Gateway API), and ApplicationSet and UI maturation. After GA, the rolling stable tag advances and the 3.4 line drops to maintenance cherry-picks.

◆ Prediction

Expect one or more further 3.5.0 release candidates with bug-fix cherry-picks, then a 3.5.0 GA that moves the rolling stable tag forward.

HashiCorp logo
HashiCorp
DEVOPS
8.8

HashiCorp pushes an infrastructure graph and Boundary 1.0 while reorienting around AI-agent access

◆ Current state

HashiCorp is layering two moves on top of its IaC and secrets core: a graph-based source of truth for sprawling multi-cloud estates, and a steady buildout of access control for AI agents. Boundary reached 1.0 with session recording, Vault and Boundary both shipped agent-security previews, and HCP gained SCIM provisioning. The through-line is governing who — and increasingly what — can touch infrastructure.

◆ Where it's heading

Terraform is being repositioned from provisioning tool to system-of-record via Infragraph, while Boundary and Vault extend privileged access from humans to autonomous agents. The AI-agent framing recurs across nearly every release, suggesting HashiCorp sees agent access as the next control-plane contest. Expect the graph and the access layer to knit into a single governance story.

◆ Prediction

Likely next: Infragraph moving from limited to general availability, and more concrete Vault and Boundary primitives for scoping and recording AI-agent sessions.

See more alternatives to Argo CD
See more alternatives to HashiCorp