epiflows
epiflows has shipped four releases in eight years, none of which changed the code.
Comparison · Analytics
EpiNow2 vs OpenCTI
A side-by-side editorial comparison of EpiNow2 and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
EpiNow2 vs OpenCTI: at a glance
What is EpiNow2?
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
What is OpenCTI?
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
The mainline is working through the consequences of the connector catalog redesign, with each release closing gaps around it: filters and saved searches became shareable, dashboards can reuse them, and background tasks can now edit relationship start and stop times in bulk. Alongside that, an LTS branch is being maintained in parallel — 7.260309.0-lts.7 backports the security fixes and dependency updates from the recent mainline releases without any of the feature work.
EpiNow2 vs OpenCTI: editorial side-by-side
EpiNow2
0.0ANALYTICS
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
◆ Current state
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
◆ Where it's heading
The package spent this window paying down interface debt and is now extending from the tidier base. Options that existed only for `estimate_infections()` have been propagated outward: `estimate_truncation()` gained the full `dist_spec` delay families, `obs_opts()` observation model selection between Poisson and negative binomial, and the `likelihood` and `return_likelihood` settings that make prior-only fits and loo-compatible output possible. Hardcoded assumptions are being replaced by specifiable ones in the same motion — the truncation model's additive noise term was a fixed `sigma ~ normal(0, 1)` prior and is now a `dist_spec` argument.
◆ Prediction
Expect the remaining modelling functions to keep converging on the shared options interface, since the last two releases have each moved another function onto it. A new `estimate_dist()` for interval-censored linelist data suggests delay estimation is the area still gaining surface.
OpenCTI
6.3ANALYTICS
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
◆ Current state
The mainline is working through the consequences of the connector catalog redesign, with each release closing gaps around it: filters and saved searches became shareable, dashboards can reuse them, and background tasks can now edit relationship start and stop times in bulk. Alongside that, an LTS branch is being maintained in parallel — 7.260309.0-lts.7 backports the security fixes and dependency updates from the recent mainline releases without any of the feature work.
◆ Where it's heading
Two things are running at once. The product arc is about making the platform's own surfaces composable — a faceted connector marketplace, reusable filters, workflow approval and draft metadata — rather than adding threat-intel primitives. The engineering arc is a maintained LTS channel that gets security parity and nothing else, which is how a project behaves once it has deployments it cannot ask to track weekly releases.
◆ Prediction
Expect the mainline to keep landing XTM Hub integration and workflow-governance work at roughly a weekly cadence, with a matching lts.8 backport following whenever the next batch of security fixes accumulates.
Alternatives to EpiNow2 and OpenCTI
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 EpiNow2 or OpenCTI.
lpjmlkit
The LPJmL toolkit finally reads NetCDF, closing a gap against the format its field uses.
survminer
survminer is back after a five-year gap, and spending it cutting dependencies loose.
stockplotr
A stock-assessment plotting package is growing a table engine to match its figures.
xts
xts is finished software, and its releases now track R's C API more than user requests.
rjwsacruncher
A thin R wrapper around a Java seasonal-adjustment tool, slowly absorbing the setup work.
See all EpiNow2 alternatives → · See all OpenCTI alternatives →
Recent activity from EpiNow2 and OpenCTI
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOpenCTILTS branch gets the security backport: access-scoped streams, dependency sweep
- 4d agoOpenCTIMass operations can now edit relation start and stop times
- 8d agoOpenCTISaved searches and dashboard filters become shareable and reusable
- 12d agoOpenCTIData sanity operations can be stopped mid-run
- 16d agoOpenCTIIntegrations experience reworked around the new catalog, plus draft approval workflows
- 24d agoOpenCTIConnector catalog is rebuilt as a faceted marketplace ⚡
- 1mo agoEpiNow2estimate_truncation gains full delay and observation options
- 6mo agoEpiNow2Unified return objects and shared accessors across all models ⚡
- 1y agoEpiNow2Patch for an upstream rstan issue
- 1y agoEpiNow2Accumulation for irregularly reported data; unified priors
- 1y agoEpiNow2Matern kernel spectral density fix and GP prior revert
- 1y agoEpiNow2Gaussian Process model improvements and explicit defaults
Frequently asked questions
What is the difference between EpiNow2 and OpenCTI?
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 EpiNow2 better than OpenCTI?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 EpiNow2?
Top EpiNow2 alternatives in Analytics are ranked by recent ship velocity. Browse the "EpiNow2 alternatives" section above for the current picks, or visit /alternatives/epinow2 for the full list with editorial commentary on each.
What are the best alternatives to OpenCTI?
Top OpenCTI alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenCTI alternatives" section above for the current picks, or visit /alternatives/opencti for the full list with editorial commentary on each.