← Back to home
Comparison · Infra & APIs

ggalign vs inlabru

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

ggalign vs inlabru: at a glance

Featureggaligninlabru
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesggplot2, layout, heatmaps, s7bayesian-modelling, spatial-statistics, r-package, api-consolidation
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

What is ggalign?

Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.

ggalign composes multiple ggplots against a shared observation ordering, covering heatmap annotation, oncoplots, phylogenies and circular layouts. Releases have come roughly monthly through 2025, first completing the layout system, then migrating the internals to S7 and absorbing the ggplot2 4.0 changes. The alignment machinery is now exported for other packages to build on.

Read the full ggalign trajectory →

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 →

ggalign vs inlabru: editorial side-by-side

G
ggalign
INFRA · APIS
0.0

Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.

◆ Current state

ggalign composes multiple ggplots against a shared observation ordering, covering heatmap annotation, oncoplots, phylogenies and circular layouts. Releases have come roughly monthly through 2025, first completing the layout system, then migrating the internals to S7 and absorbing the ggplot2 4.0 changes. The alignment machinery is now exported for other packages to build on.

◆ Where it's heading

Two threads run in parallel. One widens what can be aligned, with sector facets, ideograms, image point shapes and observation linking. The other keeps rebuilding the foundation, with the S7 migration, repeated renames toward consistent naming, and the deliberate handing of element_polygon() and element_curve() upstream to ggplot2. The renaming is aggressive enough that each recent release soft-deprecates something.

◆ Prediction

With the internals on S7 and the Patch object exported, the next step is most likely stabilising those names rather than another refactor.

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.

Alternatives to ggalign and inlabru

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 ggalign or inlabru.

See all ggalign alternatives → · See all inlabru alternatives →

Recent activity from ggalign and inlabru

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  3. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  4. 10mo agoggalignalignpatch internals moved to S7; Patch object exported
  5. 11mo agoggalignInternals migrated to S7; ideogram, tags and image shapes
  6. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  7. 1y agoggalignz aesthetic scales and guide collection in borders
  8. 1y agoggalignchannelGrob() draws across facets; ggplot2 3.5.2 fix
  9. 1y agoggalignLayout system declared complete; polar facets and coord_circle()
  10. 1y agoggalignLayouts split into discrete and continuous; linking system added
  11. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack

Frequently asked questions

What is the difference between ggalign and inlabru?

They serve adjacent needs but don't currently overlap on shipped themes. 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 ggalign better than inlabru?

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 ggalign?

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

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.