r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
brulee vs nodbi
A side-by-side editorial comparison of brulee and nodbi — release velocity, themes, recent moves, and the top alternatives to consider.
brulee vs nodbi: at a glance
What is brulee?
tidymodels' torch backend grew from MLPs into a tabular deep learning suite with foundation models.
brulee fits neural networks for tidymodels on torch, and 1.0.0 redefined what that means: alongside the original MLP it now ships Regularization Learning Networks, ResNet with skip connections and batch normalization, AutoInt with columnwise attention, SAINT with row and column attention, and Chronos2, a foundational forecasting model. GPU acceleration arrived in the same release with automatic CUDA selection and opt-in MPS. Version 1.1.0 added TabICL, an open-source tabular foundation model, and 1.1.1 spent its time cleaning up the consequences of shipping models that need weight downloads.
What is nodbi?
One document API over six databases, and every release is spent absorbing their JSON engines' churn
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
brulee vs nodbi: editorial side-by-side
brulee
0.0ANALYTICS
tidymodels' torch backend grew from MLPs into a tabular deep learning suite with foundation models.
◆ Current state
brulee fits neural networks for tidymodels on torch, and 1.0.0 redefined what that means: alongside the original MLP it now ships Regularization Learning Networks, ResNet with skip connections and batch normalization, AutoInt with columnwise attention, SAINT with row and column attention, and Chronos2, a foundational forecasting model. GPU acceleration arrived in the same release with automatic CUDA selection and opt-in MPS. Version 1.1.0 added TabICL, an open-source tabular foundation model, and 1.1.1 spent its time cleaning up the consequences of shipping models that need weight downloads.
◆ Where it's heading
The package has crossed from a torch convenience wrapper into a catalog of current tabular architectures, and the recent releases show it absorbing what that costs. Pretrained weights meant a 400MB download, so 1.1.1 stopped fetching them on attach and moved the cache to the platform-appropriate R_user_dir location. Numerical robustness is the other constant thread — 64-bit tensors, Gaussian initialization, gradient clipping extended architecture by architecture, and a ResNet batch-normalization bug where a single-row trailing batch produced all-NA predictions.
◆ Prediction
Gradient clipping has been rolled out one architecture at a time and TabICL is the newest arrival, so the likely next step is bringing the foundation models to parity with the trained ones on device selection, prediction types, and the tuning surface.
nodbi
0.0ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
◆ Current state
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
◆ Where it's heading
Two threads dominate. The first is performance, pursued backend by backend: fast direct NDJSON import moved from DuckDB-only to SQLite and PostgreSQL, query refactors chasing each DuckDB release, and the removal of expensive tree-walking where a cheaper path exists. The second is making results predictable — consistent column types, version checks on the database backend, clearer messages when a Postgres database does not exist yet or when column names contain the dots nodbi reserves for JSON paths.
◆ Prediction
Given that most recent releases are triggered by DuckDB and RSQLite version changes, the next one likely follows the same pattern — adopting a new JSON function or working around a slow one. The duplicate-_id handling added in 0.14.0 suggests NDJSON ingestion edge cases are the current active area.
Alternatives to brulee and nodbi
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 brulee or nodbi.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all brulee alternatives → · See all nodbi alternatives →
Recent activity from brulee and nodbi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agobruleeModel weights no longer download on package attach
- 1mo agobruleeTabICL foundation model added, gradient clipping extended
- 1mo agobruleeFive new architectures and GPU support arrive at 1.0.0 ⚡
- 8mo agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
- 11mo agobrulee64-bit tensors and new optimizers to stop loss overflow
- 1y agonodbiDuckDB version parsing and listfields fix
- 1y agonodbidocdb_query reworked for DuckDB 1.3.0
- 1y agobruleeNumerical overflow unit test removed
- 1y agonodbiNDJSON writing delegated to DuckDB's internal function
- 1y agobruleebrulee_mlp_two_layer() convenience wrapper for parsnip
- 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres ⚡
- 1y agonodbiQuery and file-import speedups via newer DuckDB features
Frequently asked questions
What is the difference between brulee and nodbi?
They serve adjacent needs but don't currently overlap on shipped themes. brulee and nodbi are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is brulee better than nodbi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. brulee and nodbi are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to brulee?
Top brulee alternatives in Analytics are ranked by recent ship velocity. Browse the "brulee alternatives" section above for the current picks, or visit /alternatives/brulee for the full list with editorial commentary on each.
What are the best alternatives to nodbi?
Top nodbi alternatives in Analytics are ranked by recent ship velocity. Browse the "nodbi alternatives" section above for the current picks, or visit /alternatives/nodbi for the full list with editorial commentary on each.