Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of etn and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
etn stopped being an RStudio-server package and became something you can run anywhere.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
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.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
Two arcs run in parallel: widening access, and making room for non-acoustic data. The access work has been deliberate — an API-backed beta in 2024, then a stable release that picks the transport automatically and checks that a local etnservice install matches the deployed one, because the same query returning different results by transport would be worse than requiring the server. The Darwin Core export added in 2.1.0 points the same outward direction, moving data to OBIS and GBIF instead of keeping it in the ETN silo.
The cpod scope named in the 2.0.0 notes is the most likely next addition, now that the naming and the API transport are both in place to carry it.
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.
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.
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.
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 etn or OpenCTI.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top etn alternatives in Analytics are ranked by recent ship velocity. Browse the "etn alternatives" section above for the current picks, or visit /alternatives/etn-r for the full list with editorial commentary on each.
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.