← Back to home
Comparison · Analytics

epidemics vs TimescaleDB

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

epidemics vs TimescaleDB: at a glance

FeatureepidemicsTimescaleDB
SectorAnalyticsAnalytics
Velocity score3.85.0
Sparks · 30d00
Top themesepiverse-trace, compartmental-models, odin, breaking-changestime-series, postgresql, columnstore, query-optimization
Last editorial update4d ago1d ago
WebsiteVisit →Visit →

What is epidemics?

epidemics swapped its C++ engine for odin — and quietly inverted how contact matrices must be passed.

epidemics ships composable compartmental model structures — default SEIR-V, Vacamole, diphtheria and Ebola — with classes for populations, interventions and vaccination campaigns. After more than two years without a release, 0.5.0 landed in July 2026 carrying both an engine migration and a breaking input-convention change. Maintainership moved to a new lead back in 0.4.0.

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

epidemics vs TimescaleDB: editorial side-by-side

E
epidemics
ANALYTICS
3.8

epidemics swapped its C++ engine for odin — and quietly inverted how contact matrices must be passed.

◆ Current state

epidemics ships composable compartmental model structures — default SEIR-V, Vacamole, diphtheria and Ebola — with classes for populations, interventions and vaccination campaigns. After more than two years without a release, 0.5.0 landed in July 2026 carrying both an engine migration and a breaking input-convention change. Maintainership moved to a new lead back in 0.4.0.

◆ Where it's heading

The package's history is a sequence of deliberate breaking releases: 0.2.0 renamed every model function and vectorised the ODE models, 0.3.0 restructured the Ebola model into two levels and made replicates the default, and 0.5.0 rewrites the compiled core. The direction is toward a smaller, more declarative model definition layer with the numerical work delegated to a dedicated tool.

◆ Prediction

With the default, Vacamole and diphtheria systems now declared in odin, the Ebola model is the obvious remaining candidate for the same treatment.

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

See all epidemics alternatives → · See all TimescaleDB alternatives →

Recent activity from epidemics 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 agoepidemicsODE models migrate to odin; contact matrices must no longer be transposed
  5. 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
  6. 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
  7. 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
  8. 2y agoepidemicsPeak timing and scenario comparison helpers; negative-susceptible bug fixed
  9. 2y agoepidemicsEbola model accepts vector inputs and defaults to 100 replicates
  10. 2y agoepidemicsODE models vectorised; every model function renamed
  11. 2y agoepidemicsFirst release: four composable compartmental model structures

Frequently asked questions

What is the difference between epidemics and TimescaleDB?

They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 3.8), 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 epidemics 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 3.8), 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 epidemics?

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