GitHub
GitHub shut down its model catalog and shipped stacked pull requests on the same day.
A side-by-side editorial comparison of Retool and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A workflow engine where the AI builds the scripts and the enterprise gates come down
Windmill's July stream is dominated by AI sessions, now in beta and on by default: each session ties a chat to a workspace or fork with a live preview, builds scripts, flows and apps as reviewable drafts, and runs many in parallel. Supporting work landed around it — file attachments in chat, visible web-search sources, in-app git-to-Windmill sync, and schema contracts that warn when a consumer script drifts from a producer's materialized table.
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.
Windmill's July stream is dominated by AI sessions, now in beta and on by default: each session ties a chat to a workspace or fork with a live preview, builds scripts, flows and apps as reviewable drafts, and runs many in parallel. Supporting work landed around it — file attachments in chat, visible web-search sources, in-app git-to-Windmill sync, and schema contracts that warn when a consumer script drifts from a producer's materialized table.
Two moves are running together. The authoring model is shifting from writing scripts to reviewing generated ones, with the diff drawer and draft state as the safety mechanism rather than trusting the model outright. Meanwhile the commercial line is being redrawn: BigQuery and Snowflake left the Enterprise tier for community edition, including self-hosted. Windmill is trading connector exclusivity for adoption while the AI layer becomes the thing worth paying for.
Expect AI sessions to leave beta with governance around it — who can deploy a generated draft, and what an autonomous session may touch — since the draft-and-diff design already anticipates that review step.
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 Retool or Windmill.
GitHub shut down its model catalog and shipped stacked pull requests on the same day.
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 Retool alternatives → · See all Windmill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Windmill is currently shipping more aggressively (velocity 7.5 vs 6.3), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Windmill is currently shipping more aggressively (velocity 7.5 vs 6.3), 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.
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.
Top Windmill alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Windmill alternatives" section above for the current picks, or visit /alternatives/windmill for the full list with editorial commentary on each.