OSRM
OSRM 26.9.0 routes through pedestrian areas and plazas for the first time.
A side-by-side editorial comparison of Argo CD and Scalingo — release velocity, themes, recent moves, and the top alternatives to consider.
Argo CD's 3.5 train is all hydrator, supply-chain verification and OIDC session repair.
Argo CD is mid-release-candidate on 3.5, with rc1 carrying the feature payload and rc2/rc3 narrowing to fixes. The 3.4 line went stable in May and picked up a 3.4.3 patch. Feature work concentrates in three places: the source hydrator and promoter, ApplicationSet scale and concurrency, and the long tail of resource health checks contributed by users.
Scalingo phases out swap memory for application containers, shifting OOM behavior for new and restarted apps starting September 2026.
Scalingo is implementing a breaking platform change: new applications created after September 1, 2026 no longer receive swap memory, and existing applications will have their swap limit reduced to 25% of container memory on their next restart. The rest of the changelog is routine buildpack version updates across PHP, Go, Java, and Python.
Argo CD is mid-release-candidate on 3.5, with rc1 carrying the feature payload and rc2/rc3 narrowing to fixes. The 3.4 line went stable in May and picked up a 3.4.3 patch. Feature work concentrates in three places: the source hydrator and promoter, ApplicationSet scale and concurrency, and the long tail of resource health checks contributed by users.
The hydrator is becoming the centre of gravity — configurable hydration queue concurrency, ConfigMap-managed README templates, a separate destination repo for syncSource, and opt-in source integrity verification for dry sources in alpha. Paired with cosign-signed images and SLSA Level 3 provenance on every release, Argo CD is moving toward a GitOps pipeline where what gets hydrated is verified, not just applied. The rc2/rc3 fix lists are dominated by sync-correctness and auth-session bugs, which is where a 3.5 GA will stand or fall.
3.5.0 GA is the next step once the cherry-pick stream dries up; on current evidence source integrity verification stays alpha and opt-in through that release.
Scalingo is implementing a breaking platform change: new applications created after September 1, 2026 no longer receive swap memory, and existing applications will have their swap limit reduced to 25% of container memory on their next restart. The rest of the changelog is routine buildpack version updates across PHP, Go, Java, and Python.
Removing swap reflects a broader PaaS trend toward tighter memory boundaries, forcing applications to be correctly sized rather than relying on disk-backed swap as an overflow buffer. For memory-inefficient applications, this will surface OOM restarts that were previously masked. Existing applications have until end of 2026 before the full cutover.
Scalingo will likely follow the swap removal with tighter memory monitoring tooling or sizing recommendations to help customers identify applications relying on swap before the end-of-2026 cutover for existing apps.
Other DevOps 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 Argo CD or Scalingo.
OSRM 26.9.0 routes through pedestrian areas and plazas for the first time.
FusionAuth adds RFC 8707 resource-scoped tokens while most recent changelogs surface only upgrade boilerplate.
Sanity centralizes its AI context layer in a dedicated dashboard app while running the most active MCP release sprint yet.
Dapr is hardening workflow reliability across three concurrent release branches, with actor hot-reload as the headliner.
Slurm coordinated a 7-CVE security drop across three active branches, including a privilege escalation and SQL injection.
NSD patched 8 CVEs across two dedicated security releases and added EDNS0 padding and PROXYv2 access controls.
See all Argo CD alternatives → · See all Scalingo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Argo CD and Scalingo are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Argo CD and Scalingo are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Argo CD alternatives in DevOps are ranked by recent ship velocity. Browse the "Argo CD alternatives" section above for the current picks, or visit /alternatives/argo-cd for the full list with editorial commentary on each.
Top Scalingo alternatives in DevOps are ranked by recent ship velocity. Browse the "Scalingo alternatives" section above for the current picks, or visit /alternatives/scalingo for the full list with editorial commentary on each.