Prometheus
Prometheus 3.16 reaches rc.4 with an integral() function and stricter exemplar handling
A side-by-side editorial comparison of Exoscale and Grav — release velocity, themes, recent moves, and the top alternatives to consider.
Exoscale lets customers keep their own encryption keys outside its cloud.
Exoscale, a European cloud provider, opened a private preview of KMS External Key Store on 3 November: customers connect Exoscale KMS to their own HSM or key manager through a proxy they host, and Exoscale never sees the key material. It implements the AWS KMS XKS proxy API, so existing proxies work unchanged. This follows a free VPC in every zone in October, object-storage lifecycle rules, asymmetric KMS keys and cheaper IPv6 load balancing.
Grav's 1.7 line keeps taking small patches after its security backport burst.
Grav's 1.7 branch shipped four patches between 10-31 and 11-04. 1.7.53.7 and 1.7.53.8 backported Grav 2 security fixes and web-server protection rules; 1.7.53.9 fixed :80 redirects behind HTTPS proxies; 1.7.53.10 makes cache purges report which file failed and why.
Exoscale, a European cloud provider, opened a private preview of KMS External Key Store on 3 November: customers connect Exoscale KMS to their own HSM or key manager through a proxy they host, and Exoscale never sees the key material. It implements the AWS KMS XKS proxy API, so existing proxies work unchanged. This follows a free VPC in every zone in October, object-storage lifecycle rules, asymmetric KMS keys and cheaper IPv6 load balancing.
KMS has moved fast: asymmetric keys in early October, external keys four weeks later. Together with VPC and lifecycle rules, Exoscale is closing gaps against the hyperscalers, and XKS points its pitch at sovereignty-bound customers who need to prove the provider cannot decrypt their data.
XKS will likely widen from private preview to general availability, and the next steps are probably more services encrypting with KMS keys; the entries don't say which services or when.
Grav's 1.7 branch shipped four patches between 10-31 and 11-04. 1.7.53.7 and 1.7.53.8 backported Grav 2 security fixes and web-server protection rules; 1.7.53.9 fixed :80 redirects behind HTTPS proxies; 1.7.53.10 makes cache purges report which file failed and why.
Security work lands on Grav 2 first and is then carried back to 1.7, and the pace of that carry-back jumped: one patch on 10-24, three within about four hours. The fixes moved from individual code paths to the web-server rules that sit in front of the application. Among web servers, only Apache sites get those rules on upgrade; IIS, nginx, Caddy and lighttpd sites must copy them by hand, so protection on 1.7 now depends on the host's web server.
Expect more 1.7.53.x patches mirroring 2.x security fixes, plus small follow-up fixes like the proxy redirect in 1.7.53.9. The entries don't show how long 1.7 support continues.
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 Exoscale or Grav.
Prometheus 3.16 reaches rc.4 with an integral() function and stricter exemplar handling
HashiCorp is rebuilding Terraform and Vault around AI agents as governed users
One Node.js Brotli bug and a compromised CA bundle force ten patches across the Elastic Stack.
QuestDB keeps proving its market-data case with reproducible benchmarks between releases.
Z-Wave JS v15.32.0 ships the findings of two full-codebase security reviews.
Sanity moves agent settings onto the MCP endpoint, so every connected agent behaves alike.
See all Exoscale alternatives → · See all Grav alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Exoscale is currently shipping more aggressively (velocity 6.3 vs 5.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. Exoscale is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Exoscale alternatives in DevOps are ranked by recent ship velocity. Browse the "Exoscale alternatives" section above for the current picks, or visit /alternatives/exoscale for the full list with editorial commentary on each.
Top Grav alternatives in DevOps are ranked by recent ship velocity. Browse the "Grav alternatives" section above for the current picks, or visit /alternatives/grav for the full list with editorial commentary on each.