GitHub
GitHub killed its model-hosting product and shipped stacked PRs in the same week.
A side-by-side editorial comparison of Windmill and authentik — release velocity, themes, recent moves, and the top alternatives to consider.
Windmill let its AI build deployable drafts, then handed two paid runtimes to the free tier.
Windmill is a developer platform for scripts, flows and internal apps, shipping near-daily and with most of this window aimed at two things: an AI chat that has grown into a full authoring session, and the git and workspace plumbing that gets what it produces into production. AI sessions went to beta enabled by default in July, and BigQuery and Snowflake moved out from behind the Enterprise license in the same week.
Two supported branches, every release a bot-driven cherry-pick — authentik is in pure maintenance here
All six releases in this window are patches across two maintained branches, 2026.5.x and 2026.2.x, and nearly every commit in them is a cherry-pick bot backporting a fix from main. The content is fixes and documentation rather than capability: reverting locale-driven flow re-requests in the flow executor, handling an exception in connector controller sync setup, fixing outgoing sync discovery running once per page, migrating OpenID conformance tests to upstream images, and additional SCIM provider documentation. The one change with an operational edge is 2026.5.6 dropping curl and runit from the container image.
Windmill is a developer platform for scripts, flows and internal apps, shipping near-daily and with most of this window aimed at two things: an AI chat that has grown into a full authoring session, and the git and workspace plumbing that gets what it produces into production. AI sessions went to beta enabled by default in July, and BigQuery and Snowflake moved out from behind the Enterprise license in the same week.
The AI thread and the deployment thread are converging on one workflow. Sessions produce scripts, flows and apps as drafts reviewed in a unified diff drawer; git sync now deploys from a tracked branch in-app and posts a diff check on pull requests; Compare & Deploy targets any workspace rather than only the parent. The result is a path where AI-generated work is reviewed as a diff and promoted like code — which is a bet that the constraint on AI authoring is trust in the review step, not generation quality.
Expect AI sessions to move from beta toward default, and further work on the review-and-promote path they feed, since every release in this window touched one or the other. What happens to the remaining Enterprise-only runtimes, Oracle DB and MS SQL, is not indicated.
All six releases in this window are patches across two maintained branches, 2026.5.x and 2026.2.x, and nearly every commit in them is a cherry-pick bot backporting a fix from main. The content is fixes and documentation rather than capability: reverting locale-driven flow re-requests in the flow executor, handling an exception in connector controller sync setup, fixing outgoing sync discovery running once per page, migrating OpenID conformance tests to upstream images, and additional SCIM provider documentation. The one change with an operational edge is 2026.5.6 dropping curl and runit from the container image.
The release pattern says more than the contents: two branches maintained in parallel with the same fixes landing on each — 2026.2.6 and 2026.5.5 shipped the same day carrying the same conformance-test migration — which is the shape of a project supporting long-lived deployments rather than pushing users forward. Feature work is happening on main and is not visible in this feed; what reaches these branches is the fix subset. Removing curl and runit from the image continues a slow trimming of what ships inside the container.
The visible pattern supports only more of the same: alternating 2026.5.x and 2026.2.x patches assembled from cherry-picks, until a new feature branch is cut. Nothing in these entries indicates what that branch will contain.
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 Windmill or authentik.
GitHub killed its model-hosting product and shipped stacked PRs in the same week.
Ably is building an agent transport layer, shipping a new AI SDK version roughly every ten days.
One commit per release, and most of them are closing security holes in the Cloud Code and query paths.
Three branches patched in lockstep for an unauthenticated takeover — then patched again for the fix's regression.
Two maintained branches, a paired-release rhythm, and a window with no new features in it.
Three branches tagged on one day, with the actual release notes published somewhere else
See all Windmill alternatives → · See all authentik 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 8.8 vs 5.0), with 2 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 8.8 vs 5.0), with 2 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 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.
Top authentik alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "authentik alternatives" section above for the current picks, or visit /alternatives/authentik for the full list with editorial commentary on each.