Authelia
Authelia ships weekly OIDC patches as v4.39 works through a long conformance backlog
A side-by-side editorial comparison of Icinga and Redocly — 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.
Redocly ships full MCP server infrastructure—API docs are now directly AI-queryable
The 0.137.0 release across Redocly's package family ships a complete MCP server integration: a /mcp setup page with tabbed configuration guides for Claude, ChatGPT, and Codex; an optional /mcp-public endpoint for unauthenticated access on RBAC-restricted projects; OAuth 2.0 credential flows with bearer token audience validation; and RFC 8414-conformant authorization server metadata. The Replay API client also gained environment management via ReplayGate and a path-parameter shortcut.
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.
The 0.137.0 release across Redocly's package family ships a complete MCP server integration: a /mcp setup page with tabbed configuration guides for Claude, ChatGPT, and Codex; an optional /mcp-public endpoint for unauthenticated access on RBAC-restricted projects; OAuth 2.0 credential flows with bearer token audience validation; and RFC 8414-conformant authorization server metadata. The Replay API client also gained environment management via ReplayGate and a path-parameter shortcut.
Redocly is positioning its documentation platform as an MCP-native layer for AI agents—a meaningful bet that API docs will be queried by agents as often as by humans. The volume of MCP fixes in this release (OAuth discovery, credential management, code mode reliability, proxy handling, connection protocol compatibility) suggests the feature shipped before it was fully hardened, and the team is iterating toward stability. The /mcp-public endpoint is particularly notable: it signals that Redocly is thinking about public API discoverability for agents, not just internal tooling.
The next release will close remaining MCP agent-mode edge cases and likely extend the MCP tool surface to cover more endpoint types or finer-grained RBAC on docs content. Expect competitor API documentation platforms to ship comparable MCP endpoints within the next few months.
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 Redocly.
Authelia ships weekly OIDC patches as v4.39 works through a long conformance backlog
Jackett ships daily indexer maintenance at a consistent one-release-per-day cadence.
Kubernetes v1.37 promotes gang scheduling to Beta, closing the gap with dedicated ML schedulers.
Resend ships SSO and enters the enterprise conversation as its product surface broadens.
CircleCI ships an MCP server and auto-rollback deployments, moving well past pure CI.
GitHub Copilot splits into cost tiers and deepens agentic automation across the dev stack
See all Icinga alternatives → · See all Redocly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Redocly is currently shipping more aggressively (velocity 7.5 vs 5.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. Redocly is currently shipping more aggressively (velocity 7.5 vs 5.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 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 Redocly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Redocly alternatives" section above for the current picks, or visit /alternatives/redocly for the full list with editorial commentary on each.