← Back to home
Comparison · Infra & APIs

Nautobot vs Incus

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

Nautobot vs Incus: at a glance

FeatureNautobotIncus
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themesnetwork source of truth, security advisories, breaking api changes, dual branchcontainer manager, lts branch, live migration, qemu gating
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is Nautobot?

A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.

3.2.0 and 2.4.38 shipped the same day in late July carrying CVE fixes that the notes state introduce breaking changes, most often surfacing as unexpected TypeError, AttributeError or KeyError for REST and GraphQL clients. The central change, from advisory GHSA-h8rv-c7c8-cvmx, is that the REST API now enforces object-level view permissions when traversing to related objects via ?depth — beyond depth 1 a related object the caller cannot view is reduced to id, object_type, url and display instead of being serialised in full. 3.2.0 also makes job_kwargs required for create_schedule, enqueue_job, execute_job and run_job_for_testing, with a temporary fallback that warns. 3.1.8 closed an authorization bypass letting a user self-approve a workflow, and 2.4.37 fixed stored XSS in Relationship and Module Family fields.

Read the full Nautobot trajectory →

What is Incus?

Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.

7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.

Read the full Incus trajectory →

Nautobot vs Incus: editorial side-by-side

N
Nautobot
INFRA · APIS
5.0

A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.

◆ Current state

3.2.0 and 2.4.38 shipped the same day in late July carrying CVE fixes that the notes state introduce breaking changes, most often surfacing as unexpected TypeError, AttributeError or KeyError for REST and GraphQL clients. The central change, from advisory GHSA-h8rv-c7c8-cvmx, is that the REST API now enforces object-level view permissions when traversing to related objects via ?depth — beyond depth 1 a related object the caller cannot view is reduced to id, object_type, url and display instead of being serialised in full. 3.2.0 also makes job_kwargs required for create_schedule, enqueue_job, execute_job and run_job_for_testing, with a temporary fallback that warns. 3.1.8 closed an authorization bypass letting a user self-approve a workflow, and 2.4.37 fixed stored XSS in Relationship and Module Family fields.

◆ Where it's heading

Nautobot is running two supported lines in parallel and treating them as equals: 3.2.2 and 2.4.39 both shipped on 3 August with the same many-to-many change-logging fix. The security work in this window is not incidental — the advisories cluster around authorization boundaries that the API had been permissive about, and closing them meant accepting a compatibility break rather than preserving behaviour. The documentation change acknowledging that managing a Git repository grants arbitrary code execution on the worker is the same instinct applied to expectations rather than code.

◆ Prediction

The job_kwargs fallback is explicitly temporary and warns when used, so its removal in a later release is the stated next step. Expect the paired 2.4.z and 3.x releases to continue landing together.

I
Incus
INFRA · APIS
5.0

Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.

◆ Current state

7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.

◆ Where it's heading

The rhythm is a monthly feature release running alongside a long-term branch, and the recent work leans toward reach rather than new primitives: clients built natively for Windows and macOS, translations updated in nearly every release, feature gating so the same daemon behaves correctly across host configurations. Stateful migration getting migration-compatible CPU flags is the most operationally significant item, since it is what makes live migration work across non-identical hosts.

◆ Prediction

The cadence in this window is a feature release roughly every four to six weeks with LTS patches interleaved, so a 7.4 is the expected next step. The entries give no indication of a headline feature queued for it.

Alternatives to Nautobot and Incus

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

See all Nautobot alternatives → · See all Incus alternatives →

Recent activity from Nautobot and Incus

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

  1. 3d agoNautobotCable termination filter and GraphQL OpenTelemetry corrections
  2. 4d agoNautobotMany-to-many change logging and GitRepository sync permissions
  3. 7d agoIncusNative Windows and macOS installers; QMP command timeouts
  4. 9d agoNautobotPublic API constants and a widened cryptography range
  5. 11d agoNautobotREST API permission enforcement on related objects; job_kwargs required
  6. 11d agoNautobotSecurity-driven breaking API changes on the 2.4 branch
  7. 14d agoNautobotDependency updates mitigating CVEs
  8. 27d agoIncusFirst patch release on the 7.0 LTS branch
  9. 1mo agoIncusMigration-compatible hypervisor flags for stateful migration
  10. 2mo agoIncusFixes for issues surfaced by the 7.0 release
  11. 3mo agoIncusIncus 7.0 LTS, with runtime-detected QEMU feature gating
  12. 4mo agoIncusVolume snapshots while attached; OVN dhcp gateway option

Frequently asked questions

What is the difference between Nautobot and Incus?

They serve adjacent needs but don't currently overlap on shipped themes. Nautobot and Incus are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Nautobot better than Incus?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nautobot and Incus are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Nautobot?

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

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.