tidyr
tidyr replaced separate() with a family that says what it does.
Comparison · Analytics
performance vs OpenCTI
A side-by-side editorial comparison of performance and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
performance vs OpenCTI: at a glance
What is performance?
performance keeps adding ways to check a model you have already fitted.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
What is OpenCTI?
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
performance vs OpenCTI: editorial side-by-side
performance
0.0ANALYTICS
performance keeps adding ways to check a model you have already fitted.
◆ Current state
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
◆ Where it's heading
Two consistent habits. Diagnostics keep gaining arguments to narrow what is examined — ppc_range, x_limits, maximum_dots, show_ci — which reads as a package being used on models large and awkward enough that the defaults stopped working. And simulated residuals via DHARMa keep displacing standard ones as the basis for the checks themselves.
◆ Prediction
With check_priors() newly added and Bayesian predictive checks now routed through modelbased, the next release most likely extends the Bayesian diagnostic set rather than reworking the frequentist checks.
OpenCTI
6.3ANALYTICS
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
◆ Current state
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
◆ Where it's heading
The centre of gravity is moving from OpenCTI as a self-contained platform to OpenCTI as a client of Filigran's wider ecosystem — connectors sourced from a catalog with support tiers, custom views deployed from XTM Hub, an MCP server exposed through XTM One. The workflow engine is maturing in parallel, picking up draft approval, transition restrictions and full reset. Telemetry coverage expanded significantly in the same period, which is what makes the catalog's adoption measurable.
◆ Prediction
Expect more of the platform's configuration surface — dashboards, playbooks, mappers — to become distributable through XTM Hub the way custom views and connectors already are. The workflow approval features suggest governance controls are the next area to fill in.
Alternatives to performance 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 performance or OpenCTI.
modeltime
modeltime built conformal intervals in, then went quiet on features.
cmdstanpy
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
dowhy
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all performance alternatives → · See all OpenCTI alternatives →
Recent activity from performance and OpenCTI
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoOpenCTIMass operations can now edit relation start and stop times
- 5d agoOpenCTISaved searches and dashboard filters become shareable and reusable
- 8d agoOpenCTIData sanity operations can be stopped mid-run
- 13d agoOpenCTIIntegrations experience reworked around the new catalog, plus draft approval workflows
- 21d agoOpenCTIConnector catalog is rebuilt as a faceted marketplace ⚡
- 26d agoOpenCTIFix-only release across live streams, groups and dashboard widgets
- 1mo agoperformancecheck_priors() added; overdispersion plots use simulated residuals
- 2mo agoperformance-2LL criterion column and unified Bayesian predictive checks
- 6mo agoperformanceBreaking renames plus point-count and CI controls in check_model()
- 8mo agoperformancecheck_autocorrelation() methods for DHARMa objects
- 10mo agoperformanceFixes CRAN checks after an rstanarm update
- 11mo agoperformancetinytable output format in display()
Frequently asked questions
What is the difference between performance 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 performance 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 performance?
Top performance alternatives in Analytics are ranked by recent ship velocity. Browse the "performance alternatives" section above for the current picks, or visit /alternatives/easystats-performance 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.