← Back to home
Comparison · Infra & APIs

NetBox vs rgm

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

NetBox vs rgm: at a glance

FeatureNetBoxrgm
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d10
Top themesdcim, cooling, liquid-cooling, breaking-changesmicrobiome, graphical-models, bayesian-inference, cran-maintenance
Last editorial update10h ago1h ago
WebsiteVisit →Visit →

What is NetBox?

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.

Read the full NetBox trajectory →

What is rgm?

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

Read the full rgm trajectory →

NetBox vs rgm: editorial side-by-side

N
NetBox
INFRA · APIS
6.3

NetBox adds a cooling data model — the first new infrastructure domain since power

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

R
rgm
INFRA · APIS
0.0

A microbiome network model that got itself un-archived by deleting the dependency that killed it.

◆ Current state

rgm implements the random graphical model for microbiome interactions across related environments, published in JABES in 2026. The package was archived from CRAN in February 2026 because of its dependency on huge; the recovery release drops that dependency entirely, which cost it the graphical-lasso warm start that used to seed the initial graph — the default is now an empty graph, with warm starts left to the user. A post-processing function returning ggplot diagnostics arrived in the same release.

◆ Where it's heading

Three tags shipped inside two hours on one day, and the notes are candid about why: 1.1.0 held the actual work but was never released, 1.2.0 restated it under a higher version to signal the size of the change, and 1.2.1 answered CRAN pre-test feedback. Beyond the archival recovery, the visible work is housekeeping that had accumulated — a shadowed rmvnorm() definition, roxygen import tags that were silently emitting nothing, leftover C++ template scaffolding, and build artifacts under version control. The diagnostics function is the only genuinely new user-facing capability in the window.

◆ Prediction

The immediate task was restoring availability, and that is done; the open question the entries raise is whether losing the graphical-lasso warm start affects convergence in practice, which the new diagnostic plots are positioned to answer.

Alternatives to NetBox and rgm

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 NetBox or rgm.

See all NetBox alternatives → · See all rgm alternatives →

Recent activity from NetBox and rgm

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

  1. 1d agoNetBoxNetBox 4.7 beta models cooling plant the way it models power
  2. 8d agoNetBoxGraphQL N+1 fixes and permission corrections in 4.6.8
  3. 15d agoNetBox4.6.8 release candidate refreshes translation strings
  4. 19d agoNetBox4.6.7 trims GraphQL and scope-rebuild query overhead
  5. 21d agoNetBoxCluster-scoped VLANs, tag "any" lookup, audit-trail hardening
  6. 1mo agoNetBoxMDC connectors, script-module REST updates, Korean support
  7. 3mo agorgmJournal DOI replaces the preprint; promotional wording removed
  8. 3mo agorgmBack on CRAN after dropping the dependency that caused archival
  9. 3mo agorgmUnreleased twin of the CRAN recovery release
  10. 2y agorgmFirst release: simulation, estimation and post-processing

Frequently asked questions

What is the difference between NetBox and rgm?

They serve adjacent needs but don't currently overlap on shipped themes. NetBox is currently shipping more aggressively (velocity 6.3 vs 0.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 NetBox better than rgm?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NetBox is currently shipping more aggressively (velocity 6.3 vs 0.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 NetBox?

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.

What are the best alternatives to rgm?

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