Nautobot
Nautobot 3.3 alpha adds API rate limits while 3.2.9 stops cross-user token reads.
A side-by-side editorial comparison of kOps and Redocly — release velocity, themes, recent moves, and the top alternatives to consider.
kOps deletes gossip DNS and the protokube binary, and spends the room on Akamai.
kOps publishes alpha and beta tags to this feed rather than finals, and 1.37.0-beta.1 is the largest cut in its visible history. Gossip DNS is gone, along with the protokube binary that served it, Classic Load Balancer support for the API, and Kubernetes 1.31. In the same tag Akamai — renamed from Linode across the codebase — grows from SSH-key handling into a provider with its own network model, subnets, instance management and etcd block storage volumes.
Redocly fixes API reference pages that broke on custom hooks across five packages.
Redocly's past week was fixes. On November 9 five packages shipped the same fix for API reference pages that showed an Unknown hook error instead of docs, plus a Try it console that now asks for a reload after a redeploy. Platform releases fixed editor hangs on large repos, rejected organization names that look like card numbers, and stopped redocly push reporting success on blocked publishes. Config 0.72.1 adds triggers and rules to the docs agent's support-conversation duty.
kOps publishes alpha and beta tags to this feed rather than finals, and 1.37.0-beta.1 is the largest cut in its visible history. Gossip DNS is gone, along with the protokube binary that served it, Classic Load Balancer support for the API, and Kubernetes 1.31. In the same tag Akamai — renamed from Linode across the codebase — grows from SSH-key handling into a provider with its own network model, subnets, instance management and etcd block storage volumes.
The deliberate narrowing this feed has shown since 1.36 has stopped being incremental. Removing gossip means every cluster now needs real DNS, which ends the configuration that let kOps stand up clusters without a hosted zone. The room that deletion frees is going two visible places: a genuinely new cloud provider in Akamai, and a smaller binary, via grpcnotrace, a forked text/template that lets the linker prune, and a minimal TOML writer replacing go-toml.
Akamai moved from SSH keys to subnets, instances and etcd volumes inside a single tag, so it is the provider most likely to keep gaining tasks next. With a gossip migration guide already written, the remaining 1.37 work is the removal reaching users rather than more subtraction.
Redocly's past week was fixes. On November 9 five packages shipped the same fix for API reference pages that showed an Unknown hook error instead of docs, plus a Try it console that now asks for a reload after a redeploy. Platform releases fixed editor hangs on large repos, rejected organization names that look like card numbers, and stopped redocly push reporting success on blocked publishes. Config 0.72.1 adds triggers and rules to the docs agent's support-conversation duty.
After the Markdoc fork and docs agent changes on November 3 and 4, Redocly is in stabilization. The agent work continues in config, where the support-conversation duty can now run on a schedule against a Front desk.
Expect more docs agent duties and options in config, and further fix batches as the Markdoc fork settles.
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 kOps or Redocly.
Nautobot 3.3 alpha adds API rate limits while 3.2.9 stops cross-user token reads.
SpinupWP now writes DNS records for you, starting with Cloudflare and Route 53.
One Node.js Brotli bug and a compromised CA bundle force ten patches across the Elastic Stack.
OpenMQTTGateway returns after 22 months with a security-first 1.9.0.
Parse Server 9.11.1 alphas close two beforeSave advisories, one a server crash.
GitLab sells Orbit as the evidence layer for agent pilots and AI-code rules.
See all kOps 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 6.3 vs 3.8), 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 6.3 vs 3.8), 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 kOps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "kOps alternatives" section above for the current picks, or visit /alternatives/kops 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.