Drizzle ORM
Drizzle's v1.0 release candidates land a JIT mapper rework, new codecs, and a breaking casing API
Comparison · Infra & APIs
Clerk vs Depot
A side-by-side editorial comparison of Clerk and Depot — release velocity, themes, recent moves, and the top alternatives to consider.
Clerk vs Depot: at a glance
| Feature | Clerk | Depot |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 7.5 | 7.5 |
| Sparks · 30d | 0 | 1 |
| Top themes | agentic auth, api keys, scim directory sync, developer cli | ci-cd, container-builds, agent-compute, sandboxes |
| Last editorial update | 1mo ago | 5d ago |
| Website | Visit → | — |
What is Clerk?
Clerk shipped a CLI for humans and agents, monetized API Keys, and graduated SCIM — auth for the agentic era.
April was a strategically dense month. Clerk shipped a new CLI that the company explicitly frames as a tool for both developers and their agents to manage authentication and billing. API Keys went GA with usage-based pricing live (1,000 free creations and 100,000 verifications monthly, then per-unit). SCIM Directory Sync went GA with custom attribute mapping and IdP-group role assignment in beta. Smaller items rounded it out: Expo JSON theming for native components, infinite-scroll dashboard tables, test-user filtering in analytics, and Clerk Billing additions (annual-only plans, seat-limited plans). The captured feed also picked up the marketing landing page mentioning a $50M Series C.
What is Depot?
Depot turns its build-acceleration compute into a metered backend for AI agents.
Depot is shipping fast across two fronts: hardening its CI platform and opening its compute to AI workloads. Recent CI work includes native step retries, durable cache disks, and a generally available API and CLI with full dashboard parity. On the AI front it added SOCI v2 to cut startup time for large CUDA and PyTorch images and launched a Sandbox SDK to run untrusted or agent-generated code in ephemeral, billed sandboxes.
Clerk vs Depot: editorial side-by-side
Clerk
7.5INFRA · APIS
Clerk shipped a CLI for humans and agents, monetized API Keys, and graduated SCIM — auth for the agentic era.
◆ Current state
April was a strategically dense month. Clerk shipped a new CLI that the company explicitly frames as a tool for both developers and their agents to manage authentication and billing. API Keys went GA with usage-based pricing live (1,000 free creations and 100,000 verifications monthly, then per-unit). SCIM Directory Sync went GA with custom attribute mapping and IdP-group role assignment in beta. Smaller items rounded it out: Expo JSON theming for native components, infinite-scroll dashboard tables, test-user filtering in analytics, and Clerk Billing additions (annual-only plans, seat-limited plans). The captured feed also picked up the marketing landing page mentioning a $50M Series C.
◆ Where it's heading
Two arcs are converging. First, Clerk is staking out auth-for-agents: the CLI is designed to be agent-callable, API Keys are the substrate agents need to act on behalf of users, and the metered billing model lets that scale without per-seat friction. Second, Clerk is closing the enterprise B2B feature gap with SCIM Directory Sync GA — the move that lets it sell into IT-procurement-driven deals where WorkOS has been winning. The Billing surface continues to deepen, increasingly looking like a real billing product rather than just an auth add-on.
◆ Prediction
Expect the Clerk CLI to gain MCP-friendly commands and scripted-onboarding templates within a release or two, and the SCIM beta features (custom attributes, role assignment) to graduate quickly given the GA framing. Clerk Billing's monetization surface should keep widening — usage-based metering for more primitives, possibly tied to AI/agent activity directly.
Depot
7.5INFRA · APIS
Depot turns its build-acceleration compute into a metered backend for AI agents.
◆ Current state
Depot is shipping fast across two fronts: hardening its CI platform and opening its compute to AI workloads. Recent CI work includes native step retries, durable cache disks, and a generally available API and CLI with full dashboard parity. On the AI front it added SOCI v2 to cut startup time for large CUDA and PyTorch images and launched a Sandbox SDK to run untrusted or agent-generated code in ephemeral, billed sandboxes.
◆ Where it's heading
Depot is extending from build and CI acceleration toward being a general compute backend for agents. The Sandbox SDK, the agent-friendly GA API, and ML-image startup optimizations point the same way: sell fast, isolated, metered compute that AI tools and pipelines can drive programmatically. The CI improvements keep the core product sticky while the platform broadens.
◆ Prediction
Expect the Sandbox SDK to move toward general availability with more language and filesystem surface, and continued convergence of CI and sandbox compute under one metered, API-first platform.
Alternatives to Clerk and Depot
Other Infra & APIs 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 Clerk or Depot.
Warp
Warp drops the terminal framing to bet on cloud software factories and agent orchestration
Unleash
Unleash leans hard into AI-agent governance and self-hosting as its crawled feed fills with thought-leadership.
GitHub
GitHub spends the week hardening enterprise governance and supply-chain security.
Resend
Resend keeps widening from a raw email API into agent-native tooling and audience management.
Daytona
Very high-cadence sandbox infra building the primitives agents need to run code
Recent activity from Clerk and Depot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8d agoDepotSOCI v2 support for Depot container builds
- 9d agoDepotSandbox SDK is now available in private beta ⚡
- 15d agoDepotNative step retries in Depot CI
- 17d agoDepotDurable cache disks for Depot CI jobs are now available in beta
- 23d agoDepotDepot CI API and CLI are now generally available
- 24d agoDepotSSH into Depot CI sandboxes now uses exec.depot.dev
- 1mo agoClerkImproved observability with Application Logs
- 2mo agoClerkClerk CLI ⚡
- 2mo agoClerkScraping artifact: marketing homepage (notes Series C, not a release)
- 2mo agoClerkAPI Keys General AvailabilityCategoryProductPublishedApr 17API keys are now generally available, with usage-based billing now active.API… ⚡
- 2mo agoClerkDuplicate: API Keys General Availability (short-form copy)
- 2mo agoClerkDirectory Sync (SCIM) is now generally availableCategoryOrganizationsPublishedApr 16Directory Sync is now available to all users, with ne…
Frequently asked questions
What is the difference between Clerk and Depot?
They serve adjacent needs but don't currently overlap on shipped themes. Clerk and Depot are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Clerk better than Depot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Clerk and Depot are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Clerk?
Top Clerk alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Clerk alternatives" section above for the current picks, or visit /alternatives/clerk for the full list with editorial commentary on each.
What are the best alternatives to Depot?
Top Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot for the full list with editorial commentary on each.