← Back to home
Comparison · Infra & APIs

Supabase vs werf

A side-by-side editorial comparison of Supabase and werf — release velocity, themes, recent moves, and the top alternatives to consider.

Supabase vs werf: at a glance

FeatureSupabasewerf
SectorInfra & APIs, DevOpsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themessecure-defaults, breaking-changes, row-level-security, postgrestgitops, kubernetes, ci-cd, buildah
Last editorial update1mo ago13h ago
WebsiteVisit →Visit →

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.

Read the full Supabase trajectory →

What is werf?

werf's v3 dev track ships multi-namespace cleanup scanning and JSON config schemas in rapid succession

werf runs two parallel release channels: v2.79.x (alpha/beta, the stabilizing line) and v3.x (dev, where new features land first). The v3 track has shipped three releases in under two weeks, adding JSON schemas for werf config files (enabling IDE validation), multi-namespace cleanup scanning, and renderPatches support for post-render Helm modification. The v2 channel is converging on the same features through backports, with bug fixes dominating recent releases.

Read the full werf trajectory →

Supabase vs werf: editorial side-by-side

Supabase logo
Supabase
INFRA · APISDEVOPS
0.0

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.

W
werf
INFRA · APIS
5.0

werf's v3 dev track ships multi-namespace cleanup scanning and JSON config schemas in rapid succession

◆ Current state

werf runs two parallel release channels: v2.79.x (alpha/beta, the stabilizing line) and v3.x (dev, where new features land first). The v3 track has shipped three releases in under two weeks, adding JSON schemas for werf config files (enabling IDE validation), multi-namespace cleanup scanning, and renderPatches support for post-render Helm modification. The v2 channel is converging on the same features through backports, with bug fixes dominating recent releases.

◆ Where it's heading

The v3 dev track is steadily building a production-ready feature set: JSON config schemas close a long-standing IDE integration gap, multi-namespace cleanup addresses GitOps hygiene at enterprise scale, and the netavark migration (replacing CNI/slirp4netns) aligns the buildah runtime with the current Podman network stack. The convergence between v3 features and v2 backports suggests v3 is being positioned for a stable release in the coming months.

◆ Prediction

Multi-namespace cleanup will likely backport to v2.79 once it stabilizes in v3.6. Expect v3 to enter beta status as the feature gap with v2 closes — the pace of shipping into the dev channel has been high enough that a beta designation is the natural next step.

Alternatives to Supabase and werf

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 Supabase or werf.

See all Supabase alternatives → · See all werf alternatives →

Recent activity from Supabase and werf

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 22h agowerfv3.6.0: multi-namespace cleanup scan
  2. 2d agowerfv2.79.1: bug fixes for metadata sync and Harbor deletion
  3. 2d agowerfv3.5.0: JSON config schemas and renderPatches support
  4. 3d agowerfv2.79.0: version in build report, ReleaseInstall resources
  5. 15d agowerfv2.78.2: stop re-compressing parent layers on push
  6. 16d agowerfv3.4.0: switch rootless builds to netavark network stack
  7. 4mo agoSupabaseDeprecation Notice: Dropping Support for Node.js 20
  8. 4mo agoSupabaseDeveloper Update - May 2026
  9. 4mo agoSupabaseBreaking Change: OAuth token endpoint will return HTTP 200 instead of 201
  10. 5mo agoSupabaseBreaking Change: Tables not exposed to Data and GraphQL API automatically ⚡
  11. 5mo agoSupabaseFragment of the no-auto-expose announcement
  12. 5mo agoSupabaseFeature Preview: RLS Tester

Frequently asked questions

What is the difference between Supabase and werf?

They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Supabase better than werf?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 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.

What are the best alternatives to werf?

Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.