← Back to home
Comparison · Analytics

brulee vs webmockr

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

brulee vs webmockr: at a glance

Featurebruleewebmockr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdeep-learning, tabular-models, torch, tidymodelshttp-mocking, testing, httr2, ropensci
Last editorial update3h 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 webmockr?

The stubbing library added httr2 support, then spent a year cutting itself free of everything else

webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.

Read the full webmockr trajectory →

brulee vs webmockr: 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.

W
webmockr
ANALYTICS
0.0

The stubbing library added httr2 support, then spent a year cutting itself free of everything else

◆ Current state

webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.

◆ Where it's heading

Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.

◆ Prediction

RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.

Alternatives to brulee and webmockr

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

See all brulee alternatives → · See all webmockr alternatives →

Recent activity from brulee and webmockr

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 agowebmockrvcr dependency severed
  6. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  7. 1y agobruleeNumerical overflow unit test removed
  8. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  9. 1y agobruleebrulee_mlp_two_layer() convenience wrapper for parsnip
  10. 2y agowebmockrhttr2 joins httr and crul as a supported client
  11. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  12. 3y agowebmockrRegex URI matching fixed

Frequently asked questions

What is the difference between brulee and webmockr?

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

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

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