mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
Trackingplan vs vetiver
A side-by-side editorial comparison of Trackingplan and vetiver — release velocity, themes, recent moves, and the top alternatives to consider.
Trackingplan vs vetiver: at a glance
What is Trackingplan?
Trackingplan turns tracking-plan validation into AI-assisted, consent-aware observability.
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
What is vetiver?
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
Trackingplan vs vetiver: editorial side-by-side
Trackingplan
5.0ANALYTICS
Trackingplan turns tracking-plan validation into AI-assisted, consent-aware observability.
◆ Current state
Trackingplan monitors analytics implementations for drift and now anchors its workflow on two pillars: an AI Debugger that supplies root-cause analysis and recommended fixes, and Consent Monitoring that watches CMPs for privacy compliance. Recent releases connect these — deep links from charts into RCA and Data Explorer, shareable warning links, and consolidated troubleshooting views.
◆ Where it's heading
The product is moving from passive tracking-plan validation toward active, guided remediation. Each release tightens the loop between detecting a problem (a warning, a consent gap) and resolving it — AI Debugger is spreading from generic warnings to consent warnings, and the UI is being rebuilt around single-surface investigation rather than scattered reports.
◆ Prediction
Expect AI Debugger to reach more warning types and Consent Monitoring to add further CMP integrations, continuing the pattern of extending both features to new surfaces rather than shipping a new pillar.
vetiver
0.0ANALYTICS
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
◆ Current state
vetiver versions, deploys and monitors models: it pins a model, generates a plumber API around it, and writes the Dockerfile to run it. The visible release stream is bug fixes to plumber file generation, one prototype endpoint, and then a two-year gap between 0.2.5 in November 2023 and 0.2.6 in October 2025. The two releases since that gap are compatibility work — recipes' new input data prototype, support for probably, and all versions of xgboost.
◆ Where it's heading
The feature era ended before this window opened. Deploying to SageMaker, generating Docker files, storing renv lockfiles in model metadata and supporting keras, luz and recipes all landed in 0.2.1 and 0.2.2; nothing since has extended what vetiver does. What it does now is track the rest of tidymodels — when recipes gains a prototype API or probably becomes something a workflow can contain, vetiver adds a line. That is a package holding its position rather than advancing it.
◆ Prediction
The entries do not support a confident prediction of new capability. On this pattern the next release tracks another tidymodels change, most likely the postprocessing stage that workflows added in 1.3.0.
Alternatives to Trackingplan and vetiver
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 Trackingplan or vetiver.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk
timetk swallowed anomalize whole, then went quiet for two years
modelbased
modelbased is turning marginal effects into a full contrast grammar
parameters
easystats' parameters package absorbs one more model class every few weeks
See all Trackingplan alternatives → · See all vetiver alternatives →
Recent activity from Trackingplan and vetiver
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agoTrackingplanConsent Monitoring: Faster investigation and clearer navigation | Trackingplan Latest Features
- 21d agoTrackingplanDeep Audits, ready in seconds with the new step-by-step wizard | Trackingplan Latest Features
- 21d agoTrackingplanData Explorer Loads Faster on Starred Events for Large Plans | Trackingplan Latest Features
- 21d agoTrackingplanAI Debugger Now Available for Consent Warnings | Trackingplan Latest Features
- 1mo agoTrackingplanClearer Validation Warnings in Tracks Explorer | Trackingplan Latest Features
- 1mo agoTrackingplanAdvanced aggregations in Data Explorer | Trackingplan Latest Features
- 8mo agovetiverSupport all versions of xgboost
- 9mo agovetiverFirst release in two years catches up with recipes and probably
- 2y agovetiverFix plumber file generation bug
- 2y agovetiverFix plumber generation for board_url() pins
- 3y agovetivervetiver 0.2.3
- 3y agovetiverModels expose their input prototype over HTTP
Frequently asked questions
What is the difference between Trackingplan and vetiver?
They serve adjacent needs but don't currently overlap on shipped themes. Trackingplan is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Is Trackingplan better than vetiver?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Trackingplan is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
What are the best alternatives to Trackingplan?
Top Trackingplan alternatives in Analytics are ranked by recent ship velocity. Browse the "Trackingplan alternatives" section above for the current picks, or visit /alternatives/trackingplan for the full list with editorial commentary on each.
What are the best alternatives to vetiver?
Top vetiver alternatives in Analytics are ranked by recent ship velocity. Browse the "vetiver alternatives" section above for the current picks, or visit /alternatives/vetiver-r for the full list with editorial commentary on each.