GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Payload CMS and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Windmill keeps turning AI clients into the place you build and run its workflows.
Windmill has spent the last six weeks wiring AI into every layer: standalone agents, compaction memory, an AI decision step, Slack-answering agents, and a single /api/mcp endpoint that lets Claude, ChatGPT or Cursor write, test and deploy workspace code. Alongside that it is formalizing who can do what, with default Developer and Operator roles and seat-priced operator build rights. The latest release, Tailwind v4 compilation for full-code apps, is frontend plumbing that makes those apps easier to style.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Three betas in a row have reworked file uploads around one stored original plus replayable transforms, and two have tightened sign-in and sessions. The v4 cycle is now finishing those two systems rather than adding new surfaces, which is the usual shape of a beta nearing a release candidate.
Expect more betas that close out the transforms and session work, with a release candidate once the fix lists shrink; the entries do not show a date.
Windmill has spent the last six weeks wiring AI into every layer: standalone agents, compaction memory, an AI decision step, Slack-answering agents, and a single /api/mcp endpoint that lets Claude, ChatGPT or Cursor write, test and deploy workspace code. Alongside that it is formalizing who can do what, with default Developer and Operator roles and seat-priced operator build rights. The latest release, Tailwind v4 compilation for full-code apps, is frontend plumbing that makes those apps easier to style.
The direction is clear: Windmill wants to be the execution backend that AI clients drive, not just a UI people click through. MCP moved from a tool list to a build-and-deploy surface, then to interactive cards inside the chat. The roles and seat changes suggest it is preparing to price the wider set of people who can now build through AI.
Expect more of the deploy and review lifecycle to surface inside MCP clients, and finer-grained role controls over which MCP tools each role gets.
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 Payload CMS or Windmill.
GravityKit folds every GravityView extension into one Pro plugin.
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.
Velociraptor's recent releases are mostly about patching CVEs.
See all Payload CMS 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. Payload CMS and Windmill are shipping at a similar cadence (velocity 5.0 vs 5.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. Payload CMS and Windmill are shipping at a similar cadence (velocity 5.0 vs 5.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 Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload 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.