← Back to home
Comparison · Infra & APIs

phyloatlas vs Apache ShenYu

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

phyloatlas vs Apache ShenYu: at a glance

FeaturephyloatlasApache ShenYu
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesphylogenetics, research-data, data-provenance, open-scienceapi-gateway, ai-proxy, mcp, token-limiting
Last editorial update57m ago10d ago
WebsiteVisit →Visit →

What is phyloatlas?

An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.

This is a curated deposit of species-level phylogenies — 264 trees across 62 partitions, 247 of them time-calibrated — paired with a species-name dictionary of roughly 638,000 standardized labels and per-tree provenance. It is moving through peer review at Methods in Ecology and Evolution, and the release stream is essentially a public erratum log: eight releases in five weeks, each reconciling the deposit against source papers, the manuscript, and its own metadata. The most recent replaced the turtle canonical with a 274-tip ultrametric chronogram after the previous tree failed time-calibration integrity checks.

Read the full phyloatlas 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 →

phyloatlas vs Apache ShenYu: editorial side-by-side

P
phyloatlas
INFRA · APIS
0.0

An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.

◆ Current state

This is a curated deposit of species-level phylogenies — 264 trees across 62 partitions, 247 of them time-calibrated — paired with a species-name dictionary of roughly 638,000 standardized labels and per-tree provenance. It is moving through peer review at Methods in Ecology and Evolution, and the release stream is essentially a public erratum log: eight releases in five weeks, each reconciling the deposit against source papers, the manuscript, and its own metadata. The most recent replaced the turtle canonical with a 274-tip ultrametric chronogram after the previous tree failed time-calibration integrity checks.

◆ Where it's heading

The project's defining decision is that it archives the recipe rather than the corpus. Since 1.0.3 the Zenodo deposit holds metadata, provenance, and standardization code while the tree files live at their original sources, and the same principle was applied again when the TimeTree-of-Life was removed at the TimeTree project's request and reduced to a citation. What makes the correction log unusual is its direction: partitions keep getting reclassified from dated to undated as verification confirms the source papers described chronograms they never deposited. The atlas is being built to be honest about archival uncertainty rather than to maximize coverage.

◆ Prediction

The release cadence is driven by the manuscript review cycle, so expect corrections to continue until MEE acceptance and then slow sharply; the open thread most likely to produce the next one is the remaining recoverable archival uncertainty flagged across non-Condamine dated source trees.

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

See all phyloatlas alternatives → · See all Apache ShenYu alternatives →

Recent activity from phyloatlas and Apache ShenYu

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

  1. 1mo agophyloatlasv1.0.8 — turtle chronogram canonical; MEE integrity pass
  2. 1mo agophyloatlasv1.0.7 — restore species-name dictionary
  3. 1mo agophyloatlasv1.0.6 — data-integrity corrections + TimeTree de-redistribution
  4. 2mo agophyloatlasv1.0.5 — consistency corrections
  5. 2mo agophyloatlasv1.0.4 — data corrections + canonical succession (Supplementary Table S7)
  6. 2mo agophyloatlasv1.0.3 — title alignment, LICENSE, three-category framework, sensitivity bounds
  7. 8mo agoApache ShenYuMCP server plugin fixes and Nacos sync cache corrections
  8. 11mo agoApache ShenYuAI request transformer plugin joins the proxy and token limiter
  9. 1y agoApache ShenYuJWT SPI extension and Dubbo method configuration land

Frequently asked questions

What is the difference between phyloatlas and Apache ShenYu?

They serve adjacent needs but don't currently overlap on shipped themes. phyloatlas 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 phyloatlas better than Apache ShenYu?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. phyloatlas 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 phyloatlas?

Top phyloatlas alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "phyloatlas alternatives" section above for the current picks, or visit /alternatives/phylo-species-atlas 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.