Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of epidemics and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
With the default, Vacamole and diphtheria systems now declared in odin, the Ebola model is the obvious remaining candidate for the same treatment.
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.
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.
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.
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.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all epidemics alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
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.