Windmill
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
A side-by-side editorial comparison of Dashy and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
The self-hosted dashboard finally let you drag things around instead of editing YAML.
Dashy tags a release per merged pull request, so the version number climbs several times a week while most tags carry a single dependabot bump or a translation file. The substance sits in 4.5.0, which added drag-and-drop editing of sections, items and widgets, rebuilt the GitHub stats widget on GitHub's own API with optional token authentication, and expanded number formatting in the custom-api widget. Point releases since have been an OIDC post-logout redirect, item sorting options, and an out-of-memory crash fix.
Resend spent a month making itself something agents and third-party apps can log into.
Resend is shipping weekly, and the last six weeks split cleanly into two tracks. One is dashboard housekeeping for teams sending at volume: template folders, suppression management from both the dashboard and the API, Message-ID on webhooks and email endpoints for threading. The other is access: a hosted MCP server with OAuth built in, a one-click Claude connector, a Codex marketplace plugin bundling the MCP server and Resend's own skills, and OAuth 2.1 with PKCE so outside developers can build authenticated Resend experiences.
Dashy tags a release per merged pull request, so the version number climbs several times a week while most tags carry a single dependabot bump or a translation file. The substance sits in 4.5.0, which added drag-and-drop editing of sections, items and widgets, rebuilt the GitHub stats widget on GitHub's own API with optional token authentication, and expanded number formatting in the custom-api widget. Point releases since have been an OIDC post-logout redirect, item sorting options, and an out-of-memory crash fix.
The direction is away from configuration-as-a-file toward direct manipulation, which is the friction that has always separated Dashy from simpler homepage dashboards. The supporting work lines up with it: sorting controls, better handling of long titles, richer widget formatting. The auth-adjacent changes — OIDC logout redirect, logout destination — suggest people are running Dashy behind an identity provider for more than one user.
With drag-and-drop editing shipped, the follow-on is most likely persistence and permissions questions around who can edit a shared dashboard, though these notes do not state that. Expect the per-PR release cadence to continue producing mostly dependency tags.
Resend is shipping weekly, and the last six weeks split cleanly into two tracks. One is dashboard housekeeping for teams sending at volume: template folders, suppression management from both the dashboard and the API, Message-ID on webhooks and email endpoints for threading. The other is access: a hosted MCP server with OAuth built in, a one-click Claude connector, a Codex marketplace plugin bundling the MCP server and Resend's own skills, and OAuth 2.1 with PKCE so outside developers can build authenticated Resend experiences.
The second track is the one that changes what Resend is. Shipping an OAuth provider alongside agent-facing distribution turns an API you hold a key for into a platform other software signs into on a user's behalf — the MCP server, the Claude connector and the Codex plugin are all downstream of that auth work. The GitHub secret scanner, which detects and auto-revokes exposed keys, reads as the other half of the same shift: if keys are going to be handled by agents and third-party apps, leaked-key cleanup has to be automatic.
Expect the agent surfaces to deepen rather than multiply — scoped OAuth permissions and per-app access controls are the natural follow-on once third parties are authenticating into accounts. More marketplace listings are cheap by comparison and likely to continue alongside.
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 Dashy or Resend.
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
Nine releases in four days, all of them small — Casdoor is grinding on tenant-level governance.
Prowler turned its assistant from a read-only explainer into something that can change your tenant.
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.
See all Dashy alternatives → · See all Resend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy and Resend are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Dashy and Resend are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.
Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.