← Back to home
Comparison · Infra & APIs

FoRecoML vs PocketBase

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

FoRecoML vs PocketBase: at a glance

FeatureFoRecoMLPocketBase
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-seriesbackend-as-a-service, go, sqlite, supply-chain
Last editorial update52m ago4d ago
WebsiteVisit →Visit →

What is FoRecoML?

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

Read the full FoRecoML trajectory →

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 →

FoRecoML vs PocketBase: editorial side-by-side

F
FoRecoML
INFRA · APIS
0.0

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

◆ Current state

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

◆ Where it's heading

This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.

◆ Prediction

With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.

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.

Alternatives to FoRecoML and PocketBase

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

See all FoRecoML alternatives → · See all PocketBase alternatives →

Recent activity from FoRecoML and PocketBase

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. 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
  8. 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
  9. 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN

Frequently asked questions

What is the difference between FoRecoML and PocketBase?

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 FoRecoML better than PocketBase?

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

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

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.