← Back to home
Comparison · Analytics

epinowcast vs TimescaleDB

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

epinowcast vs TimescaleDB: at a glance

FeatureepinowcastTimescaleDB
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesr, bayesian, stan, epidemiologytime-series, postgresql, columnstore, query-optimization
Last editorial update2d ago1d 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 TimescaleDB?

TimescaleDB is paying down correctness debt in its columnstore query paths.

The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.

Read the full TimescaleDB trajectory →

epinowcast vs TimescaleDB: 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
TimescaleDB
ANALYTICS
5.0

TimescaleDB is paying down correctness debt in its columnstore query paths.

◆ Current state

The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.

◆ Where it's heading

The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.

◆ Prediction

With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.

Alternatives to epinowcast and TimescaleDB

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 TimescaleDB.

See all epinowcast alternatives → · See all TimescaleDB alternatives →

Recent activity from epinowcast and TimescaleDB

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

  1. 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
  2. 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
  3. 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
  4. 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
  5. 1mo agoepinowcastgp() brings Gaussian processes to every module, and centring doubles sampling speed
  6. 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
  7. 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
  8. 3mo agoepinowcastCRAN preparation, inspection methods, and retrospective-only fitting
  9. 7mo agoepinowcastStructural reporting patterns for non-daily reporting cycles
  10. 10mo agoepinowcastLifecycle moves to stable; pathfinder and negative binomial support
  11. 2y agoepinowcastNon-parametric reference date models and a stricter max_delay default
  12. 3y agoepinowcastFix initial conditions for cmdstan 2.32.1 compatibility

Frequently asked questions

What is the difference between epinowcast and TimescaleDB?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB 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 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 TimescaleDB?

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