← Back to home
Comparison · DevOps

Libreswan vs Scalingo

A side-by-side editorial comparison of Libreswan and Scalingo — release velocity, themes, recent moves, and the top alternatives to consider.

Libreswan vs Scalingo: at a glance

FeatureLibreswanScalingo
SectorDevOpsDevOps
Velocity score6.35.0
Sparks · 30d00
Top themesipsec, post-quantum crypto, ikev2, rfc 9370platform-maintenance, database-operations, sdk-expansion, valkey
Last editorial update1mo ago8h ago
WebsiteVisit →Visit →

What is Libreswan?

Libreswan puts post-quantum key exchange into IKEv2 — ML-KEM 768 ships in v5.4.

Libreswan spent the last two releases on security patches, including a CVE found when the project ran an AI audit over its own codebase. v5.4 breaks that pattern: it implements RFC 9370's multiple-key-exchange machinery end to end — IKE_INTERMEDIATE, IKE_ADDITIONAL_KE and IKE_FOLLOWUP_KE — and uses it to carry ML_KEM_768 in IKE_SA_INIT and IKE_INTERMEDIATE. The rest of the release is a wide maintenance sweep across kernel integration on the BSDs, config parsing and logging.

Read the full Libreswan trajectory →

What is Scalingo?

Scalingo ships routine runtime maintenance at high cadence while expanding database observability through its SDK.

Scalingo is in a steady maintenance pattern: multiple PHP minor versions, Redis security patches, and nginx stable bumps ship on a near-daily schedule. The go-scalingo SDK is receiving functional additions each release — TokenDelete, application firewall rules, default credential fetching for database endpoints, and the new Missed Database Maintenance event. The Valkey console in CLI 1.49.0 signals early positioning for the Redis → Valkey transition.

Read the full Scalingo trajectory →

Libreswan vs Scalingo: editorial side-by-side

L
Libreswan
DEVOPS
6.3

Libreswan puts post-quantum key exchange into IKEv2 — ML-KEM 768 ships in v5.4.

◆ Current state

Libreswan spent the last two releases on security patches, including a CVE found when the project ran an AI audit over its own codebase. v5.4 breaks that pattern: it implements RFC 9370's multiple-key-exchange machinery end to end — IKE_INTERMEDIATE, IKE_ADDITIONAL_KE and IKE_FOLLOWUP_KE — and uses it to carry ML_KEM_768 in IKE_SA_INIT and IKE_INTERMEDIATE. The rest of the release is a wide maintenance sweep across kernel integration on the BSDs, config parsing and logging.

◆ Where it's heading

The post-quantum work is the spine of this release and it is not experimental framing — it is standards-track RFC 9370 plus a hard dependency on NSS 3.118.1, meaning distributions have to move their crypto library before users can turn it on. Around it, the project keeps grinding on operator experience: better proposal parsing, more specific error messages, traffic selectors and DIGSIG algorithms in logs, and rate-limited logging. Experimental flags for subnet leasing and updown-config suggest the next capability additions are already staged.

◆ Prediction

Expect ML-KEM to move from supported to recommended in default proposals once NSS 3.118.1 is widely packaged, and the experimental leftaddresspool subnet leasing and per-connection debug options to stabilize in a following release.

S
Scalingo
DEVOPS
5.0

Scalingo ships routine runtime maintenance at high cadence while expanding database observability through its SDK.

◆ Current state

Scalingo is in a steady maintenance pattern: multiple PHP minor versions, Redis security patches, and nginx stable bumps ship on a near-daily schedule. The go-scalingo SDK is receiving functional additions each release — TokenDelete, application firewall rules, default credential fetching for database endpoints, and the new Missed Database Maintenance event. The Valkey console in CLI 1.49.0 signals early positioning for the Redis → Valkey transition.

◆ Where it's heading

The SDK additions point toward a more complete programmatic database management surface — maintenance event tracking, credential management, and network security at the platform layer. If the application firewall rules from go-scalingo v11.5.0 surface in the Dashboard UI, it marks a real expansion into network security controls. The Missed Maintenance event enables monitoring integrations for production teams who care about database SLA windows. Scalingo's trajectory is incremental platform hardening aimed at teams with stricter compliance and operational requirements.

◆ Prediction

Firewall rules management will appear in the Scalingo Dashboard UI within the next few releases, and the Valkey support track will expand into a first-class Valkey addon as Redis license pressure accelerates migration.

Alternatives to Libreswan 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 Libreswan or Scalingo.

See all Libreswan alternatives → · See all Scalingo alternatives →

Recent activity from Libreswan and Scalingo

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 10h agoScalingobuildpacks - PHP - PHP 8.2.34, 8.3.35, 8.4.26 and 8.5.11 are now available
  2. 1d agoScalingogo-scalingo SDK adds TokenDelete method
  3. 2d agoScalingogo-scalingo SDK: default credentials for database endpoint listing
  4. 3d agoScalingodatabases - Redis - New versions: 6.2.24-1 and 7.2.16-1
  5. 7d agoScalingoapi - New Database Maintenance Missed Event
  6. 8d agoScalingobuildpacks - Keycloak: Keycloak 26.7.4 is now available
  7. 1mo agoLibreswan5.4: ML-KEM 768 and RFC 9370 multiple key exchanges for IKEv2 ⚡
  8. 2mo agoLibreswan5.3.2: FIPS-mode daemon crash from malformed X.509 certificates
  9. 3mo agoLibreswan5.3.1: three CVEs and a newer-GCC compile fix
  10. 2y agoLibreswanIKEv1 cryptosuite defaults tightened; systemd libxz dependency dropped
  11. 2y agoLibreswanCompile error fix carried over from 4.13

Frequently asked questions

What is the difference between Libreswan and Scalingo?

They serve adjacent needs but don't currently overlap on shipped themes. Libreswan is currently shipping more aggressively (velocity 6.3 vs 5.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.

Is Libreswan better than Scalingo?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Libreswan is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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.

What are the best alternatives to Libreswan?

Top Libreswan alternatives in DevOps are ranked by recent ship velocity. Browse the "Libreswan alternatives" section above for the current picks, or visit /alternatives/libreswan 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.