vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
Comparison · Infra & APIs
inlabru vs powerly
A side-by-side editorial comparison of inlabru and powerly — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
inlabru vs powerly: at a glance
What is inlabru?
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.
What is powerly?
A dormant sample-size package woke up in 2025 with parallel backends and a three-release DOI farce.
powerly implements a simulation-based method for choosing sample sizes in psychological network models. It sat untouched from September 2022 until August 2025, then shipped five releases in two days. v1.10.0 is the substantive one: parabar parallel backends with progress tracking, validation restricted to specific sample sizes, and warnings when the user picks argument values the method cannot support.
inlabru vs powerly: editorial side-by-side
inlabru
2.5INFRA · APIS
A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time
◆ Current state
inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.
◆ Where it's heading
The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.
◆ Prediction
The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.
powerly
0.0INFRA · APIS
A dormant sample-size package woke up in 2025 with parallel backends and a three-release DOI farce.
◆ Current state
powerly implements a simulation-based method for choosing sample sizes in psychological network models. It sat untouched from September 2022 until August 2025, then shipped five releases in two days. v1.10.0 is the substantive one: parabar parallel backends with progress tracking, validation restricted to specific sample sizes, and warnings when the user picks argument values the method cannot support.
◆ Where it's heading
The reawakening tracks the underlying manuscript reaching publication — v1.9.0 is largely citation, DOI, and website work around a published paper, with CI and documentation debt cleared at the same time. Feature work resumed only after that housekeeping, and it points at usability rather than method: better feedback, better progress reporting, the ability to validate one sample size instead of a whole grid. Three of the five 2025 releases exist only to fix a DOI in the package documentation, one of them undoing the previous one.
◆ Prediction
With the paper published and the parallel-backend request from issue #8 finally closed, further releases most likely continue the usability line — more guardrails on argument choice — rather than extending the statistical method itself.
Alternatives to inlabru and powerly
Other Infra & APIs 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 inlabru or powerly.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
ordinalsimr
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
transltr
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
hereR
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all inlabru alternatives → · See all powerly alternatives →
Recent activity from inlabru and powerly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
- 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
- 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
- 11mo agopowerlyParallel backends with progress tracking, plus targeted validation
- 11mo agopowerlyDOI markup restored in package documentation
- 11mo agopowerlyDOI markup removed from package documentation
- 11mo agopowerlyIncorrect DOI corrected in package documentation
- 11mo agopowerlyThree-year gap closed with citation refresh and an osqp dependency drop
- 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
- 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack ⚡
- 3y agopowerlyInvalid HTML nesting removed from function documentation
Frequently asked questions
What is the difference between inlabru and powerly?
Both compete on the same themes — r-package — within Infra & APIs. inlabru is currently shipping more aggressively (velocity 2.5 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 inlabru better than powerly?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to inlabru?
Top inlabru alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inlabru alternatives" section above for the current picks, or visit /alternatives/inlabru for the full list with editorial commentary on each.
What are the best alternatives to powerly?
Top powerly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "powerly alternatives" section above for the current picks, or visit /alternatives/powerly for the full list with editorial commentary on each.