← Back to home
Comparison · Infra & APIs

FoRecoML vs Nebula

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

FoRecoML vs Nebula: at a glance

FeatureFoRecoMLNebula
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriesmesh-vpn, overlay-network, certificates, ipv6
Last editorial update57m ago8d ago
WebsiteVisit →Visit →

What is FoRecoML?

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

Read the full FoRecoML trajectory →

What is Nebula?

Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.

Read the full Nebula trajectory →

FoRecoML vs Nebula: editorial side-by-side

F
FoRecoML
INFRA · APIS
0.0

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

◆ Current state

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

◆ Where it's heading

This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.

◆ Prediction

With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.

N
Nebula
INFRA · APIS
2.5

Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.

◆ Current state

Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.

◆ Where it's heading

The project has moved from single-IPv4-per-node assumptions toward a genuinely flexible addressing model, and the security fixes since v1.10.0 map directly onto that change — the new certificate features widened what the code has to validate. v1.11.0 shifts attention to the operational surface instead: structured logging, corrected firewall reject-versus-drop semantics, and Windows WFP filters installed by default.

◆ Prediction

The stated plan to assert low-s signature form when validating certificates is the concrete next step visible in these entries; expect it to land as a breaking validation change in a future release.

Alternatives to FoRecoML and Nebula

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

See all FoRecoML alternatives → · See all Nebula alternatives →

Recent activity from FoRecoML and Nebula

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

  1. 26d agoNebulaBreaking: slog logging, corrected firewall reject/drop directions, Windows WFP filters
  2. 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
  3. 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
  4. 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN
  5. 6mo agoNebulaP256 signature malleability allowed blocklist bypass
  6. 6mo agoNebulaFix panic in use_system_route_table introduced by the previous release
  7. 7mo agoNebulaRoute-reload, handshake, and Windows listener fixes after the v1.10 rework
  8. 8mo agoNebulaIPv6 and multiple addresses in the overlay, plus a v2 certificate format
  9. 10mo agoNebulaPackets accepted from erroneous source IPs with unsafe_routes or multi-IP certificates

Frequently asked questions

What is the difference between FoRecoML and Nebula?

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

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

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

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.