nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
A side-by-side editorial comparison of Cosmic and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
Cosmic retired AI Studio and gave its agents goals — the CMS is becoming an agent runtime.
Six weeks of releases pull in one direction. AI Studio was retired and Cosmic's AI consolidated into three surfaces: Agents, Workflows, and Code. Agents gained goals described in plain language that they work toward on their own, running steps and checking in, plus write access to reusable rich-text Content Blocks rather than read-only reference. Semantic search embeds bucket objects into a vector index so content is retrievable by meaning. The two newest entries add Claude Opus 5 and Kimi K3 to the model lineup.
NetBox adds a cooling data model — the first new infrastructure domain since power
After a 4.6 patch cycle spent almost entirely on GraphQL query cost and permission correctness, NetBox has opened its 4.7 line with a beta that is the opposite kind of release. It introduces cooling infrastructure as a first-class modeling domain, migrates nested group models off django-mptt onto a PostgreSQL ltree column, replaces the Service protocol/ports fields with a unified port_mappings structure, and raises the floor to PostgreSQL 15 and Redis 6. The breaking-change list runs longer than most NetBox releases run in total.
Six weeks of releases pull in one direction. AI Studio was retired and Cosmic's AI consolidated into three surfaces: Agents, Workflows, and Code. Agents gained goals described in plain language that they work toward on their own, running steps and checking in, plus write access to reusable rich-text Content Blocks rather than read-only reference. Semantic search embeds bucket objects into a vector index so content is retrievable by meaning. The two newest entries add Claude Opus 5 and Kimi K3 to the model lineup.
The content API is turning into a runtime agents operate inside: goals instead of prompts, write permissions instead of suggestions, and a vector index so an agent can find what it needs without being handed it. Retiring AI Studio is the clearest signal — Cosmic is choosing fewer, deeper surfaces over a menu of separate AI features, which is a harder position to reverse.
Expect agent write scope to extend past Content Blocks to objects and media, and goals to gain triggers or schedules so they run without a person starting them.
After a 4.6 patch cycle spent almost entirely on GraphQL query cost and permission correctness, NetBox has opened its 4.7 line with a beta that is the opposite kind of release. It introduces cooling infrastructure as a first-class modeling domain, migrates nested group models off django-mptt onto a PostgreSQL ltree column, replaces the Service protocol/ports fields with a unified port_mappings structure, and raises the floor to PostgreSQL 15 and Redis 6. The breaking-change list runs longer than most NetBox releases run in total.
The cooling model is deliberately shaped as a mirror of the existing power model — CoolingSource and CoolingFeed parallel PowerPanel and PowerFeed, CoolingIntake and CoolingOutflow parallel PowerPort and PowerOutlet, with CDUs and manifolds modeled as ordinary devices carrying those components. That symmetry says NetBox intends liquid cooling to be documented with the same rigor as power distribution, not bolted on as attributes. Underneath it, the ltree migration and the deferred search-index rebuild continue the performance thread of 4.6 by other means: instead of trimming queries inside the ORM, 4.7 is changing what the ORM sits on.
Expect at least one more 4.7 beta or release candidate before general availability, with the deprecated NestedGroupModel base class and the retained protocol/ports API fields the most likely sources of follow-up fixes as plugins migrate.
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 Cosmic or NetBox.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all Cosmic alternatives → · See all NetBox alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NetBox 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NetBox 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.
Top Cosmic alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cosmic alternatives" section above for the current picks, or visit /alternatives/cosmicjs for the full list with editorial commentary on each.
Top NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox for the full list with editorial commentary on each.