Windmill
A workflow engine where the AI builds the scripts and the enterprise gates come down
A side-by-side editorial comparison of Supabase and VictoriaMetrics — 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.
Five of six VictoriaMetrics entries are scraped GitHub page furniture; one is a real LTS patch.
The feed is largely broken. Entries titled Appearance settings, Code security, Secret protection, SUPPORT & SERVICES and Enterprise platform are fragments of GitHub.com navigation chrome, most with no source URL and one pointing at docs.github.com. The single genuine release is v1.136.6 on the v1.136.x LTS line, carrying an Alpine base-image upgrade from 3.23.3 to 3.23.4 and bugfixes shared with the community build.
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.
The feed is largely broken. Entries titled Appearance settings, Code security, Secret protection, SUPPORT & SERVICES and Enterprise platform are fragments of GitHub.com navigation chrome, most with no source URL and one pointing at docs.github.com. The single genuine release is v1.136.6 on the v1.136.x LTS line, carrying an Alpine base-image upgrade from 3.23.3 to 3.23.4 and bugfixes shared with the community build.
What can be read from one real entry is maintenance discipline: a 12-month-supported LTS branch getting security and defect backports that also land in the community release. Product direction cannot be read from this feed at all until the crawl source is corrected.
Expect continued v1.136.x patch releases on the LTS support cadence. Any claim about feature direction would not be grounded in these entries.
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 VictoriaMetrics.
A workflow engine where the AI builds the scripts and the enterprise gates come down
Pressable is shipping near-daily, and MCP is being maintained as a peer surface to its API.
Cosmic retired AI Studio and gave its agents goals — the CMS is becoming an agent runtime.
Pipedream put OAuth on its 10,000-tool MCP server and annotated every tool read or write.
Buildkite is forcing a major agent upgrade and handing agents a shortcut through failures.
Statsig is packaging its own workflows as skills for someone else's agent to run.
See all Supabase alternatives → · See all VictoriaMetrics 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 VictoriaMetrics 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 VictoriaMetrics 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 VictoriaMetrics alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "VictoriaMetrics alternatives" section above for the current picks, or visit /alternatives/victoriametrics for the full list with editorial commentary on each.