Rootly vs Auth0
Side-by-side trajectory, velocity, and editorial themes.
Rootly is moving the incident workflow out of the dashboard and into the IDE.
Rootly is shipping steadily across three lanes: on-call ergonomics (SLA follow-ups, deferred paging, team heartbeats), AI surfaces (Claude Code and Cursor plugins), and enterprise plumbing (Google Workspace directory sync, deeper RBAC). The cadence is roughly one release per week and the changes are coherent rather than scattershot — each lane is building toward a recognizable end-state.
The on-call work is a maturation arc: features that used to be coarse (paging, heartbeats, follow-ups) are gaining ownership, scheduling, and SLA awareness. The AI work is the more interesting axis — pulling on-call context, retros, and incident state into Claude Code and Cursor signals that Rootly wants engineers to interact with the platform inside their editor, not by tabbing away to a separate UI.
Expect the IDE plugins to gain write-side actions next (acking pages, drafting retros, triggering runbooks from the editor), and on-call configuration to keep moving toward team-scoped, RBAC-aware defaults rather than global ones.
Auth0 ships Auth for MCP GA and starts unbundling the rest of identity for AI agents.
Auth0 just made Auth for MCP generally available — a bundle of CIMD client registration, On-Behalf-Of token exchange, and OAuth resource-parameter compatibility purpose-built for AI agents talking to MCP servers. Around it, the team is reworking core identity primitives: non-unique emails reached GA, online refresh tokens entered beta with session binding, and the Account API now supports step-up auth for sensitive scopes. Smaller polish items (CMD+K palette, Resend GA, signing algorithm coverage) round out the release stream.
Auth0 is repositioning from a B2C/B2B login provider to an authorization layer for agent ecosystems. The MCP work is the centerpiece, but the supporting moves — session-bound refresh tokens, step-up auth on the Account API, non-unique emails — all point at use cases where users, agents, and resources have more complex relationships than classic OIDC was designed for. Outbound event streams to AWS EventBridge and Okta Workflows extend the same direction outward.
Expect Auth for MCP to gain a managed catalog of pre-vetted MCP clients and deeper Actions-based policy hooks for OBO token exchange, plus online refresh tokens reaching GA within a quarter.
See more alternatives to Rootly →
See more alternatives to Auth0 →