Kinsta
Kinsta is moving MyKinsta's controls into its API, one surface per month
A side-by-side editorial comparison of bcmaps and Apache CloudStack — release velocity, themes, recent moves, and the top alternatives to consider.
BC's spatial data package finished its sf migration and went back to adding layers
bcmaps provides British Columbia spatial layers and boundary data to R users, pulling from the BC Data Catalogue. The disruptive work is behind it: version 2.0.0 removed sp and raster support outright, leaving sf as the only returned class, in response to the retirement of rgdal and rgeos. Since then releases have been additive and small - cded_terra() replacing the deprecated raster variant, utm_convert() for reconciling coordinates across UTM zones, and in 2.3.0 a census dissemination block layer plus a dependency bump that removes an indirect reliance on the soon-to-be-archived leaflet.extras.
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.
bcmaps provides British Columbia spatial layers and boundary data to R users, pulling from the BC Data Catalogue. The disruptive work is behind it: version 2.0.0 removed sp and raster support outright, leaving sf as the only returned class, in response to the retirement of rgdal and rgeos. Since then releases have been additive and small - cded_terra() replacing the deprecated raster variant, utm_convert() for reconciling coordinates across UTM zones, and in 2.3.0 a census dissemination block layer plus a dependency bump that removes an indirect reliance on the soon-to-be-archived leaflet.extras.
The package has spent most of its recent history reducing what it depends on rather than growing. Layers moved from a companion data package to direct Data Catalogue downloads in 1.1.0, ending manual update cycles; the sp and raster removal followed a full release of deprecation warnings; the terra transition took the same staged path. The recent dependency bump for leaflet.extras is the same instinct applied early. Feature work now arrives one function or one layer at a time, at roughly one release a year.
Expect further individual layer additions on request, and a completion of the terra transition through removal of the deprecated cded_raster(), given the package's pattern of announcing removals a release ahead.
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.
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 bcmaps or Apache CloudStack.
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 bcmaps alternatives → · See all Apache CloudStack 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 bcmaps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bcmaps alternatives" section above for the current picks, or visit /alternatives/bcmaps for the full list with editorial commentary on each.
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.