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 NetBox — 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.
NetBox is spending 4.6 paying down query cost, not adding models.
The 4.6 line opened in May with genuinely new modelling — virtual machine types, cable bundles, a flat rack-group axis, ETag support on the REST API — and every patch release since has been maintenance in the same shape: a handful of enhancements, a block of performance work, a longer block of bug fixes. The performance entries are consistently about query count: N+1 elimination in GraphQL, prefetch hints, serializer caching, chunked bulk updates, a GIN index on cable paths.
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.
The 4.6 line opened in May with genuinely new modelling — virtual machine types, cable bundles, a flat rack-group axis, ETag support on the REST API — and every patch release since has been maintenance in the same shape: a handful of enhancements, a block of performance work, a longer block of bug fixes. The performance entries are consistently about query count: N+1 elimination in GraphQL, prefetch hints, serializer caching, chunked bulk updates, a GIN index on cable paths.
This is a project optimising for large installations rather than new use cases. GraphQL in particular is being hardened release by release — depth limiting, prefetch hints, schema corrections — which reads as API consumers hitting limits at scale. Security fixes arrive quietly inside the same lists, including audit-trail immutability and constant-time token comparison.
Expect the 4.6.x train to continue on its roughly two-week cadence with the same enhancement/performance/fix mix, and the next feature-bearing work to wait for 4.7 rather than appearing in a patch.
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 NetBox.
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.
Resend spent a month making itself something agents and third-party apps can log into.
Prowler turned its assistant from a read-only explainer into something that can change your tenant.
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 NetBox alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Infra & APIs. Dashy is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Dashy is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 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 NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox for the full list with editorial commentary on each.