Kinsta
Kinsta is moving MyKinsta's controls into its API, one surface per month
A side-by-side editorial comparison of Apache CloudStack and Fission — release velocity, themes, recent moves, and the top alternatives to consider.
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Apache CloudStack maintains 4.20 and 4.22 as parallel LTS lines and tags them together — 4.20.3.1 and 4.22.1.1 were cut 49 minutes apart, both with bodies that say only which branch was tagged. The release entries themselves carry no content: the standard body is a set of links to release notes, install, upgrade, admin, and API docs hosted elsewhere. The one exception is the security releases, where the CVE list is written inline.
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.
Apache CloudStack maintains 4.20 and 4.22 as parallel LTS lines and tags them together — 4.20.3.1 and 4.22.1.1 were cut 49 minutes apart, both with bodies that say only which branch was tagged. The release entries themselves carry no content: the standard body is a set of links to release notes, install, upgrade, admin, and API docs hosted elsewhere. The one exception is the security releases, where the CVE list is written inline.
The pattern is stable and unlikely to change: maintenance releases on both LTS lines, a regular release on its own cadence, and security fixes backported across every supported branch at once. Because the feed only becomes descriptive when an advisory forces detail into it, the visible record of this project skews heavily toward vulnerabilities — seven CVEs across backups, templates, and cross-tenant Proxmox access in May alone — and says almost nothing about features.
Expect the paired-branch tagging to continue, with the next informative entry being a security release rather than a feature one. Nothing in this feed supports a claim about where CloudStack's capabilities are heading; that information lives in the release notes it links to.
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.
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 Apache CloudStack or Fission.
Kinsta is moving MyKinsta's controls into its API, one surface per month
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 Apache CloudStack alternatives → · See all Fission alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Apache CloudStack 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. Apache CloudStack 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 Apache CloudStack alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apache CloudStack alternatives" section above for the current picks, or visit /alternatives/cloudstack for the full list with editorial commentary on each.
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.