Kinde vs Argo CD
Side-by-side trajectory, velocity, and editorial themes.
Kinde broadens its auth surface to passkeys while building out billing and B2B controls.
Kinde is shipping monthly feature roundups that consistently advance three fronts: authentication breadth, self-serve billing, and enterprise/B2B controls. The latest release adds passkeys (WebAuthn/FIDO2) for passwordless sign-in, the clearest capability jump in the window. Recent months also brought WhatsApp verification, IdP-initiated SAML, invite controls, and an MCP server for AI agents — a developer-focused auth platform widening on every axis.
Kinde is racing to close the feature gap with incumbent auth providers while differentiating on developer experience and built-in monetization. Authentication is going passwordless and omni-channel (passkeys, WhatsApp, SAML), billing is becoming a first-class self-serve product, and the MCP server stakes an early claim on auth for AI agents. The direction is a single platform that handles identity and billing together.
Expect continued enterprise hardening — likely deeper SSO/SCIM and organization-level controls — paired with more billing automation, as Kinde pushes up-market into B2B.
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.
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.
See more alternatives to Kinde →
See more alternatives to Argo CD →