FusionAuth
FusionAuth adds RFC 8707 resource-scoped tokens while most recent changelogs surface only upgrade boilerplate.
Comparison · DevOps
NSD vs Scalingo
A side-by-side editorial comparison of NSD and Scalingo — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:infrastructure
NSD vs Scalingo: at a glance
What is NSD?
NSD patched 8 CVEs across two dedicated security releases and added EDNS0 padding and PROXYv2 access controls.
NSD released three significant versions in quick succession: 4.15.1 fixed four CVEs including a TCP-window-throttle DoS, a UDP cookie-option DoS, an IP ACL bypass for some address ranges, and a PROXYv2 port ACL bypass. 4.15.2 followed with feature additions — HHIT/BRID RR type support, new SVCB service parameter keys (docpath, pvd, oots), EDNS0 padding over TLS per RFC 7830/8467, and configurable PROXYv2 access control — alongside another substantial round of hardening fixes, many reported by Palo Alto Networks. The 4.15.0 release introduced a breaking change to Prometheus metrics, moving zone names from metric labels to label values.
What is Scalingo?
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.
NSD vs Scalingo: editorial side-by-side
NSD
5.0DEVOPS
NSD patched 8 CVEs across two dedicated security releases and added EDNS0 padding and PROXYv2 access controls.
◆ Current state
NSD released three significant versions in quick succession: 4.15.1 fixed four CVEs including a TCP-window-throttle DoS, a UDP cookie-option DoS, an IP ACL bypass for some address ranges, and a PROXYv2 port ACL bypass. 4.15.2 followed with feature additions — HHIT/BRID RR type support, new SVCB service parameter keys (docpath, pvd, oots), EDNS0 padding over TLS per RFC 7830/8467, and configurable PROXYv2 access control — alongside another substantial round of hardening fixes, many reported by Palo Alto Networks. The 4.15.0 release introduced a breaking change to Prometheus metrics, moving zone names from metric labels to label values.
◆ Where it's heading
NSD is in a security-intensive maintenance phase with a consistent external contributor: Qifan Zhang at Palo Alto Networks has reported the majority of bugs fixed in the 4.15.x cycle, including heap overflows, assertion failures on malformed records, and multiple DoS vectors. This external security research pressure is accelerating the quality of NSD's defensive posture. Protocol completeness work (new RR types, SVCB parameters) continues alongside the security fixes.
◆ Prediction
The PROXYv2 improvements suggest NSD deployments behind TLS-terminating load balancers are a growing use case — expect additional configuration controls for encrypted-DNS setups. The experimental multi-catalog-consumer-zones flag may graduate to stable in a future release.
Scalingo
5.0DEVOPS
Scalingo phases out swap memory for application containers, shifting OOM behavior for new and restarted apps starting September 2026.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to NSD and Scalingo
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 NSD or Scalingo.
Sanity
Sanity centralizes its AI context layer in a dedicated dashboard app while running the most active MCP release sprint yet.
Dapr
Dapr is hardening workflow reliability across three concurrent release branches, with actor hot-reload as the headliner.
Slurm
Slurm coordinated a 7-CVE security drop across three active branches, including a privilege escalation and SQL injection.
Meilisearch
Meilisearch is trimming ~100ms sharding latency in prototype while shipping task-queue controls in stable.
Aiven
Aiven completes its three-cloud BYOC story with self-service Azure, while adding AI agent governance and API secrets redaction.
See all NSD alternatives → · See all Scalingo alternatives →
Recent activity from NSD and Scalingo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14h agoNSDNSD 4.15.2 released
- 1d agoScalingoNew apps lose swap; existing apps reduced to 25% on next restart
- 3d agoScalingobuildpacks - PHP - PHP 8.4.25 and 8.5.10 are now available
- 7d agoScalingobuildpacks - PHP - Composer 2.10.3 is now available
- 8d agoNSDNSD 4.15.2 release candidate
- 8d agoNSDNSD 4.15.1 security release: four CVEs fixed
- 8d agoScalingoStack image updates: scalingo-26 v4, scalingo-24 v9, scalingo-22 v19
- 9d agoScalingoStack image updates: scalingo-26 v3, scalingo-24 v8, scalingo-22 v18
- 14d agoScalingobuildpacks - Java - JDK 1.8.0_504, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1 and 26.0.2.1 are now available
- 1mo agoNSDNSD 4.15.0 released
- 2mo agoNSDNSD 4.15.0 release candidate
- 2mo agoNSDNSD 4.14.3: four CVEs including heap overflow and TLS authentication bypass
Frequently asked questions
What is the difference between NSD and Scalingo?
Both compete on the same themes — infrastructure — within DevOps. NSD 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.
Is NSD better than Scalingo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NSD 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.
What are the best alternatives to NSD?
Top NSD alternatives in DevOps are ranked by recent ship velocity. Browse the "NSD alternatives" section above for the current picks, or visit /alternatives/nsd for the full list with editorial commentary on each.
What are the best alternatives to Scalingo?
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.