← Back to home
Comparison · Infra & APIs

Nebula vs Skipper

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

Nebula vs Skipper: at a glance

FeatureNebulaSkipper
SectorInfra & APIsInfra & APIs
Velocity score2.56.3
Sparks · 30d00
Top themesmesh-vpn, overlay-network, certificates, ipv6proxy, ingress, open-source, go
Last editorial update1mo ago2h ago
WebsiteVisit →Visit →

What is Nebula?

Nebula closes a firewall bypass that let unparsed IPv6 protocols match TCP rules

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. v1.10.0 was the pivot — IPv6 and multiple addresses in the overlay, plus a v2 ASN.1 certificate format with a unified interface for external implementations — and everything since has been consequence management. v1.11.0 shifted to the operational surface with structured slog logging, corrected firewall reject-versus-drop semantics, and Windows WFP filters by default. v1.11.1 returns to the packet classifier: IPv6 packets whose next header Nebula does not parse were being misread as TCP or UDP and matched against TCP/UDP firewall rules, and are now classified as their true protocol with no ports.

Read the full Nebula trajectory →

What is Skipper?

Skipper fixes two silent data-loss bugs — body truncation on large requests and multi-value header drops.

Skipper is in a steady maintenance phase: the two meaningful releases this period are correctness fixes for a silent body-truncation bug in the io matcher (large request bodies dropped silently beyond the max buffer size) and a cookie-deleting bug where modRequestHeader/modResponseHeader only applied regex rewrites to the first value of a multi-valued header. Both are proxy correctness issues where the visible behavior was incorrect responses, not errors.

Read the full Skipper trajectory →

Nebula vs Skipper: editorial side-by-side

N
Nebula
INFRA · APIS
2.5

Nebula closes a firewall bypass that let unparsed IPv6 protocols match TCP rules

◆ Current state

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. v1.10.0 was the pivot — IPv6 and multiple addresses in the overlay, plus a v2 ASN.1 certificate format with a unified interface for external implementations — and everything since has been consequence management. v1.11.0 shifted to the operational surface with structured slog logging, corrected firewall reject-versus-drop semantics, and Windows WFP filters by default. v1.11.1 returns to the packet classifier: IPv6 packets whose next header Nebula does not parse were being misread as TCP or UDP and matched against TCP/UDP firewall rules, and are now classified as their true protocol with no ports.

◆ Where it's heading

The security findings since v1.10.0 map onto the same seam — the IPv6 support that release added widened what the classifier and the certificate validator have to handle, and each subsequent release has closed another gap in that widened surface. v1.11.1 is notable for making the fix a deliberate operational break: carrying SCTP, GRE or IP-in-IP over the overlay may have been working only through the bypass, so operators must add a proto: any rule before upgrading. That the project chose correct classification over compatibility, and said so plainly in the notes, is consistent with how the firewall direction fix was handled one release earlier.

◆ Prediction

The stated plan to assert low-s signature form when validating certificates remains the concrete next step visible in these entries; expect it as a breaking validation change. The classifier work suggests remaining IPv6 extension-header handling is the other likely source of findings.

S
Skipper
INFRA · APIS
6.3

Skipper fixes two silent data-loss bugs — body truncation on large requests and multi-value header drops.

◆ Current state

Skipper is in a steady maintenance phase: the two meaningful releases this period are correctness fixes for a silent body-truncation bug in the io matcher (large request bodies dropped silently beyond the max buffer size) and a cookie-deleting bug where modRequestHeader/modResponseHeader only applied regex rewrites to the first value of a multi-valued header. Both are proxy correctness issues where the visible behavior was incorrect responses, not errors.

◆ Where it's heading

The release cadence is high but the surface area of recent changes is narrow: dependency bumps, documentation corrections, and targeted correctness fixes. Skipper is a mature, production-stable L7 proxy — the development pattern reflects that. The v0.28.x branch is moving ahead of the v0.27.x LTS track simultaneously.

◆ Prediction

The entries don't show architectural moves in the near term. The next meaningful Skipper releases will likely continue in this pattern: correctness fixes for edge-case proxy behaviors that bite production users, with occasional dependency security updates.

Alternatives to Nebula and Skipper

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 Nebula or Skipper.

See all Nebula alternatives → · See all Skipper alternatives →

Recent activity from Nebula and Skipper

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

  1. 2h agoSkipperSkipper v0.28.10: fixes silent body truncation on large requests in best-effort matcher
  2. 4d agoSkipperv0.27.108
  3. 4d agoSkipperSkipper v0.27.107: header modifier filters now apply to all values, not just the first
  4. 4d agoSkipperSkipper v0.27.106: fixes eskip float roundtrip for small canary weights
  5. 4d agoSkipperv0.27.105
  6. 4d agoSkipperv0.27.104
  7. 1mo agoNebulaIPv6 firewall bypass: unparsed protocols matched TCP/UDP rules
  8. 2mo agoNebulaBreaking: slog logging, corrected firewall reject/drop direction
  9. 7mo agoNebulaP256 signature malleability allowed blocklist bypass
  10. 8mo agoNebulaFix panic in use_system_route_table introduced by the previous release
  11. 8mo agoNebulaRoute-reload, handshake, and Windows listener fixes after the v1.10 rework
  12. 9mo agoNebulaIPv6 and multiple addresses in the overlay, plus a v2 certificate format ⚡

Frequently asked questions

What is the difference between Nebula and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Nebula better than Skipper?

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

What are the best alternatives to Nebula?

Top Nebula alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nebula alternatives" section above for the current picks, or visit /alternatives/nebula-networking for the full list with editorial commentary on each.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.