Thanos
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
A side-by-side editorial comparison of MISP and Apereo CAS — release velocity, themes, recent moves, and the top alternatives to consider.
MISP extends instance-to-instance sync to collections while a security-hardening program runs underneath
MISP is shipping on a roughly two-week cadence, and three tracks run through every release. The first is federation: 2.5.43 added collection synchronisation between instances in both pull and push directions, with per-server toggles and feature negotiation. The second is a sustained security program — 2.5.40, 2.5.41 and 2.5.42 are all substantially security releases, with 2.5.42 alone closing two RCE vectors and a mass-assignment sweep across a 74-controller review. The third is the Overmind UI migration to Bootstrap 5, which lands a batch of converted views in nearly every release.
CAS 8.0 is six release candidates deep with notes that describe nothing
Apereo CAS is working through a long v8.0.0 release-candidate series, reaching RC6 by late June 2026. The candidates are published with a fixed template — links to release notes, documentation, commit log and policies, plus contributor thanks — and no description of what each one changed, so the substance of the 8.0 cycle is not readable from the releases themselves. The one entry with real content is v7.3.7.1, a patch pointing at a published OIDC vulnerability advisory.
MISP is shipping on a roughly two-week cadence, and three tracks run through every release. The first is federation: 2.5.43 added collection synchronisation between instances in both pull and push directions, with per-server toggles and feature negotiation. The second is a sustained security program — 2.5.40, 2.5.41 and 2.5.42 are all substantially security releases, with 2.5.42 alone closing two RCE vectors and a mass-assignment sweep across a 74-controller review. The third is the Overmind UI migration to Bootstrap 5, which lands a batch of converted views in nearly every release.
The security work reads as a deliberate audit rather than incident response — the fixes are systematic (mass-assignment and broken-access-control across the controller layer, OIDC hardening, ACL enforcement on cluster search) and credited to named external researchers across four consecutive releases. Alongside it, the interop surface keeps widening: TAXII 2 conformance and scheduled push, STIX moved onto the upstream misp-stix library, and now collection sync. The Overmind migration is the slow constant, converting the UI tab by tab rather than in one cutover.
The Overmind migration and the Pivotick pivot explorer are both mid-rollout, so the next releases should continue converting views and fill out Pivotick rather than open a new track. Given the pattern of the last four releases, expect further externally-reported security fixes to ship alongside them.
Apereo CAS is working through a long v8.0.0 release-candidate series, reaching RC6 by late June 2026. The candidates are published with a fixed template — links to release notes, documentation, commit log and policies, plus contributor thanks — and no description of what each one changed, so the substance of the 8.0 cycle is not readable from the releases themselves. The one entry with real content is v7.3.7.1, a patch pointing at a published OIDC vulnerability advisory.
The observable pattern is a maintained v7 line receiving security patches while v8 advances through candidates at roughly monthly intervals with a small, stable set of contributors. Beyond that, the release notes are too thin to establish what 8.0 changes for operators, which matters for an identity product where upgrade planning depends on knowing exactly what moved.
Expect the RC series to continue at a monthly cadence toward an 8.0 release, and the v7 line to keep receiving security patches; what 8.0 actually delivers cannot be predicted from these entries.
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 MISP or Apereo CAS.
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
webpack is absorbing its own loader ecosystem — TypeScript, CSS and HTML now build natively.
LibreELEC's changelog stops dead at the 12.0 release in May 2024
Node-RED 5.0 rebuilt the editor, and the patches since are settling it in
Jaeger folds its MCP server into the query service and drops Elasticsearch 6
Biome's patch train is really a type-aware linting project in disguise
See all MISP alternatives → · See all Apereo CAS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. MISP 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. MISP 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 Infra & APIs products to evaluate alongside.
Top MISP alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "MISP alternatives" section above for the current picks, or visit /alternatives/misp for the full list with editorial commentary on each.
Top Apereo CAS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apereo CAS alternatives" section above for the current picks, or visit /alternatives/apereo-cas for the full list with editorial commentary on each.