← Back to home
Comparison · Infra & APIs

authentik vs inlabru

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

authentik vs inlabru: at a glance

Featureauthentikinlabru
SectorInfra & APIsInfra & APIs
Velocity score6.32.5
Sparks · 30d10
Top themesidentity-provider, enterprise-agents, endpoint-identity, oauth2bayesian-modelling, spatial-statistics, r-package, api-consolidation
Last editorial update14h ago38m ago
WebsiteVisit →Visit →

What is authentik?

authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO

2026.8.0 is out, closing a seven-candidate train that ran through early August. The GA tag itself is the last cherry-pick batch — SCIM group membership removals, a proxy redirect that preserves query strings, session deletion on user deactivation — but the release it finalizes is where the substance lives: an Actors primitive in core, an enterprise Agent requiring a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.

Read the full authentik 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 →

authentik vs inlabru: editorial side-by-side

A
authentik
INFRA · APIS
6.3

authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO

◆ Current state

2026.8.0 is out, closing a seven-candidate train that ran through early August. The GA tag itself is the last cherry-pick batch — SCIM group membership removals, a proxy redirect that preserves query strings, session deletion on user deactivation — but the release it finalizes is where the substance lives: an Actors primitive in core, an enterprise Agent requiring a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.

◆ Where it's heading

Two threads converge in this major. The identity surface keeps broadening at the protocol edge — CAS, WS-Fed, token exchange delegation, on-behalf-of — while the enterprise tier grows an endpoint story that reaches machines and devices rather than browser sessions. The RC train's shape reinforces it: six candidates fired in one day on CI and docs, then one heavy candidate carrying the features, then a fix-only close. That is release engineering hardened around a major, not a routine point release.

◆ Prediction

With Agents and Actors now GA rather than cherry-picks, the next branch should build out what they enable — device-conditioned policies or agent-brokered credentials — while 2026.8.x settles into backport patches.

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

See all authentik alternatives → · See all inlabru alternatives →

Recent activity from authentik and inlabru

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

  1. 1d agoauthentikauthentik 2026.8 goes GA with Actors and domain-joined Agents
  2. 9d agoauthentikauthentik 2026.8.0-rc7 lands Actors, enterprise Agents, and CAS sources
  3. 16d agoauthentik2026.8.0-rc6: flaky test and CI metadata fixes
  4. 16d agoauthentik2026.8.0-rc5: release plumbing only
  5. 16d agoauthentik2026.8.0-rc4: fix-only candidate
  6. 16d agoauthentik2026.8.0-rc3: cherry-picked fixes and CI work
  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 authentik and inlabru?

They serve adjacent needs but don't currently overlap on shipped themes. authentik is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 authentik better than inlabru?

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

Top authentik alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "authentik alternatives" section above for the current picks, or visit /alternatives/authentik 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.