bbotk
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
A side-by-side editorial comparison of Neo4j and yardstick — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Neo4j | yardstick |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | graph-database, graph-data-science, free-tier, access-control | metrics, tidymodels, fairness, survival-analysis |
| Last editorial update | 15h ago | 49m ago |
| Website | — | Visit → |
Neo4j moves its full graph algorithm catalog onto the free tier and adds attribute-based access control.
Neo4j is pushing capability downward and outward at the same time. The complete Graph Data Science catalog — 65+ algorithms — now runs on AuraDB Free in isolated, unbilled sessions, while Business Critical and Virtual Dedicated Cloud tiers gain attribute-based access control with time-windowed permissions and IdP claim mapping. Around those, the Aura platform continues its monthly cadence: Cypher 25 picked up GROUP BY and a GQL cardinality function, quantized vector search reached general availability, and the Query editor gained persistent tabs.
yardstick made fairness metrics a first-class part of tidymodels evaluation
yardstick supplies the metrics tidymodels evaluates models with. Its recent history is metric expansion into areas the package did not originally cover - survival analysis, model fairness, and in 1.4.0 a batch of regression and classification metrics filling remaining gaps - alongside a long deprecation cycle that finally turned errors on in 1.4.0.
Neo4j is pushing capability downward and outward at the same time. The complete Graph Data Science catalog — 65+ algorithms — now runs on AuraDB Free in isolated, unbilled sessions, while Business Critical and Virtual Dedicated Cloud tiers gain attribute-based access control with time-windowed permissions and IdP claim mapping. Around those, the Aura platform continues its monthly cadence: Cypher 25 picked up GROUP BY and a GQL cardinality function, quantized vector search reached general availability, and the Query editor gained persistent tabs.
The shape here is a funnel. Free-tier users get the algorithm catalog and hosted MCP access with no billing and no setup, which lowers the cost of the first serious graph experiment to nothing; enterprise tiers get the governance controls that make an expansion defensible. Cypher is simultaneously being pulled toward the GQL standard and extended with new surfaces — auth rules, grouping clauses — so the query language is absorbing work that used to sit in configuration and driver code.
Expect ABAC to descend to Professional tiers and the Aura Graph Analytics free session limits to become the pressure point Neo4j uses to convert experiments into paid capacity. The unresolved question from these entries is whether MCP for Aura reaches Virtual Dedicated Cloud, which is listed as pending.
yardstick supplies the metrics tidymodels evaluates models with. Its recent history is metric expansion into areas the package did not originally cover - survival analysis, model fairness, and in 1.4.0 a batch of regression and classification metrics filling remaining gaps - alongside a long deprecation cycle that finally turned errors on in 1.4.0.
The direction is coverage plus extensibility. Rather than adding fairness metrics one at a time, 1.3.0 shipped new_groupwise_metric() so group-aware metrics can be defined for the problem at hand, which is the more durable contribution. The parallel thread is removing hidden state: the event_first global option, deprecated in 0.0.7, took until 1.4.0 to become an error.
Expect the groupwise constructor to attract more fairness definitions than the three shipped, and the developer-facing metric creation helpers deprecated in 1.2.0 to be removed next; core metric coverage now looks close to complete.
Other Analytics 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 Neo4j or yardstick.
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
bayesplot keeps widening its posterior-check catalogue while absorbing each ggplot2 break.
Contribution-driven maintenance on a package whose last structural change was magick support.
pins keeps adding a storage backend per release while retiring its original API
tsibble shipped one release in five and a half years - the data structure is finished
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
See all Neo4j alternatives → · See all yardstick alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Neo4j is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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. Neo4j is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Neo4j alternatives in Analytics are ranked by recent ship velocity. Browse the "Neo4j alternatives" section above for the current picks, or visit /alternatives/neo4j for the full list with editorial commentary on each.
Top yardstick alternatives in Analytics are ranked by recent ship velocity. Browse the "yardstick alternatives" section above for the current picks, or visit /alternatives/yardstick for the full list with editorial commentary on each.