Apache CloudStack
CloudStack's feed shows two LTS branches maintained in parallel and little else
A side-by-side editorial comparison of Icinga and ManageEngine Applications Manager — release velocity, themes, recent moves, and the top alternatives to consider.
Icinga 2 is fixing the same API permission holes across every supported branch.
Icinga 2 ships security fixes as simultaneous releases across its 2.14, 2.15, and 2.16 branches, and has now done so twice in five weeks. The 18 August pair - v2.16.5 and v2.15.6, tagged 25 seconds apart - closes an events/* permission bypass on /v1/events and a memory-exhaustion path where a node could crash another using the 1 GB message limit, now capped at 16 MiB for messages from lower in the hierarchy. v2.16.5 additionally repairs an IcingaDB regression introduced in v2.16.0.
Applications Manager pushes monitoring past the server and out to the end user's network path
Applications Manager ships on a roughly fortnightly build cadence, and each build arrives split across three feed entries — new features, minor enhancements, and issues fixed. Build 182000 adds ISP Latency Monitoring, measuring the network path between EUM agent locations and target hosts. The accompanying enhancements are runtime upgrades (JRE 11 to 17, PostgreSQL 15 to 17, Tomcat), and the fix list is dominated by Oracle monitoring and SSL connection problems.
Read the full ManageEngine Applications Manager trajectory →
Icinga 2 ships security fixes as simultaneous releases across its 2.14, 2.15, and 2.16 branches, and has now done so twice in five weeks. The 18 August pair - v2.16.5 and v2.15.6, tagged 25 seconds apart - closes an events/* permission bypass on /v1/events and a memory-exhaustion path where a node could crash another using the 1 GB message limit, now capped at 16 MiB for messages from lower in the hierarchy. v2.16.5 additionally repairs an IcingaDB regression introduced in v2.16.0.
The recurring theme is that the API's filter and permission model was more permissive than intended. July's critical release introduced a filter-expression permission so DSL filters in API queries can be restricted per user, with enforcement deliberately deferred to v2.17; August's pair fixes filter expressions on /v1/events not being permission-checked at all. Cluster message handling is being tightened in parallel. The project is clearly working through an audit of the API surface, and it is backporting every finding rather than pushing users onto the newest branch.
Enforcement of the filter-expression permission is already scheduled for v2.17, so that release should be the one where the opt-in restrictions become mandatory - expect more backported API permission fixes across all three branches before it lands.
Applications Manager ships on a roughly fortnightly build cadence, and each build arrives split across three feed entries — new features, minor enhancements, and issues fixed. Build 182000 adds ISP Latency Monitoring, measuring the network path between EUM agent locations and target hosts. The accompanying enhancements are runtime upgrades (JRE 11 to 17, PostgreSQL 15 to 17, Tomcat), and the fix list is dominated by Oracle monitoring and SSL connection problems.
The recent builds trace a move from monitoring what a server reports to monitoring what a user experiences: ISP latency here, Capacity Planning widgets that flag idle and undersized resources in the previous build, Emergency Patching before that. The platform underneath is being modernised at the same time — this build alone jumps a major JRE version and two PostgreSQL majors. Oracle monitoring remains the most frequent source of defects across the fix lists.
Expect the end-user-experience surface to keep expanding around the EUM agent, and further platform version bumps as the JRE 17 migration settles.
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 Icinga or ManageEngine Applications Manager.
CloudStack's feed shows two LTS branches maintained in parallel and little else
ToolJet's LTS and beta trains both narrow to component polish and CVE patching
missSBM returns after four dormant years with a stricter API and a new refinement step.
Luminescence is revisiting the statistical assumptions baked into its dose-response fits.
sps keeps sanding down sequential Poisson sampling rather than adding to it.
simDAG grew a second simulation engine, then spent two releases surviving upstream breakage.
See all Icinga alternatives → · See all ManageEngine Applications Manager alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Icinga and ManageEngine Applications Manager are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Icinga and ManageEngine Applications Manager are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Icinga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Icinga alternatives" section above for the current picks, or visit /alternatives/icinga for the full list with editorial commentary on each.
Top ManageEngine Applications Manager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ManageEngine Applications Manager alternatives" section above for the current picks, or visit /alternatives/manageengine-applications-manager for the full list with editorial commentary on each.