ANALYTICS
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
Alternatives · analytics tools
nanoparquet alternatives
The best nanoparquet alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to nanoparquet? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, nanoparquet shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to nanoparquet
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
ANALYTICS
crul took mocking back from webmockr and made it a property of the client itself
ANALYTICS
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
ANALYTICS
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
ANALYTICS
Six years since the last functional change, and Google renamed the service it wraps in the release before that
ANALYTICS
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do
ANALYTICS
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since
ANALYTICS
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
ANALYTICS
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
ANALYTICS
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers
ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
nanoparquet vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| nanoparquet (baseline) | 0.0 | 0 | parquetr-languageinteroperability | Schema authoring and append_parquet arrive with a renamed API |
| DoseFinding | 0.0 | 0 | dose-responsemcp-modclinical-trials | Model averaging arrives for dose-response fitting |
| webmockr | 0.0 | 0 | http-mockingtestinghttr2 | httr2 joins httr and crul as a supported client |
| crul | 0.0 | 0 | http-clientasyncmocking | Mocking becomes a client parameter, independent of webmockr |
| dendroNetwork | 0.0 | 0 | dendrochronologynetwork-analysiscytoscape | — |
| chattr | 0.0 | 0 | llmrstudioide-integration | All model integration moves to ellmer, direct backends removed |
| cloudml | 0.0 | 0 | machine-learninggoogle-cloudtensorflow | — |
| tidymodels | 0.0 | 0 | tidymodelsmeta-packagedependency-management | — |
| datapack | 0.0 | 0 | research-datadataoneprovenance | Assembled data packages become editable in place |
| USAboundaries | 0.0 | 0 | geospatialcensus-datasf | Data split into a companion package; all boundaries become sf |
| slider | 0.0 | 0 | sliding-windowstidyversec-api-compliance | — |
| simtrial | 0.0 | 0 | clinical-trialsgroup-sequentialsurvival-analysis | RMST and milestone tests, plus a user-definable cut and test framework |
| nodbi | 0.0 | 0 | document-databasesjsonduckdb | Query results get consistent column types; fast NDJSON import reaches SQLite and Postgres |
The 12 best nanoparquet alternatives, in depth
1. DoseFinding · velocity 0.0
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Model averaging arrives for dose-response fitting”.
Where nanoparquet leans on parquet, r language and interoperability, DoseFinding focuses on dose response, mcp mod and clinical trials.
DoseFinding and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full DoseFinding trajectory → · Compare nanoparquet vs DoseFinding →
2. webmockr · velocity 0.0
The stubbing library added httr2 support, then spent a year cutting itself free of everything else.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “httr2 joins httr and crul as a supported client”.
Where nanoparquet leans on parquet, r language and interoperability, webmockr focuses on http mocking, testing and httr2.
webmockr and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full webmockr trajectory → · Compare nanoparquet vs webmockr →
3. crul · velocity 0.0
Crul took mocking back from webmockr and made it a property of the client itself.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Mocking becomes a client parameter, independent of webmockr”.
Where nanoparquet leans on parquet, r language and interoperability, crul focuses on http client, async and mocking.
crul and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. dendroNetwork · velocity 0.0
Six releases, six identical bodies — the feed carries the package abstract instead of release notes.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where nanoparquet leans on parquet, r language and interoperability, dendroNetwork focuses on dendrochronology, network analysis and cytoscape.
dendroNetwork and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full dendroNetwork trajectory → · Compare nanoparquet vs dendroNetwork →
5. chattr · velocity 0.0
Chattr deleted every LLM integration it had written and outsourced the lot to ellmer.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “All model integration moves to ellmer, direct backends removed”.
Where nanoparquet leans on parquet, r language and interoperability, chattr focuses on llm, rstudio and ide integration.
chattr and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
6. cloudml · velocity 0.0
Six years since the last functional change, and Google renamed the service it wraps in the release before that.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where nanoparquet leans on parquet, r language and interoperability, cloudml focuses on machine learning, google cloud and tensorflow.
cloudml and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full cloudml trajectory → · Compare nanoparquet vs cloudml →
7. tidymodels · velocity 0.0
The meta-package ships almost nothing, which is exactly what a version-pinning shim should do.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where nanoparquet leans on parquet, r language and interoperability, tidymodels focuses on tidymodels, meta package and dependency management.
tidymodels and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full tidymodels trajectory → · Compare nanoparquet vs tidymodels →
8. datapack · velocity 0.0
The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Assembled data packages become editable in place”.
Where nanoparquet leans on parquet, r language and interoperability, datapack focuses on research data, dataone and provenance.
datapack and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full datapack trajectory → · Compare nanoparquet vs datapack →
9. USAboundaries · velocity 0.0
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Data split into a companion package; all boundaries become sf”.
Where nanoparquet leans on parquet, r language and interoperability, USAboundaries focuses on geospatial, census data and sf.
USAboundaries and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full USAboundaries trajectory → · Compare nanoparquet vs USAboundaries →
10. slider · velocity 0.0
Feature-complete since 2021, and every release since has been paying CRAN's C API bill.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where nanoparquet leans on parquet, r language and interoperability, slider focuses on sliding windows, tidyverse and c api compliance.
slider and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. simtrial · velocity 0.0
A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “RMST and milestone tests, plus a user-definable cut and test framework”.
Where nanoparquet leans on parquet, r language and interoperability, simtrial focuses on clinical trials, group sequential and survival analysis.
simtrial and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full simtrial trajectory → · Compare nanoparquet vs simtrial →
12. nodbi · velocity 0.0
One document API over six databases, and every release is spent absorbing their JSON engines' churn.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Query results get consistent column types; fast NDJSON import reaches SQLite and Postgres”.
Where nanoparquet leans on parquet, r language and interoperability, nodbi focuses on document databases, json and duckdb.
nodbi and nanoparquet have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to nanoparquet?
The top nanoparquet alternatives we currently track in analytics tools are DoseFinding, webmockr, crul, dendroNetwork, chattr, ranked by recent ship velocity.
How is this list of nanoparquet alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare nanoparquet directly with one of these alternatives?
Yes — every card has a "Compare with nanoparquet" link to a side-by-side /compare page.