ESPHome
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
A side-by-side editorial comparison of Lima and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
Lima keeps widening which machines it can run on, and run.
Lima runs Linux virtual machines for container workloads, and its 2.x line has been a steady expansion of the host and guest matrix. macOS and FreeBSD guests arrived at 2.1.0, Windows Server 2025 and Windows 11 guests followed through 2.2.0, and 2.3.0-beta.0 adds an experimental HCS driver for Windows hosts along with further Windows guest work. Each platform addition lands marked experimental first, and much of the surrounding work is CLI and template maintenance.
Redocly ships a built-in MCP server page across its entire docs platform, with public and authenticated endpoints
Redocly just landed a coordinated 0.137.0 release across Reef, Realm, Revel, and Redoc, anchored by a structural addition: every developer portal now ships a `/mcp` page with setup instructions for Claude, ChatGPT/Codex, and raw JSON config, plus an opt-in `/mcp-public` endpoint for serving anonymous-accessible content without authentication. The MCP code mode got reliability improvements, OAuth discovery was fixed to spec (RFC 8414), and four CVEs were patched in the same release. The breadth of the drop — 20 features and 67+ bug fixes across packages — reflects a team that released a major capability and simultaneously cleared accumulated UX debt.
Lima runs Linux virtual machines for container workloads, and its 2.x line has been a steady expansion of the host and guest matrix. macOS and FreeBSD guests arrived at 2.1.0, Windows Server 2025 and Windows 11 guests followed through 2.2.0, and 2.3.0-beta.0 adds an experimental HCS driver for Windows hosts along with further Windows guest work. Each platform addition lands marked experimental first, and much of the surrounding work is CLI and template maintenance.
The project is converging on a single tool that runs any guest on any host, and it is doing so from both ends: guest support and host drivers advance in alternating releases. Windows is the current focus on both sides, having moved from an unsupported host default to qemu and now to a native HCS driver option. The LFX mentee contributions behind much of this suggest the platform matrix expands as contributor capacity allows rather than on a roadmap.
The HCS driver should follow the same path the other platform additions took, moving from experimental to a supported or default option on Windows hosts once the guest work stabilises around it.
Redocly just landed a coordinated 0.137.0 release across Reef, Realm, Revel, and Redoc, anchored by a structural addition: every developer portal now ships a `/mcp` page with setup instructions for Claude, ChatGPT/Codex, and raw JSON config, plus an opt-in `/mcp-public` endpoint for serving anonymous-accessible content without authentication. The MCP code mode got reliability improvements, OAuth discovery was fixed to spec (RFC 8414), and four CVEs were patched in the same release. The breadth of the drop — 20 features and 67+ bug fixes across packages — reflects a team that released a major capability and simultaneously cleared accumulated UX debt.
Redocly is repositioning every hosted API portal as a first-class AI agent resource, not just a human-readable docs site. The public MCP endpoint especially matters: it enables AI coding assistants to read API docs without credentials, which removes the main friction for developers integrating via LLM tools. Security hardening (audience validation, OAuth compliance, CVE patching) in the same release signals this isn't a prototype feature — it's going into production. The next logical step is deeper programmatic authoring via the MCP surface, not just reading.
Expect Redocly to add MCP write-path features — letting AI agents update API documentation or sync specs directly — once the read-path is fully stable. The visual review check in Reunite suggests a git-workflow integration direction.
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 Lima or Redocly.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
Expo kills its AI agent, SDK 58 beta arrives as EAS observability stack hits GA
Jackett in pure tracker-maintenance mode, daily domain and category updates only
Skipper adds Redis as a distributed L2 cache backend amid a high-frequency patch cadence.
Kubernetes v1.37 matures its memory management and scheduling stack for AI/ML workloads.
GitHub Copilot gets cost-aware inference tiers as enterprise AI tooling tightens across the platform.
See all Lima 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 2.5), 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 7.5 vs 2.5), 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 Lima alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lima alternatives" section above for the current picks, or visit /alternatives/lima 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.