Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of CptNonPar and NGINX — release velocity, themes, recent moves, and the top alternatives to consider.
Nonparametric change point detection swaps p-values for importance scores.
CptNonPar implements nonparametric MOJO change point detection for possibly multivariate, serially dependent data, through single-lag, multi-lag and multiscale entry points. Recent releases concern how results are reported and how data is preprocessed rather than new detection machinery. The underlying method was accepted at Biometrika during the 0.3.0 cycle.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.
CptNonPar implements nonparametric MOJO change point detection for possibly multivariate, serially dependent data, through single-lag, multi-lag and multiscale entry points. Recent releases concern how results are reported and how data is preprocessed rather than new detection machinery. The underlying method was accepted at Biometrika during the 0.3.0 cycle.
The package is tightening the statistical interface it exposes: p-values gave way to importance scores across all three detection functions, manual thresholds became specifiable per lag, and the latest release makes centring and scaling the default preprocessing step. Each change folds a decision the user previously had to make into the package itself.
Expect further work on defaults and reporting around the existing MOJO estimators rather than a new detection method.
1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.
The five preceding releases were security releases: three CVEs in July across both branches, an HTTP/2 and gRPC buffer overflow and an HTTP/3 use-after-free in June. Against that run, 1.31.4 reads as the project returning to feature work, with F5 contributors visible across the stream and upstream changes and four first-time contributors landing fixes. The JSON and data-model libraries are the item worth watching, since general serialization is not something a proxy needs for proxying.
Those libraries have no consumer in this release, so the plausible next move is a feature that uses them, such as structured status output or configuration, rather than another round of parser hardening.
Other Infra & APIs 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 CptNonPar or NGINX.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
See all CptNonPar alternatives → · See all NGINX alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NGINX is currently shipping more aggressively (velocity 2.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NGINX is currently shipping more aggressively (velocity 2.5 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 Infra & APIs products to evaluate alongside.
Top CptNonPar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CptNonPar alternatives" section above for the current picks, or visit /alternatives/cptnonpar for the full list with editorial commentary on each.
Top NGINX alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NGINX alternatives" section above for the current picks, or visit /alternatives/nginx for the full list with editorial commentary on each.