Apache CloudStack
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
A side-by-side editorial comparison of Fission and Kinsta — release velocity, themes, recent moves, and the top alternatives to consider.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Kinsta is moving MyKinsta's controls into its API, one surface per month
Kinsta's feed is a blog, so releases arrive as truncated posts, but the pattern underneath is consistent: management surfaces that used to require the MyKinsta dashboard keep reappearing in the Kinsta API. Domains, HTTPS, logs, and backups moved in July; visitor analytics — user agents, browsers, request origins — followed in August. Around that sits a year of bot-traffic work and a file manager in the dashboard, and the newest post extends resilience past backups into a named disaster-recovery offering.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
Kinsta's feed is a blog, so releases arrive as truncated posts, but the pattern underneath is consistent: management surfaces that used to require the MyKinsta dashboard keep reappearing in the Kinsta API. Domains, HTTPS, logs, and backups moved in July; visitor analytics — user agents, browsers, request origins — followed in August. Around that sits a year of bot-traffic work and a file manager in the dashboard, and the newest post extends resilience past backups into a named disaster-recovery offering.
The direction is toward WordPress hosting that can be operated entirely programmatically, with MyKinsta as one client among others rather than the control plane. Bot handling and now disaster recovery show the second thread: absorbing operational risk customers would otherwise manage themselves. The blog format hides scope — most posts are teasers — so direction is readable here but the size of any single release is not.
Expect the next API release to pick off another MyKinsta-only surface on the same roughly monthly rhythm, with the file manager the obvious candidate. How far disaster recovery goes beyond scheduled backups is the open question these posts do not answer.
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 Fission or Kinsta.
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
Observability lands on OpenTelemetry semconv in the LTS train
Canvas agents gain memory, and onboarding moves into the editor
Security and governance controls catch up to the Copilot build-out
authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO
See all Fission alternatives → · See all Kinsta alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Kinsta 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. Kinsta 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 Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission for the full list with editorial commentary on each.
Top Kinsta alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kinsta alternatives" section above for the current picks, or visit /alternatives/kinsta for the full list with editorial commentary on each.