GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Supabase and Velociraptor — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Velociraptor's recent releases are mostly about patching CVEs.
Velociraptor 0.77.3 shipped on October 5 as a bug fix and CVE release; it also adds an artifact that uploads server results to Azure Monitor and trims the columns emitted by the backup artifacts. 0.77.2 and a 0.76.7 backport in September and August were CVE fixes. The 0.77.1 feature release landed in June, but its notes in the feed only link out.
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.
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.
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.
Velociraptor 0.77.3 shipped on October 5 as a bug fix and CVE release; it also adds an artifact that uploads server results to Azure Monitor and trims the columns emitted by the backup artifacts. 0.77.2 and a 0.76.7 backport in September and August were CVE fixes. The 0.77.1 feature release landed in June, but its notes in the feed only link out.
Since June the project has been in security mode, fixing CVEs on the current line and backporting to the previous one. Feature work shows up as new artifacts, here an Azure Monitor export, which keeps Velociraptor feeding results into the logging tools teams already use.
Expect further 0.77 patch releases and possibly another backport if new CVEs are published; the timing of a 0.78 feature release is not signaled here.
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 Velociraptor.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
See all Supabase alternatives → · See all Velociraptor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Supabase and Velociraptor are shipping at a similar cadence (velocity 0.0 vs 0.0, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Supabase and Velociraptor are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Velociraptor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Velociraptor alternatives" section above for the current picks, or visit /alternatives/velociraptor for the full list with editorial commentary on each.