← Back to home
Comparison · Infra & APIs

PocketBase vs rgm

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

PocketBase vs rgm: at a glance

FeaturePocketBasergm
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesbackend-as-a-service, go, sqlite, supply-chainmicrobiome, graphical-models, bayesian-inference, cran-maintenance
Last editorial update4d ago1h ago
WebsiteVisit →Visit →

What is PocketBase?

PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.

PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.

Read the full PocketBase trajectory →

What is rgm?

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

Read the full rgm trajectory →

PocketBase vs rgm: editorial side-by-side

P
PocketBase
INFRA · APIS
5.0

PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.

◆ Current state

PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.

◆ Where it's heading

This is a mature single-maintainer project in steady maintenance, prioritizing dependency hygiene and supply-chain caution over new capability. Two things are explicitly deferred to the future: proper non-zero exit code support for CLI commands, held back to v0.40 or v0.41 after a panic-recovery change was reverted, and eventually replacing ozzo-validation with a purpose-built validator. The continued 0.22 backports show a real installed base that hasn't migrated.

◆ Prediction

The deferred CLI exit-code work marks v0.40 as the next feature release rather than another patch. Expect the 0.39 and 0.22 pairing to continue until 0.22 is formally retired.

R
rgm
INFRA · APIS
0.0

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

◆ Current state

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

◆ Where it's heading

Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.

◆ Prediction

The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.

Alternatives to PocketBase and rgm

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 PocketBase or rgm.

See all PocketBase alternatives → · See all rgm alternatives →

Recent activity from PocketBase and rgm

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

  1. 5d agoPocketBaseAPI preview fixes, UI polish, and Go dependency bumps
  2. 5d agoPocketBase0.22 LTS backport of the Go dependency bumps
  3. 20d agoPocketBaseCLI panic recovery reverted to restore non-zero exit codes
  4. 20d agoPocketBase0.22 LTS backport of the CLI exit-code revert
  5. 27d agoPocketBaseFirefox bulk-select fix, goja and filter-parser updates
  6. 27d agoPocketBase0.22 LTS backport of the goja and fexpr bumps
  7. 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
  8. 3mo agorgmBack on CRAN after dropping the dependency that caused archival
  9. 3mo agorgmUnreleased twin of the CRAN recovery release
  10. 2y agorgmFirst release: simulation, estimation and post-processing

Frequently asked questions

What is the difference between PocketBase and rgm?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PocketBase 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to PocketBase?

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

What are the best alternatives to rgm?

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