← Back to home
Comparison · Analytics

brulee vs Tplyr

A side-by-side editorial comparison of brulee and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.

brulee vs Tplyr: at a glance

FeaturebruleeTplyr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdeep-learning, tabular-models, torch, tidymodelsclinical-trials, tables, traceability, r-package
Last editorial update4h ago1h ago
WebsiteVisit →Visit →

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.

Read the full brulee trajectory →

What is Tplyr?

Tplyr made clinical summary tables explain where every number came from.

Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.

Read the full Tplyr trajectory →

brulee vs Tplyr: editorial side-by-side

B
brulee
ANALYTICS
0.0

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.

T
Tplyr
ANALYTICS
0.0

Tplyr made clinical summary tables explain where every number came from.

◆ Current state

Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.

◆ Where it's heading

Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.

◆ Prediction

Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.

Alternatives to brulee and Tplyr

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 Tplyr.

See all brulee alternatives → · See all Tplyr alternatives →

Recent activity from brulee and Tplyr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agobruleeModel weights no longer download on package attach
  2. 1mo agobruleeTabICL foundation model added, gradient clipping extended
  3. 1mo agobruleeFive new architectures and GPU support arrive at 1.0.0
  4. 11mo agobrulee64-bit tensors and new optimizers to stop loss overflow
  5. 1y agobruleeNumerical overflow unit test removed
  6. 1y agobruleebrulee_mlp_two_layer() convenience wrapper for parsnip
  7. 2y agoTplyrMissing-subject metadata, add_anti_join(), and nested-layer fixes
  8. 3y agoTplyrMetadata vignette fix and parenthesis hugging
  9. 3y agoTplyrDenominator logic fix ahead of CRAN release
  10. 3y agoTplyrReverse-dependency fix
  11. 3y agoTplyr1.0.0 introduces the traceability metadata framework

Frequently asked questions

What is the difference between brulee and Tplyr?

They serve adjacent needs but don't currently overlap on shipped themes. brulee and Tplyr 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 Tplyr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. brulee and Tplyr 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 Tplyr?

Top Tplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "Tplyr alternatives" section above for the current picks, or visit /alternatives/tplyr for the full list with editorial commentary on each.