GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Nautobot vs Knock
A side-by-side editorial comparison of Nautobot and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
Nautobot vs Knock: at a glance
| Feature | Nautobot | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | network source of truth, security advisories, breaking api changes, dual branch | notification-infrastructure, data-sources, agent-native, workflow-orchestration |
| Last editorial update | 2h ago | 11h ago |
| Website | 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.
What is Knock?
Knock is wiring both ends of the messaging data loop, then putting an agent on top
Knock has spent the last month building around its notification engine rather than inside it. Two new inbound data sources, Amplitude and Clay, let product events, cohorts, and enriched account rows land in Knock without customers writing sync code, while message and engagement events flow back out to the warehouse. The dashboard work alongside it, a rebuilt template editor, saved views and tags, schema management, and passkeys, reads as hardening for teams rather than individual developers.
Nautobot vs Knock: editorial side-by-side
Nautobot
5.0INFRA · APIS
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.
Knock
6.3INFRA · APIS
Knock is wiring both ends of the messaging data loop, then putting an agent on top
◆ Current state
Knock has spent the last month building around its notification engine rather than inside it. Two new inbound data sources, Amplitude and Clay, let product events, cohorts, and enriched account rows land in Knock without customers writing sync code, while message and engagement events flow back out to the warehouse. The dashboard work alongside it, a rebuilt template editor, saved views and tags, schema management, and passkeys, reads as hardening for teams rather than individual developers.
◆ Where it's heading
The direction is away from a notification API you call and toward the system that holds the messaging state. Ingesting cohort membership and enriched contact data is CDP-adjacent territory, and the wait-for-event function turns linear sequences into event-driven orchestration. The Knock agent then adds a natural-language layer over performance data, so the platform answers questions instead of only exporting rows.
◆ Prediction
Expect more data sources on the same pattern, warehouse and CRM-side connectors that keep audiences in sync without customer glue code. Whether the agent moves from reading analytics to editing workflows directly is the open question these entries do not yet answer.
Alternatives to Nautobot and Knock
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 Knock.
LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
Gatekeeper
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Incus
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
Firecracker
Firecracker's microVMs can now grow and shrink devices while running.
See all Nautobot alternatives → · See all Knock alternatives →
Recent activity from Nautobot and Knock
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockAmplitude data source
- 3d agoNautobotCable termination filter and GraphQL OpenTelemetry corrections
- 4d agoNautobotMany-to-many change logging and GitRepository sync permissions
- 8d agoKnockAnalytics in the Knock agent ⚡
- 9d agoKnockWait for event function
- 9d agoNautobotPublic API constants and a widened cryptography range
- 10d agoKnockClay data source
- 11d agoNautobotREST API permission enforcement on related objects; job_kwargs required
- 11d agoNautobotSecurity-driven breaking API changes on the 2.4 branch
- 14d agoNautobotDependency updates mitigating CVEs
- 15d agoKnockRedesigned template editor
- 22d agoKnockBranch rebasing
Frequently asked questions
What is the difference between Nautobot and Knock?
They serve adjacent needs but don't currently overlap on shipped themes. Knock is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
Is Nautobot better than Knock?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
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 Knock?
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.