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 Retool — 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.
Retool is giving its app-building agent the branching model human developers already had.
Retool's changelog splits cleanly in two. The app builder is accumulating agent and version-control mechanics — several agent conversations open per branch, checkout of branches created outside Retool, and an agent that asks clarifying questions before building. The other half is enterprise housekeeping: BYOK AI token usage now has an endpoint and an analytics page, Microsoft SQL integration versions 1.0 and 2.0 are deprecated in favor of 3.0, and self-hosted instances moving to 4.31 must run a one-time permissions database migration.
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.
Retool's changelog splits cleanly in two. The app builder is accumulating agent and version-control mechanics — several agent conversations open per branch, checkout of branches created outside Retool, and an agent that asks clarifying questions before building. The other half is enterprise housekeeping: BYOK AI token usage now has an endpoint and an analytics page, Microsoft SQL integration versions 1.0 and 2.0 are deprecated in favor of 3.0, and self-hosted instances moving to 4.31 must run a one-time permissions database migration.
The agent is being fitted into an existing engineering workflow rather than placed beside it: branches, parallel threads, and clarification before action are all borrowed from how teams already review code. On the operations side Retool is billing customers for their own model keys and pruning integration versions, which is what a platform does when self-hosted enterprise deployments are the base it has to keep upgradeable. Edge channel releases keep arriving for self-hosted organizations at roughly weekly intervals.
The branch and thread work points toward the app-building agent being usable by more than one person at a time on the same app, so review and merge mechanics are the natural next step. The MS SQL deprecation notice sets up a forced cutover that Retool will have to date.
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 Retool.
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.
Five of six VictoriaMetrics entries are scraped GitHub page furniture; one is a real LTS patch.
Buildkite is forcing a major agent upgrade and handing agents a shortcut through failures.
See all Supabase alternatives → · See all Retool alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Retool is currently shipping more aggressively (velocity 6.3 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Retool is currently shipping more aggressively (velocity 6.3 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.
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 Retool alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Retool alternatives" section above for the current picks, or visit /alternatives/retool for the full list with editorial commentary on each.