Retool
Retool is retiring standalone Assist while folding the same capability into the app builder.
A side-by-side editorial comparison of forestploter and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
A forest plot package that keeps handing users control of one more graphical detail.
forestploter draws forest plots where the layout is driven by the data frame itself, so text columns and confidence intervals sit in the same grid. The theme function has become the package's centre of gravity: it now controls graphical parameters for titles, legends, axis, arrow labels, footnotes, and reference lines, with multi-column and row-order legend controls added most recently. Two releases shipped nine minutes apart in April 2026 after a two-year gap, deprecating some theme parameters, removing inter-cell gaps, and improving tick breaks.
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.
forestploter draws forest plots where the layout is driven by the data frame itself, so text columns and confidence intervals sit in the same grid. The theme function has become the package's centre of gravity: it now controls graphical parameters for titles, legends, axis, arrow labels, footnotes, and reference lines, with multi-column and row-order legend controls added most recently. Two releases shipped nine minutes apart in April 2026 after a two-year gap, deprecating some theme parameters, removing inter-cell gaps, and improving tick breaks.
The direction has been consistent for four years: whatever a user might want to restyle eventually becomes an argument. Point size stopped being transformed, cell height adjustment was removed as unwanted, legends gained size, column, and fill-order control, and vertical lines learned to extend the full plot height and to draw beneath the whiskers. The one structural move was 1.1.0, which let callers supply their own confidence-interval and summary drawing functions — turning a fixed renderer into an extensible one. Everything since has been the arguments that extensibility did not cover.
The latest release deprecates theme parameters rather than adding them, which suggests the next one consolidates the theme surface that has grown for four years rather than extending it further.
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 forestploter or NetBox.
Retool is retiring standalone Assist while folding the same capability into the app builder.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all forestploter 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 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.
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.
Top forestploter alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "forestploter alternatives" section above for the current picks, or visit /alternatives/forestploter 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.