Windmill
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
A side-by-side editorial comparison of Casdoor and Prowler — release velocity, themes, recent moves, and the top alternatives to consider.
Nine releases in four days, all of them small — Casdoor is grinding on tenant-level governance.
Casdoor is running an unusually tight release train: nine tagged versions between August 1 and August 4, each carrying one or two commits. The content clusters around two areas. Retention and expiry are becoming per-organization settings — configurable record retention days, configurable token retention days, and automatic permission revocation after a set expiry. Separately, OAuth conformance work continues, with the RFC 8707 resource parameter now preserved through both the consent flow and the fast auto-signin path, plus a backchannel logout URL field on the application edit page.
Prowler turned its assistant from a read-only explainer into something that can change your tenant.
Two months of releases trace one arc: Lighthouse AI arrived in 5.33 as a read-only agent over Prowler's own tools, gained write actions in 5.35 (connect providers, trigger and schedule scans, manage mutelists), and in 5.37 became page-aware with access to every tool family the Prowler MCP server advertises. Around it, MCP itself gained integrations, users and roles tool families on both Cloud and self-hosted servers. Between feature releases the patch cadence is heavy CVE reduction in container images.
Casdoor is running an unusually tight release train: nine tagged versions between August 1 and August 4, each carrying one or two commits. The content clusters around two areas. Retention and expiry are becoming per-organization settings — configurable record retention days, configurable token retention days, and automatic permission revocation after a set expiry. Separately, OAuth conformance work continues, with the RFC 8707 resource parameter now preserved through both the consent flow and the fast auto-signin path, plus a backchannel logout URL field on the application edit page.
The per-organization retention and expiry settings point at multi-tenant deployments where each tenant carries its own compliance obligations — a single global retention policy stops working once one organization's auditor wants 90 days and another's wants 400. The RFC 8707 work is narrower but pointed: resource indicators bind a token to the API it was issued for, which matters when one identity provider fronts many services. A batch UpdatePermissions API added to cut Casbin enforcer rebuilds suggests some deployments are large enough that permission writes had become a bottleneck.
The retention-and-expiry pattern is not finished — record and token retention are now per-organization, and other lifecycle settings are the obvious next candidates. Expect the release cadence to stay at this granularity, since these tags carry single commits rather than batched releases.
Two months of releases trace one arc: Lighthouse AI arrived in 5.33 as a read-only agent over Prowler's own tools, gained write actions in 5.35 (connect providers, trigger and schedule scans, manage mutelists), and in 5.37 became page-aware with access to every tool family the Prowler MCP server advertises. Around it, MCP itself gained integrations, users and roles tool families on both Cloud and self-hosted servers. Between feature releases the patch cadence is heavy CVE reduction in container images.
The product is being repositioned from scanner to operator, with RBAC as the safety story — Lighthouse can only do what the asking user could do. The naming reshuffle in 5.34 made the split explicit: the open-source CLI and Local Server on one side, Cloud, Private Cloud and Lighthouse behind a subscription on the other. Every agentic capability so far has landed on the paid side.
Expect the Lighthouse tool surface to keep tracking whatever the MCP server exposes, with remediation actions — not just scan and triage management — as the next boundary to be tested.
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 Casdoor or Prowler.
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
Resend spent a month making itself something agents and third-party apps can log into.
NetBox is spending 4.6 paying down query cost, not adding models.
Depot is no longer a build accelerator — it is assembling the whole CI stack underneath itself.
Buildkite is rebuilding its MCP server around what an agent actually does with a failed build.
The self-hosted dashboard finally let you drag things around instead of editing YAML.
See all Casdoor alternatives → · See all Prowler alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — rbac — within Infra & APIs. Prowler 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. Prowler 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 Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.
Top Prowler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Prowler alternatives" section above for the current picks, or visit /alternatives/prowler for the full list with editorial commentary on each.