Sonarr
Sonarr's 5.0 builds move from UI rework to safer restores and keyboard-friendly selects.
A side-by-side editorial comparison of Doppler and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
Doppler shipped an on-prem build — the secrets manager that only ran as SaaS now runs in your datacenter.
Monthly digests, each one a list, and the captured bodies cut off partway so only the opening items are legible. June leads with Doppler On-prem, alongside role filters on the dashboard, warnings that show downstream impact before deleting inherited or referenced data, and fuzzy matching in secret search. The months before it are steady platform work: Integration Access Scoping via API and Terraform, the ability to redact every historical version of a secret so deleted history is genuinely gone, Azure Service Principal rotated and dynamic secrets, activity-log forwarding to multiple destinations per service type including AWS SQS, and CLI token creation from the MCP server.
Payload v4 enters beta: redesigned admin, TanStack Start support and agent instructions.
Payload 4.0 moved from canaries to beta on October 9, bundling an admin UI redesign, TanStack Start as a second framework alongside Next.js, hierarchies, tags, grid view, upload versioning and a rewritten MCP server. Two betas followed within a week; beta.2 moves the TanStack adapter to stable TanStack Start and renames LLM instructions to agent instructions. The canaries also flipped the Local API to enforce access control by default.
Monthly digests, each one a list, and the captured bodies cut off partway so only the opening items are legible. June leads with Doppler On-prem, alongside role filters on the dashboard, warnings that show downstream impact before deleting inherited or referenced data, and fuzzy matching in secret search. The months before it are steady platform work: Integration Access Scoping via API and Terraform, the ability to redact every historical version of a secret so deleted history is genuinely gone, Azure Service Principal rotated and dynamic secrets, activity-log forwarding to multiple destinations per service type including AWS SQS, and CLI token creation from the MCP server.
Two commitments run through this window. The first is that everything must be reachable programmatically — API and Terraform coverage for access scoping, Change Requests endpoints in the v3 API, service account identity management, MCP-driven CLI authentication. The second is control over the secret's whole lifecycle rather than its current value: rotation, dynamic generation, history redaction, and delete-time impact warnings all treat a secret as something with a past and dependents. On-prem is what those two make sellable to the customers who could not use Doppler at all.
Expect the on-prem build to drive the next stretch of work — parity gaps, upgrade paths, and air-gapped handling of the integrations that currently assume outbound access. The truncated digests make anything finer than that unreadable from the feed.
Payload 4.0 moved from canaries to beta on October 9, bundling an admin UI redesign, TanStack Start as a second framework alongside Next.js, hierarchies, tags, grid view, upload versioning and a rewritten MCP server. Two betas followed within a week; beta.2 moves the TanStack adapter to stable TanStack Start and renames LLM instructions to agent instructions. The canaries also flipped the Local API to enforce access control by default.
Payload is loosening its Next.js dependency and building agent features into the CMS itself: editors can manage instructions that flow into the CLI and MCP schemas, and upgrades come with an agent-assisted codemod. The betas are now mostly fixes and documentation, which points toward a stable 4.0.
Expect weekly betas focused on migration fixes and docs, with more framework-adapter work for TanStack Start. The entries don't give a 4.0 stable date.
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 Doppler or Payload CMS.
Sonarr's 5.0 builds move from UI rework to safer restores and keyboard-friendly selects.
Cursor puts its cloud agent environments behind an API and lets agents ship interactive canvases.
Railway is adding guardrails for teams moving off the dashboard and into code and the CLI.
Jackett ships daily to keep hundreds of torrent indexers working as sites move and close.
CircleCI now sizes parallelism to the tests Smarter Testing actually selects.
GitHub makes open source license compliance a ruleset-enforced GA for Enterprise Cloud.
See all Doppler alternatives → · See all Payload CMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 0.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. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 0.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 Doppler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Doppler alternatives" section above for the current picks, or visit /alternatives/doppler for the full list with editorial commentary on each.
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.