Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
A side-by-side editorial comparison of Sonarr and Microcks — release velocity, themes, recent moves, and the top alternatives to consider.
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
Ten releases in this window, several cut hours apart, and almost every one carries a single change. The dominant thread is download-client authentication: basic auth for qBittorrent, reusing authentication cookies across qBittorrent calls, and backporting both to the v4 line — the same two fixes appearing repeatedly as they propagate across branches. The rest is a Jellyfin and Emby connection test with a new Jellyfin auth header, a language-handling correction, and dependency bumps for MailKit and FFprobe.
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
Three release candidates are visible — 1.14.0-rc1 and rc2 in March 2026, then 1.15.0-rc1 in June. The 1.14 line added Sync-to-Async triggers with trigger info propagated to the async minion, pushed the Helm chart as an OCI artifact, fixed API health checks under bad connection configuration, and extended OpenAI-based example generation to the GPT-5 family. 1.15.0-rc1 is largely platform upkeep: Angular upgraded to v21, netty explicitly embedded in the native image, GraphQL extensions, paginated topic ARN lookup, and a corrected OpenAPI overlay export shape.
Ten releases in this window, several cut hours apart, and almost every one carries a single change. The dominant thread is download-client authentication: basic auth for qBittorrent, reusing authentication cookies across qBittorrent calls, and backporting both to the v4 line — the same two fixes appearing repeatedly as they propagate across branches. The rest is a Jellyfin and Emby connection test with a new Jellyfin auth header, a language-handling correction, and dependency bumps for MailKit and FFprobe.
This is mature-product maintenance, and the failure surface is entirely at the integration boundary — the download clients and media servers Sonarr talks to change their auth behaviour, and Sonarr chases them. Releases are cut per-fix rather than batched, which produces a high tag count from a low volume of actual change. Nothing in this window touches Sonarr's own capability surface.
Expect the same pattern to continue: small single-change releases tracking download-client and media-server API shifts, with no visible feature work on the 4.0 line.
Three release candidates are visible — 1.14.0-rc1 and rc2 in March 2026, then 1.15.0-rc1 in June. The 1.14 line added Sync-to-Async triggers with trigger info propagated to the async minion, pushed the Helm chart as an OCI artifact, fixed API health checks under bad connection configuration, and extended OpenAI-based example generation to the GPT-5 family. 1.15.0-rc1 is largely platform upkeep: Angular upgraded to v21, netty explicitly embedded in the native image, GraphQL extensions, paginated topic ARN lookup, and a corrected OpenAPI overlay export shape.
Two threads run in parallel. The deployment story keeps getting tightened for Kubernetes — OCI-packaged Helm charts, native-image reflection registration, an Uber distribution — which is where a mock server has to live to be useful in CI. The more interesting thread is example generation: authoring realistic mock data is the actual work of using a mocking tool, and Microcks is putting a model behind it rather than asking users to write it. That work is still surfacing as commit lines rather than headline features.
The 1.15 line should reach a final release given the pre-release pattern, and the LLM example generation is the thread most likely to move from plumbing to a named capability if it keeps expanding.
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 Sonarr or Microcks.
The self-hosted dashboard finally let you drag things around instead of editing YAML.
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
JuiceFS is spending its v1.4 cycle on metadata-engine efficiency, one transaction at a time.
See all Sonarr alternatives → · See all Microcks alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sonarr is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Sonarr is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Sonarr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Sonarr alternatives" section above for the current picks, or visit /alternatives/sonarr for the full list with editorial commentary on each.
Top Microcks alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Microcks alternatives" section above for the current picks, or visit /alternatives/microcks for the full list with editorial commentary on each.