Sanity
Sanity is turning real-time collaboration into a convergence guarantee, SDK release by release.
A side-by-side editorial comparison of Argo CD and HashiCorp — release velocity, themes, recent moves, and the top alternatives to consider.
Argo CD's 3.5 line is in release-candidate hardening after a feature-heavy rc1 (Helm 4, supply-chain, Gateway API).
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.
HashiCorp pushes secure-infrastructure primitives deeper into Kubernetes, identity, and a new infra graph
The changelog is drawn from HashiCorp's blog, so it mixes genuine product launches with thought-leadership posts. Underneath the marketing surface, the real product motion is concentrated in Vault, Boundary, and HCP: Kubernetes key management, session-recording resilience, SCIM provisioning, and a new graph layer for Terraform. The company is deepening its secure-infrastructure stack rather than expanding into new categories.
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.
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.
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.
The changelog is drawn from HashiCorp's blog, so it mixes genuine product launches with thought-leadership posts. Underneath the marketing surface, the real product motion is concentrated in Vault, Boundary, and HCP: Kubernetes key management, session-recording resilience, SCIM provisioning, and a new graph layer for Terraform. The company is deepening its secure-infrastructure stack rather than expanding into new categories.
HashiCorp is consolidating its portfolio around a single governed view of infrastructure—Infragraph as a source of truth, SCIM for identity lifecycle, Vault reaching into Kubernetes etcd encryption. The recurring framing of 'the AI era' and agent access signals where this is heading: positioning Vault and Boundary as the control plane for both human and agent access to infrastructure.
Expect Infragraph to move from limited to broader availability and more Boundary and Vault features framed explicitly around securing AI-agent access.
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Argo CD or HashiCorp.
Sanity is turning real-time collaboration into a convergence guarantee, SDK release by release.
Rivet is pivoting from actor infrastructure into agentOS, a runtime built for coding agents.
Auth0 keeps widening its enterprise identity surface, one GA at a time
GitHub is building the governance layer for AI-written code.
Gravity Forms pushes toward a 3.0 platform while its add-on ecosystem keeps shipping.
A time-series engine that has quietly become capital-markets infrastructure
See all Argo CD alternatives → · See all HashiCorp alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within DevOps. HashiCorp is currently shipping more aggressively (velocity 7.5 vs 6.3), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HashiCorp is currently shipping more aggressively (velocity 7.5 vs 6.3), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Argo CD alternatives in DevOps are ranked by recent ship velocity. Browse the "Argo CD alternatives" section above for the current picks, or visit /alternatives/argo-cd for the full list with editorial commentary on each.
Top HashiCorp alternatives in DevOps are ranked by recent ship velocity. Browse the "HashiCorp alternatives" section above for the current picks, or visit /alternatives/hashicorp for the full list with editorial commentary on each.