Buildkite
Buildkite is forcing a major agent upgrade and handing agents a shortcut through failures.
Comparison · Infra & APIs
Expo vs Clerk
A side-by-side editorial comparison of Expo and Clerk — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:observability
Expo vs Clerk: at a glance
| Feature | Expo | Clerk |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | react-native, eas, mcp, ci-cd | authentication, machine-auth, agent-tooling, scim |
| Last editorial update | 2h ago | 2h ago |
| Website | — | Visit → |
What is Expo?
Expo shut down its own coding agent and kept the MCP server — it wants to be the substrate.
Two SDK releases landed in quick succession, 56 in May and 57 at the end of June, alongside steady EAS work: Maestro test insights with flake detection, automated iOS device registration in Workflows, and a general availability date for EAS Observe. On the AI side the direction reversed — the Expo MCP Server became available on the free plan in May, and in July the Expo Agent closed beta ended with the project wound down. Entry bodies in this feed are thin, so specifics beyond the headlines are limited.
What is Clerk?
Clerk is building auth for machines: API keys, a CLI agents can drive, per-verification pricing.
Two threads dominate. The first is machine authentication: API keys reached general availability with usage-based billing at $0.001 per creation and $0.00001 per verification, and a new CLI is described as a tool for developers and their agents to manage auth and billing. The second is enterprise readiness — Directory Sync (SCIM) generally available with custom attribute mapping and IdP role assignment, plus an Application Logs event stream across auth, billing, and organizations. Dashboard polish and Expo theming fill in around them.
Expo vs Clerk: editorial side-by-side
Expo
6.3INFRA · APIS
Expo shut down its own coding agent and kept the MCP server — it wants to be the substrate.
◆ Current state
Two SDK releases landed in quick succession, 56 in May and 57 at the end of June, alongside steady EAS work: Maestro test insights with flake detection, automated iOS device registration in Workflows, and a general availability date for EAS Observe. On the AI side the direction reversed — the Expo MCP Server became available on the free plan in May, and in July the Expo Agent closed beta ended with the project wound down. Entry bodies in this feed are thin, so specifics beyond the headlines are limited.
◆ Where it's heading
Expo is consolidating around the build, test, and observe pipeline it already owns and stepping back from competing on the agent itself. Making the MCP server free while retiring Expo Agent puts the company underneath whichever assistant a developer already uses, rather than asking them to adopt another one. EAS is where the commercial weight sits, and the recent releases all reduce the manual work between a commit and a working build on a device.
◆ Prediction
Expect EAS Observe's August general availability to anchor the next stretch, with AI effort staying on the MCP surface that connects outside assistants to Expo projects.
Clerk
0.0INFRA · APIS
Clerk is building auth for machines: API keys, a CLI agents can drive, per-verification pricing.
◆ Current state
Two threads dominate. The first is machine authentication: API keys reached general availability with usage-based billing at $0.001 per creation and $0.00001 per verification, and a new CLI is described as a tool for developers and their agents to manage auth and billing. The second is enterprise readiness — Directory Sync (SCIM) generally available with custom attribute mapping and IdP role assignment, plus an Application Logs event stream across auth, billing, and organizations. Dashboard polish and Expo theming fill in around them.
◆ Where it's heading
Clerk is extending from human sign-in toward credentials for software acting on a user's behalf, and pricing that surface by the call rather than by the seat. The CLI framing makes the direction explicit: the control plane should be operable by an agent, not only by a person in a dashboard. Meanwhile SCIM, logs, and billing controls are the enterprise checklist that lets it sell upmarket while that bet plays out.
◆ Prediction
Expect the machine authentication suite to deepen around delegated and scoped access for agents — finer-grained key permissions or short-lived credentials — with usage-based pricing extended to whatever ships next.
Alternatives to Expo and Clerk
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 Expo or Clerk.
Statsig
Statsig is packaging its own workflows as skills for someone else's agent to run.
Rootly
Rootly's AI stops summarizing incidents and starts investigating them.
Knock
Notification infrastructure grows a memory: workflows can now wait on the real world.
WorkOS
Auth infrastructure that agents can drive and developers can run locally.
Airbyte
Airbyte 2.0 made the pipeline run both ways: data activation turns the warehouse into a source.
Recent activity from Expo and Clerk
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agoExpoExpo Agent: ending the closed beta and winding the project down ⚡
- 10d agoExpoEAS Observe moves to general availability on August 20
- 1mo agoExpoExpo SDK 57
- 1mo agoExpoMaestro testing: insights, clearer results, and faster retries
- 1mo agoExpoAutomate iOS device registration for internal builds in EAS Workflows
- 2mo agoExpoThe Expo MCP Server is now available on the Free plan
- 2mo agoClerkImproved observability with Application Logs
- 3mo agoClerkClerk CLI ⚡
- 3mo agoClerkClerk homepage captured as a changelog entry
- 3mo agoClerkAPI keys reach GA with usage-based billing active
- 3mo agoClerkAPI Keys General Availability
- 3mo agoClerkTheme Expo native components from a JSON fileCategorySDKPublishedApr 16@clerk/expo now supports a JSON-based theme for native iOS and And…
Frequently asked questions
What is the difference between Expo and Clerk?
Both compete on the same themes — observability — within Infra & APIs. Expo is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Expo better than Clerk?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Expo is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Expo?
Top Expo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Expo alternatives" section above for the current picks, or visit /alternatives/expo for the full list with editorial commentary on each.
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.