← Back to home
Comparison · Infra & APIs

inlabru vs Jackett

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

inlabru vs Jackett: at a glance

FeatureinlabruJackett
SectorInfra & APIsInfra & APIs
Velocity score2.55.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationindexers, torrent-search, maintenance, daily-releases
Last editorial update46m ago5h ago
WebsiteVisit →Visit →

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.

Read the full inlabru trajectory →

What is Jackett?

Daily tags chasing tracker domain moves, login changes and freeleech detection

Jackett continues to ship a tag most mornings, each one a short auto-generated commit list of indexer definition edits. The newest adds a cookie login variant for HD-Space and captcha-aware login for funfile; the day before was a sweep of domain bumps and download-volume-factor detection corrections across torrenttip, magnetcat, 52bt, torrenteros, tocashare and seedcore. No release in this window touches the application itself.

Read the full Jackett trajectory →

inlabru vs Jackett: editorial side-by-side

I
inlabru
INFRA · APIS
2.5

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.

J
Jackett
INFRA · APIS
5.0

Daily tags chasing tracker domain moves, login changes and freeleech detection

◆ Current state

Jackett continues to ship a tag most mornings, each one a short auto-generated commit list of indexer definition edits. The newest adds a cookie login variant for HD-Space and captcha-aware login for funfile; the day before was a sweep of domain bumps and download-volume-factor detection corrections across torrenttip, magnetcat, 52bt, torrenteros, tocashare and seedcore. No release in this window touches the application itself.

◆ Where it's heading

This is maintenance as a product, and the cadence is the feature. Trackers rotate domains, add captchas, switch to cookie auth or vary their freeleech percentages, and Jackett absorbs each change within a day — Scenetime was added and dropped within days, 720pier removed and then restored by revert. The recurring shift from form login to cookie and captcha handling across sites is the one visible pattern: the definitions are steadily taking on more anti-bot handling.

◆ Prediction

Expect the same daily cadence of definition edits, with more cookie and captcha login variants as trackers tighten access. The entries show no application-level work planned or in progress.

Alternatives to inlabru and Jackett

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

See all inlabru alternatives → · See all Jackett alternatives →

Recent activity from inlabru and Jackett

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

  1. 8h agoJackettHD-Space cookie login variant; funfile captcha handling
  2. 1d agoJackettDomain bumps and freeleech detection fixes across six trackers
  3. 2d agoJackettIP filtering note for newstudio; anisource goes IPv6-only
  4. 3d agoJackett720pier tracker restored by revert
  5. 4d agoJackettScenetime dropped days after being added; new magnetcat domains
  6. 6d agoJackettdocspedia cookie auth, nyaa season search, duplicate GET fix
  7. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  8. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  9. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  10. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  11. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack

Frequently asked questions

What is the difference between inlabru and Jackett?

They serve adjacent needs but don't currently overlap on shipped themes. Jackett is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Jackett?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jackett is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Jackett?

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