Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of Nebula and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
Redocly shipped three Reunite releases and a config release on Oct 28. The feedback and discovery duties in reunite.agent can now each run on their own UTC cron trigger, follow their own rules and read only listed source repositories. SCIM provisioning now accepts identity-provider groups of any size, where pushes over 1,000 members used to fail. @redocly/config 0.69.0 also adds per-rule impact settings for the experimental diff command.
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.
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.
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.
Redocly shipped three Reunite releases and a config release on Oct 28. The feedback and discovery duties in reunite.agent can now each run on their own UTC cron trigger, follow their own rules and read only listed source repositories. SCIM provisioning now accepts identity-provider groups of any size, where pushes over 1,000 members used to fail. @redocly/config 0.69.0 also adds per-rule impact settings for the experimental diff command.
Two threads run together: an agent inside Reunite that does recurring docs work (feedback and discovery) and is gaining scheduling and scoping controls, and enterprise plumbing such as SCIM scale, Git token rotation and permission fixes. Last week's configurable docs MCP server points the same way, with Redocly adding AI surfaces and making them configurable in redocly.yaml.
Expect more reunite.agent duty types or options in @redocly/config, and the experimental diff command moving toward a documented API-change check.
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 Redocly.
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io's agent now runs your team's own tools, with a human approval before any change.
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
See all Nebula alternatives → · See all Redocly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Redocly 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Redocly 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.
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.
Top Redocly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Redocly alternatives" section above for the current picks, or visit /alternatives/redocly for the full list with editorial commentary on each.