L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A side-by-side editorial comparison of eratosthenes and Unkey — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | eratosthenes | Unkey |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 3.8 |
| Sparks · 30d | 0 | 0 |
| Top themes | archaeology, bayesian-inference, mcmc, input-validation | api-platform, container-deploy, developer-tools, cli |
| Last editorial update | 59m ago | 3mo ago |
| Website | Visit → | — |
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
Unkey is racing to harden Deploy into a credible Vercel/Fly alternative.
Unkey has spent April and May turning Deploy from a demo into a usable platform: public beta launch alongside a $4.5M seed and a website refresh, plus autoscaling, ephemeral disks, build cancellation, fork-PR previews, and a CLI deploy path. The trajectory is clearly capability parity with established container-PaaS competitors. Original API key management work (CLI for keys, identities, rate limits) continues underneath but is now secondary to Deploy.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.
With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.
Unkey has spent April and May turning Deploy from a demo into a usable platform: public beta launch alongside a $4.5M seed and a website refresh, plus autoscaling, ephemeral disks, build cancellation, fork-PR previews, and a CLI deploy path. The trajectory is clearly capability parity with established container-PaaS competitors. Original API key management work (CLI for keys, identities, rate limits) continues underneath but is now secondary to Deploy.
Deploy is the company's central bet now and the cadence reflects it: weekly feature drops covering compute, storage, and ops controls. The seed round explicitly funds the path from code to production API, and the editor of choice is moving from the dashboard to the CLI. Expect the security/rate-limit heritage to fold into Deploy as differentiation versus generic container hosts.
The next directional move likely connects Deploy with Unkey's API-key and rate-limit primitives natively, so deployed apps get gateway-grade controls out of the box. A custom domains and TLS story plus more region coverage seem imminent.
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 eratosthenes or Unkey.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
See all eratosthenes alternatives → · See all Unkey alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Unkey is currently shipping more aggressively (velocity 3.8 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Unkey is currently shipping more aggressively (velocity 3.8 vs 2.5), 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.
Top eratosthenes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "eratosthenes alternatives" section above for the current picks, or visit /alternatives/eratosthenes for the full list with editorial commentary on each.
Top Unkey alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Unkey alternatives" section above for the current picks, or visit /alternatives/unkey for the full list with editorial commentary on each.