Unleash
Feature flags repositioned as the runtime kill switch for AI agents writing your code.
Comparison · Infra & APIs
Depot vs Supabase
A side-by-side editorial comparison of Depot and Supabase — release velocity, themes, recent moves, and the top alternatives to consider.
Depot vs Supabase: at a glance
| Feature | Depot | Supabase |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs, DevOps |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | ci-cd, build-acceleration, test-analytics, source-control | secure-defaults, breaking-changes, row-level-security, postgrest |
| Last editorial update | 1d ago | 12d ago |
| Website | — | Visit → |
What is Depot?
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
Depot has spent the last month building outward from build acceleration. Test results went generally available with JUnit ingest, org-wide flaky and slow test analytics, and timing-based shard balancing. Underneath that, Depot Metal moved CI and Sandboxes onto bare-metal microVMs the company controls end to end, and Depot Code entered private beta as a diskless git server backed by blob storage. The smaller releases fill in the surrounding surface: Tailscale access to private networks, GitLab OIDC, Datadog CI Visibility, stacked pull requests, and macOS 26 runners on M4.
What is Supabase?
Supabase is closing its most-exploited default: tables stop being public unless you say so.
The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.
Depot vs Supabase: editorial side-by-side
Depot
6.3INFRA · APIS
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
◆ Current state
Depot has spent the last month building outward from build acceleration. Test results went generally available with JUnit ingest, org-wide flaky and slow test analytics, and timing-based shard balancing. Underneath that, Depot Metal moved CI and Sandboxes onto bare-metal microVMs the company controls end to end, and Depot Code entered private beta as a diskless git server backed by blob storage. The smaller releases fill in the surrounding surface: Tailscale access to private networks, GitLab OIDC, Datadog CI Visibility, stacked pull requests, and macOS 26 runners on M4.
◆ Where it's heading
Each layer Depot adds is one it previously rented — compute from cloud runners, source hosting from GitHub, test insight from nothing at all. Owning the storage and hypervisor tiers is what makes the performance claims possible, and owning test data is what turns a build accelerator into something that reports on the pipeline rather than just running it faster. The pattern suggests Depot is positioning as the full CI platform, with speed as the entry point rather than the product.
◆ Prediction
Depot Code should move from private to open beta with tighter Depot CI integration, since a git server the company controls is what makes source-aware caching and test selection possible. Expect the test analytics to grow toward selecting which tests to run, not only how to split them.
Supabase
0.0INFRA · APISDEVOPS
Supabase is closing its most-exploited default: tables stop being public unless you say so.
◆ Current state
The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.
◆ Where it's heading
Supabase is paying down the security cost of its own convenience. Auto-exposing every public-schema table made the product fast to start with and easy to misconfigure; the fix is explicit Postgres grants, staged over six months from new projects in April to all existing projects on October 30. The RLS Tester is the same theme from the other side — the auto-exposure default only worked if row-level security was correct, and until now there was no way to check.
◆ Prediction
Expect the remaining rollout dates to hold and more of the developer experience to be rebuilt around explicit grants, with the RLS Tester graduating from preview as it becomes the tool people need to verify the new model. The October cutover for existing projects is the moment where this stops being an announcement and starts breaking things.
Alternatives to Depot and Supabase
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 Depot or Supabase.
Kubernetes
The blog has become a teaching channel, with the real releases arriving as Gateway API and deprecation notices.
ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
GitHub
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
See all Depot alternatives → · See all Supabase alternatives →
Recent activity from Depot and Supabase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
- 9d agoDepotDepot CI now supports native GitHub stacked pull requests
- 14d agoDepotTest results are now generally available ⚡
- 22d agoDepotAI analysis available for all Depot CI workflows and jobs
- 28d agoDepotSplit CI test suites with historical timing data (beta)
- 1mo agoDepotDepot CI now supports Tailscale
- 3mo agoSupabaseDeprecation Notice: Dropping Support for Node.js 20
- 3mo agoSupabaseDeveloper Update - May 2026
- 3mo agoSupabaseBreaking Change: OAuth token endpoint will return HTTP 200 instead of 201
- 3mo agoSupabaseBreaking Change: Tables not exposed to Data and GraphQL API automatically ⚡
- 3mo agoSupabaseFragment of the no-auto-expose announcement
- 3mo agoSupabaseFeature Preview: RLS Tester
Frequently asked questions
What is the difference between Depot and Supabase?
They serve adjacent needs but don't currently overlap on shipped themes. Depot 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 Depot better than Supabase?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot 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 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.
What are the best alternatives to Supabase?
Top Supabase alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Supabase alternatives" section above for the current picks, or visit /alternatives/supabase for the full list with editorial commentary on each.