OpenStatus
OpenStatus scopes API keys per resource and lets its MCP server set up monitors.
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
The controller remains on the 3.2 patch line. Since v3.2.14 the only release of substance is v3.2.15, which stopped filtering ingresses on IngressClass name at ingestion, reworked status publishing and moved to Go 1.27. Later patches are mainly dependency and tooling updates, with v3.2.18 keeping every TLS secret of an ingress on the same host and v3.2.19 fixing a data race on the reload flag.
Read the full HAProxy Kubernetes Ingress Controller trajectory →
Redocly forks Markdoc and points Open in Claude at the desktop app.
Redocly's November 4 package release moved its docs stack to @redocly/markdoc, its own fork of Markdoc, with existing custom tags still working. The same release renders GitHub alert syntax as admonitions, sends Open in Claude to a Claude Code session in the desktop app, adds enum menus to the Try it console, and fixes mock servers that leaked earlier responses. The day before, config 0.71.0 made the docs agent opt-out.
The controller remains on the 3.2 patch line. Since v3.2.14 the only release of substance is v3.2.15, which stopped filtering ingresses on IngressClass name at ingestion, reworked status publishing and moved to Go 1.27. Later patches are mainly dependency and tooling updates, with v3.2.18 keeping every TLS secret of an ingress on the same host and v3.2.19 fixing a data race on the reload flag.
The ssl-passthrough theme has faded, and the series is now closer to routine upkeep than stabilization. Fixes have moved to ingress class handling, TLS secret storage and concurrency, with test coverage arriving in the same changes. Patches keep coming, but no new configuration surface has appeared on this line in the entries shown, apart from amending the SSL frontend through a custom resource in v3.2.15.
Expect further patches dominated by go.mod and Kubernetes client updates, with new capability waiting for a later line.
Redocly's November 4 package release moved its docs stack to @redocly/markdoc, its own fork of Markdoc, with existing custom tags still working. The same release renders GitHub alert syntax as admonitions, sends Open in Claude to a Claude Code session in the desktop app, adds enum menus to the Try it console, and fixes mock servers that leaked earlier responses. The day before, config 0.71.0 made the docs agent opt-out.
Redocly is taking more of its stack in-house and renaming it around one platform: Reunite options become platform, mcp.docs folds into mcp, and Markdoc is now a fork. The AI hooks point at the desktop agents rather than web chats, which fits the opt-out docs agent shipped a day earlier.
Expect the deprecated reunite and mcp.docs names to become errors in a later config release, and more Markdoc tags only Redocly's fork supports.
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 HAProxy Kubernetes Ingress Controller or Redocly.
OpenStatus scopes API keys per resource and lets its MCP server set up monitors.
Hoppscotch adds an enterprise cloud tier and an AI assistant, then turns to desktop trust.
Grype keeps tightening match accuracy while making its database diff tool usable at scale
AdGuard Home's 1.0 beta matches stable's security fixes and reworks client settings
Snort 3.13.2 is a broad bounds-checking sweep across SMB, HTTP and industrial protocol parsers
DNSimple's origin name servers answer a quarter faster at p90 after erldns work
See all HAProxy Kubernetes Ingress Controller 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 6.3 vs 5.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. Redocly is currently shipping more aggressively (velocity 6.3 vs 5.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 HAProxy Kubernetes Ingress Controller alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HAProxy Kubernetes Ingress Controller alternatives" section above for the current picks, or visit /alternatives/haproxy-ingress 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.