← Back to home
Comparison · Infra & APIs

Nomad vs phyloatlas

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

Nomad vs phyloatlas: at a glance

FeatureNomadphyloatlas
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesorchestration, container-isolation, cve-response, namespace-boundariesphylogenetics, research-data, data-provenance, open-science
Last editorial update17d ago57m ago
WebsiteVisit →Visit →

What is Nomad?

Nomad's July release closed two Docker CVEs that let tasks escape their own driver configuration.

HashiCorp is cutting 1.11.x and 1.10.x Enterprise releases in matched pairs, seconds apart, with identical content. July's pair carried two Docker CVEs — one where allowed_modes or allow_privileged was not enforced before setting host namespace modes, one where a symlink let a task bypass volumes.enabled=false — plus a dynamic host volume bug that let a namespace-scoped delete permission remove another namespace's claims.

Read the full Nomad trajectory →

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 →

Nomad vs phyloatlas: editorial side-by-side

N
Nomad
INFRA · APIS
5.0

Nomad's July release closed two Docker CVEs that let tasks escape their own driver configuration.

◆ Current state

HashiCorp is cutting 1.11.x and 1.10.x Enterprise releases in matched pairs, seconds apart, with identical content. July's pair carried two Docker CVEs — one where allowed_modes or allow_privileged was not enforced before setting host namespace modes, one where a symlink let a task bypass volumes.enabled=false — plus a dynamic host volume bug that let a namespace-scoped delete permission remove another namespace's claims.

◆ Where it's heading

All three July fixes are the same failure: a boundary that was declared in configuration but not enforced at the point of use. Alongside that, the improvements are about degraded-mode operation — falling back to the client agent's Consul token when workload identity is unavailable, Vault token renewal retries, an optional Init hook for task driver plugins. Nomad is hardening the seams between the scheduler and the systems it delegates to.

◆ Prediction

Expect the paired Enterprise releases to continue at monthly cadence, with further fixes concentrated in the Docker driver and dynamic host volumes, where the isolation boundaries are newest.

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.

Alternatives to Nomad and phyloatlas

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 Nomad or phyloatlas.

See all Nomad alternatives → · See all phyloatlas alternatives →

Recent activity from Nomad and phyloatlas

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

  1. 1mo agoNomadTwo Docker CVEs and a cross-namespace volume delete
  2. 1mo agoNomadSame CVE batch backported to the 1.10 line
  3. 1mo agophyloatlasv1.0.8 — turtle chronogram canonical; MEE integrity pass
  4. 1mo agophyloatlasv1.0.7 — restore species-name dictionary
  5. 1mo agophyloatlasv1.0.6 — data-integrity corrections + TimeTree de-redistribution
  6. 2mo agophyloatlasv1.0.5 — consistency corrections
  7. 2mo agoNomadDebug bundle redaction, Vault retries, template restart fix
  8. 2mo agoNomad1.11 twin of the June maintenance release
  9. 2mo agophyloatlasv1.0.4 — data corrections + canonical succession (Supplementary Table S7)
  10. 2mo agophyloatlasv1.0.3 — title alignment, LICENSE, three-category framework, sensitivity bounds
  11. 2mo agoNomadThree web UI rendering fixes
  12. 2mo agoNomad1.11 twin of the May UI fix release

Frequently asked questions

What is the difference between Nomad and phyloatlas?

They serve adjacent needs but don't currently overlap on shipped themes. Nomad is currently shipping more aggressively (velocity 5.0 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 Nomad better than phyloatlas?

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

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

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.