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 Split.io and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
Split FME's March releases pull feature flags fully into the Harness DevOps platform.
Split.io now ships under the Harness Feature Management & Experimentation (FME) brand, and the substantive activity is captured in the rolled-up release-notes page rather than per-release entries. The March 2026 wave landed three real ships: Policy As Code (OPA) for FME Feature Flags, Feature Flag Archiving with RBAC and pre-archive checks, and the GA of FME steps in Harness pipelines covering full flag lifecycle management. The rest of the recent feed is scraper artifacts — page chrome captured as titles.
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.
Split.io now ships under the Harness Feature Management & Experimentation (FME) brand, and the substantive activity is captured in the rolled-up release-notes page rather than per-release entries. The March 2026 wave landed three real ships: Policy As Code (OPA) for FME Feature Flags, Feature Flag Archiving with RBAC and pre-archive checks, and the GA of FME steps in Harness pipelines covering full flag lifecycle management. The rest of the recent feed is scraper artifacts — page chrome captured as titles.
FME is becoming a first-class part of the Harness DevOps surface rather than a standalone feature-flag tool. Pipeline-native flag operations, policy-as-code governance, and archiving as a managed lifecycle state all reflect a single direction: feature flags as a governed, audited, and pipeline-integrated component of the deployment system. The standalone Split UX is fading into Harness conventions.
Expect more Harness-platform conventions to land on FME — RBAC unification, environments and pipelines parity, OPA policy templates shipped out of the box, and observability tying flag changes back into deploy-failure/MTTR dashboards. Standalone-Split UX surfaces will likely be retired further.
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 Split.io 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 Split.io 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 0.6), 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 0.6), 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 Split.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Split.io alternatives" section above for the current picks, or visit /alternatives/split 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.