← Back to home
Comparison · Infra & APIs

FoReco vs Apache ShenYu

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

FoReco vs Apache ShenYu: at a glance

FeatureFoRecoApache ShenYu
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, hierarchical-reconciliation, time-series, s3-classesapi-gateway, ai-proxy, mcp, token-limiting
Last editorial update54m ago10d ago
WebsiteVisit →Visit →

What is FoReco?

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

Read the full FoReco trajectory →

What is Apache ShenYu?

An API gateway that has quietly grown an LLM plugin family — and then stopped shipping.

Apache ShenYu's tracked releases run through the 2.7.0.x patch line and stop in November 2025. The consistent thread across those releases is a set of AI plugins accumulating alongside the traditional gateway ones: an AI proxy, an AI token limiter, an AI request transformer, and an MCP server plugin that shows up in the most recent entry through timeout and request-size fixes. The rest of each release is bug fixing and test coverage, with configuration synchronization through Nacos accounting for a recurring share of the defects.

Read the full Apache ShenYu trajectory →

FoReco vs Apache ShenYu: editorial side-by-side

F
FoReco
INFRA · APIS
0.0

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

◆ Current state

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

◆ Where it's heading

The package is completing a reversal it started in 1.0.0. That release simplified outputs to plain matrices and pushed metadata into attributes reachable via recoinfo(); 1.3.0 removed recoinfo() outright and put the structure back as a class with components(), summary(), and plot() methods. The direction is toward being infrastructure rather than a function library — the class is exported through new_foreco_class() and a sibling package has already adopted it. Method coverage has meanwhile broadened from optimal combination into non-negative algorithms, bounded reconciliation, and Gaussian and sample-based probabilistic variants.

◆ Prediction

The soft-deprecated res2matrix() is flagged for removal, so a subsequent release should finish that cleanup; with the class now exported, expect more methods to hang off foreco objects rather than more top-level functions.

A
Apache ShenYu
INFRA · APIS
0.0

An API gateway that has quietly grown an LLM plugin family — and then stopped shipping.

◆ Current state

Apache ShenYu's tracked releases run through the 2.7.0.x patch line and stop in November 2025. The consistent thread across those releases is a set of AI plugins accumulating alongside the traditional gateway ones: an AI proxy, an AI token limiter, an AI request transformer, and an MCP server plugin that shows up in the most recent entry through timeout and request-size fixes. The rest of each release is bug fixing and test coverage, with configuration synchronization through Nacos accounting for a recurring share of the defects.

◆ Where it's heading

ShenYu is positioning as a gateway for model traffic as well as service traffic, and the pattern is telling — the AI plugins appear first as features and then, one release later, as bug reports, which is what real usage looks like. Rate limiting by token rather than by request is the specific piece that matters, since it is the unit LLM providers actually bill on. Against that, the release notes are undifferentiated pull-request lists and nothing has shipped in the tracked feed for over eight months.

◆ Prediction

Expect further hardening of the MCP server plugin, which is the newest and least settled of the AI additions. The gap since 2.7.0.3 should be checked against the project's actual activity before drawing conclusions from it.

Alternatives to FoReco and Apache ShenYu

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 FoReco or Apache ShenYu.

See all FoReco alternatives → · See all Apache ShenYu alternatives →

Recent activity from FoReco and Apache ShenYu

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

  1. 1mo agoFoRecoStrict argument validation and a pruned help index
  2. 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object
  3. 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
  4. 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
  5. 8mo agoApache ShenYuMCP server plugin fixes and Nacos sync cache corrections
  6. 11mo agoApache ShenYuAI request transformer plugin joins the proxy and token limiter
  7. 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
  8. 1y agoApache ShenYuJWT SPI extension and Dubbo method configuration land
  9. 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions

Frequently asked questions

What is the difference between FoReco and Apache ShenYu?

They serve adjacent needs but don't currently overlap on shipped themes. FoReco and Apache ShenYu are shipping at a similar cadence (velocity 0.0 vs 0.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 FoReco better than Apache ShenYu?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoReco and Apache ShenYu are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to FoReco?

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

What are the best alternatives to Apache ShenYu?

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