tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of Neo4j and workflowsets — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Neo4j | workflowsets |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | graph-database, graph-data-science, free-tier, access-control | tidymodels, model-comparison, clustering, tuning |
| Last editorial update | 18h ago | 50m 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.
workflowsets keeps widening what counts as a model worth comparing.
workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.
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.
workflowsets holds a grid of preprocessor and model combinations and evaluates all of them under one call to workflow_map(). The releases in view widen that grid — clustering specifications via tidyclust, censored regression via an eval_time argument, case weights — and fill in the accessors around it with collect_notes(), collect_extracts() and fit_best(). The long-running pull_*() deprecation finally reached the error stage in 1.1.1.
The package's job is comparison, so its direction is set by what tidymodels can express: every time a new model paradigm lands elsewhere, workflowsets has to learn to rank it. Clustering was the largest of those steps because it has no outcome column to score against. Alongside that runs a slower cleanup — named-only optional arguments, type checking on inputs, informative errors when someone passes a workflow set to fit() — that reads as a package hardening after its API settled.
Expect the tailor postprocessors that workflows added in 1.3.0 to need representation here next, since a workflow set that cannot vary the postprocessor cannot compare calibration choices.
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 workflowsets.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
patchwork stopped being a ggplot composer and became a page composer.
See all Neo4j alternatives → · See all workflowsets 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 workflowsets alternatives in Analytics are ranked by recent ship velocity. Browse the "workflowsets alternatives" section above for the current picks, or visit /alternatives/workflowsets for the full list with editorial commentary on each.