Kinde vs Rivet
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.
Rivet pivots from actor backend to a coding-agent OS, and is building the ecosystem to match.
Rivet began as an actor and serverless backend platform — RivetKit, Rivet Actors, Rivet Compute — and has spent the last month reorienting around agentOS, a WebAssembly-based Linux environment for running coding agents without a heavy sandbox. The June and July releases show both threads running in parallel: native language SDKs (Rust, Effect) for Actors, and a fast-maturing agentOS that now has its own package registry.
The center of gravity is shifting from hosting stateful actors to being the runtime coding agents execute inside. agentOS went from a v0.2 sandbox alternative to shipping a package registry and a sub-millisecond package manager in under two weeks, a sign Rivet wants to own the developer surface around agent execution, not just the compute underneath it.
Expect agentOS to keep accreting ecosystem pieces — more registry content and tighter orchestration — while the Actors SDKs settle toward maintenance. A likely next move is deeper coupling between agentOS and Rivet Compute so agents run on Rivet's own cloud.
See more alternatives to Kinde →
See more alternatives to Rivet →