Depot vs WorkOS
Side-by-side trajectory, velocity, and editorial themes.
Depot extends from build acceleration into hosted source control with Depot Code.
Depot is broadening from a CI and build-cache company into a full developer-infrastructure platform. This cycle it launched Depot Code — a diskless git server backed by S3 blob storage — into private beta, moved CI and Sandboxes onto a re-architected Depot Metal compute tier, and kept extending Depot CI with new triggers, snapshot improvements, OIDC auth, and Datadog observability.
The direction is a vertically integrated build-and-source stack: Depot Code stores git packfiles as S3 objects and runs stateless git workers, mirroring the same storage-compute separation behind Depot Metal. Each piece plugs into Depot CI, so the company is assembling an end-to-end alternative to the hub-and-spoke GitHub model rather than just accelerating it. The CI surface is maturing in parallel with reliability and integration features.
Expect Depot Code to move toward wider access and tighter Depot CI integration, and GitHub Actions runners and container builds to migrate onto Depot Metal over the coming months as promised.
WorkOS ships three new surfaces in a week, pushing into front-end widgets and agent-run admin.
WorkOS is an enterprise identity and auth infrastructure provider, best known for AuthKit, SSO, directory sync, and audit logs. The changelog shows an unusually dense shipping burst: three distinct new product surfaces in a single week, the Widgets API, a Management MCP server, and an API Gateway, layered on top of steady AuthKit feature work like step-up authentication, waitlists, and an Astro integration.
Two directions are visible. First, AuthKit is growing from a backend auth library into a fuller front-end toolkit, adding client widgets, framework SDKs, and richer session flows. Second, the platform is becoming programmable by agents and unified at the edge, via the MCP server and the API Gateway. WorkOS is moving up the stack from backend primitives toward client UI and agent-driven administration.
Expect more AuthKit framework integrations and additional agent-facing tooling built on the MCP server, plus broadening coverage for the newer Widgets API and API Gateway. The pace suggests WorkOS is racing to own both the front-end auth UI layer and the agent-administration layer at once.
See more alternatives to Depot →
See more alternatives to WorkOS →