← Back to home
Comparison · Infra & APIs

Depot vs phyloatlas

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

Depot vs phyloatlas: at a glance

FeatureDepotphyloatlas
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d10
Top themesci-cd, build-acceleration, test-intelligence, git-hostingphylogenetics, research-data, data-provenance, open-science
Last editorial update5d ago57m ago
WebsiteVisit →

What is Depot?

Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.

Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.

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

Depot vs phyloatlas: editorial side-by-side

D
Depot
INFRA · APIS
6.3

Depot keeps absorbing the CI stack — tests, networking, runners, now its own git host.

◆ Current state

Depot has moved well past build caching. Test results reached general availability in July with org-wide flaky, slow, and recurring failure analytics plus timing-based shard splitting; Sherlock's AI analysis became available on any run rather than only failed ones; and CI jobs can join a Tailscale tailnet to reach private services. The runner fleet now defaults to macOS 26 on M4 hardware, Depot CI understands GitHub stacked pull requests, and Depot Code — a diskless git server backed by blob storage — entered private beta.

◆ Where it's heading

The pattern is absorbing each adjacent piece of the pipeline that Depot's position already gives it data about. It runs the builds, so it owns test timing, so it can balance shards; it runs the jobs, so it can diagnose them; it hosts the runners, so it can wire private networking into them. Depot Code extends the same logic upstream to source hosting, which would close the loop between repository and runner. A quieter parallel thread keeps moving SDK- and dashboard-only settings into the CLI, stated explicitly as making projects configurable by agents and scripts.

◆ Prediction

Depot Code widening past private beta and binding more tightly to CI is the move the rest of the window sets up. The test work is also positioned to go from reporting to selection — skipping tests a change cannot affect — since Depot now holds the timing and failure history that would require, though the entries stop short of saying so.

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

See all Depot alternatives → · See all phyloatlas alternatives →

Recent activity from Depot and phyloatlas

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

  1. 9d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
  2. 16d agoDepotDepot CI now supports native GitHub stacked pull requests
  3. 19d agoDepotSet cache retention when creating a project with --cache-policy-keep-days
  4. 20d agoDepotView and edit project details from the Depot CLI
  5. 21d agoDepotTest results are now generally available
  6. 29d agoDepotAI analysis available for all Depot CI workflows and jobs
  7. 1mo agophyloatlasv1.0.8 — turtle chronogram canonical; MEE integrity pass
  8. 1mo agophyloatlasv1.0.7 — restore species-name dictionary
  9. 1mo agophyloatlasv1.0.6 — data-integrity corrections + TimeTree de-redistribution
  10. 2mo agophyloatlasv1.0.5 — consistency corrections
  11. 2mo agophyloatlasv1.0.4 — data corrections + canonical succession (Supplementary Table S7)
  12. 2mo agophyloatlasv1.0.3 — title alignment, LICENSE, three-category framework, sensitivity bounds

Frequently asked questions

What is the difference between Depot and phyloatlas?

They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Depot better than phyloatlas?

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

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