← Back to home
Comparison · Infra & APIs

Incus vs Redocly

A side-by-side editorial comparison of Incus and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.

Incus vs Redocly: at a glance

FeatureIncusRedocly
SectorInfra & APIsInfra & APIs
Velocity score6.37.5
Sparks · 30d10
Top themescontainer manager, near-live migration, secure boot, nvramapi-docs, mcp, developer-portal, ai-native
Last editorial update23d ago3d ago
WebsiteVisit →Visit →

What is Incus?

Incus 7.4 turns a year of migration plumbing into near-live migration that actually moves disks.

7.0.0 LTS became the supported baseline in May with 7.0.1 as its first patch, while the feature branch kept a roughly monthly cadence: 7.1 cleaned up issues the LTS surfaced, 7.2 added migration-compatible hypervisor flags for stateful migration, 7.3 shipped native Windows and macOS installers. 7.4 is the largest of them and the first with a headline capability — near-live migration implemented on both client and server, extended to dependent disks inside a cluster, with incremental memory migration made opt-in. Alongside it sit Secure Boot key management, a substantial NVRAM rework, librbd for all Ceph interactions, and disk and NIC burst limits.

Read the full Incus trajectory →

What is Redocly?

Redocly ships MCP servers across its entire doc portal stack, making any hosted API docs directly queryable by AI agents.

The September 15 coordinated 0.137.0 release across Reef, Realm, Redoc, and the async API plugin was the centrepiece: every Redocly-hosted portal now ships with a /mcp endpoint, tabbed setup instructions for Claude and ChatGPT/Codex, an optional /mcp-public path for RBAC-restricted content, OAuth discovery per RFC 8414, and audience-validated bearer tokens. The MCP code mode was hardened to reduce agent script failures and produce cleaner error messages. Reunite (the CI/PR platform layer) is simultaneously shipping at higher frequency — multiple intra-day releases — with PR diff summaries and feedback origin filtering now live.

Read the full Redocly trajectory →

Incus vs Redocly: editorial side-by-side

I
Incus
INFRA · APIS
6.3

Incus 7.4 turns a year of migration plumbing into near-live migration that actually moves disks.

◆ Current state

7.0.0 LTS became the supported baseline in May with 7.0.1 as its first patch, while the feature branch kept a roughly monthly cadence: 7.1 cleaned up issues the LTS surfaced, 7.2 added migration-compatible hypervisor flags for stateful migration, 7.3 shipped native Windows and macOS installers. 7.4 is the largest of them and the first with a headline capability — near-live migration implemented on both client and server, extended to dependent disks inside a cluster, with incremental memory migration made opt-in. Alongside it sit Secure Boot key management, a substantial NVRAM rework, librbd for all Ceph interactions, and disk and NIC burst limits.

◆ Where it's heading

Migration has been the through-line for three releases and 7.4 is where it becomes a feature rather than plumbing. The pattern is consistent: 7.2 made stateful migration survive non-identical hosts, 7.4 makes moving an instance cheap enough to do routinely, including the storage that hangs off it. Around that, the VM side is maturing toward parity with commercial hypervisors — firmware key management, NVRAM control, per-device rate limits — which is the surface that decides whether Incus is usable as a datacentre hypervisor rather than a container manager that also runs VMs.

◆ Prediction

Expect the next release to harden near-live migration rather than replace it — the evacuation and cluster-recovery fixes already threaded through 7.4 suggest the gaps are in cluster-wide orchestration, not the transfer itself.

R
Redocly
INFRA · APIS
7.5

Redocly ships MCP servers across its entire doc portal stack, making any hosted API docs directly queryable by AI agents.

◆ Current state

The September 15 coordinated 0.137.0 release across Reef, Realm, Redoc, and the async API plugin was the centrepiece: every Redocly-hosted portal now ships with a /mcp endpoint, tabbed setup instructions for Claude and ChatGPT/Codex, an optional /mcp-public path for RBAC-restricted content, OAuth discovery per RFC 8414, and audience-validated bearer tokens. The MCP code mode was hardened to reduce agent script failures and produce cleaner error messages. Reunite (the CI/PR platform layer) is simultaneously shipping at higher frequency — multiple intra-day releases — with PR diff summaries and feedback origin filtering now live.

◆ Where it's heading

Redocly is repositioning its doc portals from human-readable API references to AI-addressable knowledge bases. The depth of the MCP implementation (public/private endpoint split, OAuth, credential validation, code mode, feedback filtering by MCP source) indicates this is a strategic capability, not an experiment. Reunite's fast cadence suggests the CI layer is being tightened to support AI-driven review and deploy workflows.

◆ Prediction

The next likely additions to the MCP surface: agent write tools (create/update docs programmatically) and analytics on which endpoints agents query most. Reunite will close the loop by letting MCP-sourced feedback trigger doc update PRs.

Alternatives to Incus and Redocly

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 Incus or Redocly.

See all Incus alternatives → · See all Redocly alternatives →

Recent activity from Incus and Redocly

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoRedoclyReunite v2026-09-17.5
  2. 4d agoRedoclyReunite v2026-09-17.4
  3. 5d agoRedoclyReunite v2026-09-16.1
  4. 6d agoRedoclyReunite v2026-09-15.2
  5. 6d agoRedocly@redocly/theme 0.69.0
  6. 6d agoRedocly@redocly/api-docs 0.2.0
  7. 24d agoIncusIncus 7.4 adds near-live migration and Secure Boot key management
  8. 1mo agoIncusNative Windows and macOS installers; QMP command timeouts
  9. 2mo agoIncusFirst patch release on the 7.0 LTS branch
  10. 2mo agoIncusMigration-compatible hypervisor flags for stateful migration
  11. 3mo agoIncusFixes for issues surfaced by the 7.0 release
  12. 4mo agoIncusIncus 7.0 LTS, with runtime-detected QEMU feature gating

Frequently asked questions

What is the difference between Incus and Redocly?

They serve adjacent needs but don't currently overlap on shipped themes. Redocly is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Incus better than Redocly?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Redocly is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Incus?

Top Incus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Incus alternatives" section above for the current picks, or visit /alternatives/incus for the full list with editorial commentary on each.

What are the best alternatives to Redocly?

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.