exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
Comparison · Infra & APIs
NetBox vs PocketBase
A side-by-side editorial comparison of NetBox and PocketBase — release velocity, themes, recent moves, and the top alternatives to consider.
NetBox vs PocketBase: at a glance
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.
What is PocketBase?
PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.
PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.
NetBox vs PocketBase: editorial side-by-side
NetBox
6.3INFRA · APIS
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.
PocketBase
5.0INFRA · APIS
PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.
◆ Current state
PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.
◆ Where it's heading
This is a mature single-maintainer project in steady maintenance, prioritizing dependency hygiene and supply-chain caution over new capability. Two things are explicitly deferred to the future: proper non-zero exit code support for CLI commands, held back to v0.40 or v0.41 after a panic-recovery change was reverted, and eventually replacing ozzo-validation with a purpose-built validator. The continued 0.22 backports show a real installed base that hasn't migrated.
◆ Prediction
The deferred CLI exit-code work marks v0.40 as the next feature release rather than another patch. Expect the 0.39 and 0.22 pairing to continue until 0.22 is formally retired.
Alternatives to NetBox and PocketBase
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 PocketBase.
nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
lifecontingencies
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
See all NetBox alternatives → · See all PocketBase alternatives →
Recent activity from NetBox and PocketBase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoNetBoxNetBox 4.7 beta models cooling plant the way it models power ⚡
- 5d agoPocketBaseAPI preview fixes, UI polish, and Go dependency bumps
- 5d agoPocketBase0.22 LTS backport of the Go dependency bumps
- 8d agoNetBoxGraphQL N+1 fixes and permission corrections in 4.6.8
- 15d agoNetBox4.6.8 release candidate refreshes translation strings
- 19d agoNetBox4.6.7 trims GraphQL and scope-rebuild query overhead
- 20d agoPocketBaseCLI panic recovery reverted to restore non-zero exit codes
- 20d agoPocketBase0.22 LTS backport of the CLI exit-code revert
- 21d agoNetBoxCluster-scoped VLANs, tag "any" lookup, audit-trail hardening
- 27d agoPocketBaseFirefox bulk-select fix, goja and filter-parser updates
- 27d agoPocketBase0.22 LTS backport of the goja and fexpr bumps
- 1mo agoNetBoxMDC connectors, script-module REST updates, Korean support
Frequently asked questions
What is the difference between NetBox and PocketBase?
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.
Is NetBox better than PocketBase?
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.
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 PocketBase?
Top PocketBase alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PocketBase alternatives" section above for the current picks, or visit /alternatives/pocketbase for the full list with editorial commentary on each.