← Back to home
Comparison · Analytics

epinowcast vs tibblify

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

Shared themes:r

epinowcast vs tibblify: at a glance

Featureepinowcasttibblify
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr, bayesian, stan, epidemiologyr, json, data rectangling, openapi
Last editorial update27m ago27m ago
WebsiteVisit →Visit →

What is epinowcast?

epinowcast added Gaussian processes to its formula interface and made the sampler twice as fast

epinowcast is a Bayesian nowcasting toolkit for right-truncated epidemiological count data, built on Stan with a brms-style formula interface. Over 2025-2026 it moved from experimental to stable, prepared for CRAN, and broadened past nowcasting proper — 0.6.0's max_delay = 1 support allows purely retrospective fitting of fully reported counts. 0.7.0 in July 2026 is the largest modelling release in the window.

Read the full epinowcast trajectory →

What is tibblify?

tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most

tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.

Read the full tibblify trajectory →

epinowcast vs tibblify: editorial side-by-side

E
epinowcast
ANALYTICS
0.0

epinowcast added Gaussian processes to its formula interface and made the sampler twice as fast

◆ Current state

epinowcast is a Bayesian nowcasting toolkit for right-truncated epidemiological count data, built on Stan with a brms-style formula interface. Over 2025-2026 it moved from experimental to stable, prepared for CRAN, and broadened past nowcasting proper — 0.6.0's max_delay = 1 support allows purely retrospective fitting of fully reported counts. 0.7.0 in July 2026 is the largest modelling release in the window.

◆ Where it's heading

The package is converging on a general formula-driven latent process toolkit rather than a single nowcasting model. rw() and arima() were joined in 0.7.0 by gp(), a Hilbert-space reduced-rank Gaussian process placeable on any module's linear predictor with selectable kernels and an integration order matching arima()'s d. Alongside it, the fixed-effects design and integrated residuals are now centred against the module intercept, which the notes report roughly doubles sampling speed on a weekly random-walk growth model.

◆ Prediction

With CRAN preparation done in 0.6.0 and the model surface substantially widened in 0.7.0, the next release is likely a CRAN submission plus consolidation of the gp() kernels. The release notes repeatedly benchmark against EpiNow2's behaviour, suggesting continued convergence between the two codebases.

T
tibblify
ANALYTICS
0.0

tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most

◆ Current state

tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.

◆ Where it's heading

The arc runs from 'write a spec by hand' toward 'the spec comes from somewhere else'. Alongside the OpenAPI importer, guess_tspec() gained exported variants so users can override its dispatch, and untibblify() now picks up the tib_spec attribute automatically. 0.4.0's breaking change prefixes all arguments of dot-accepting functions with a period to avoid collisions with column names, softened by a once-per-session deprecation warning, and refactors the entire codebase.

◆ Prediction

The un-dotted argument forms are explicitly slated for removal, so the next release most likely completes that deprecation. Whether the 0.4.0 refactor introduced corner-case regressions is the open question the release notes themselves raise.

Alternatives to epinowcast and tibblify

Other Analytics 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 epinowcast or tibblify.

See all epinowcast alternatives → · See all tibblify alternatives →

Recent activity from epinowcast and tibblify

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

  1. 1mo agoepinowcastgp() brings Gaussian processes to every module, and centring doubles sampling speed
  2. 3mo agotibblifyFix type mismatch in C code
  3. 3mo agotibblifyDot-prefixed arguments and a full internal refactor
  4. 3mo agoepinowcastCRAN preparation, inspection methods, and retrospective-only fitting
  5. 7mo agoepinowcastStructural reporting patterns for non-daily reporting cycles
  6. 10mo agoepinowcastLifecycle moves to stable; pathfinder and negative binomial support
  7. 2y agoepinowcastNon-parametric reference date models and a stricter max_delay default
  8. 2y agotibblifyparse_openapi_spec() generates tibblify specs from API documentation
  9. 3y agoepinowcastFix initial conditions for cmdstan 2.32.1 compatibility
  10. 3y agotibblifyRecursive specs, transform control and memory fixes
  11. 4y agotibblifyEngine rewritten in C with a renamed specification API

Frequently asked questions

What is the difference between epinowcast and tibblify?

Both compete on the same themes — r — within Analytics. epinowcast and tibblify are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is epinowcast better than tibblify?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epinowcast and tibblify are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to epinowcast?

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

What are the best alternatives to tibblify?

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