Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
NetBox vs Supabase
A side-by-side editorial comparison of NetBox and Supabase — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:breaking-changes
NetBox vs Supabase: 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 Supabase?
Supabase is closing its most-exploited default: tables stop being public unless you say so.
The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.
NetBox vs Supabase: 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.
Supabase
0.0INFRA · APISDEVOPS
Supabase is closing its most-exploited default: tables stop being public unless you say so.
◆ Current state
The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.
◆ Where it's heading
Supabase is paying down the security cost of its own convenience. Auto-exposing every public-schema table made the product fast to start with and easy to misconfigure; the fix is explicit Postgres grants, staged over six months from new projects in April to all existing projects on October 30. The RLS Tester is the same theme from the other side — the auto-exposure default only worked if row-level security was correct, and until now there was no way to check.
◆ Prediction
Expect the remaining rollout dates to hold and more of the developer experience to be rebuilt around explicit grants, with the RLS Tester graduating from preview as it becomes the tool people need to verify the new model. The October cutover for existing projects is the moment where this stops being an announcement and starts breaking things.
Alternatives to NetBox and Supabase
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 Supabase.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all NetBox alternatives → · See all Supabase alternatives →
Recent activity from NetBox and Supabase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoNetBoxNetBox 4.7 beta models cooling plant the way it models power ⚡
- 7d 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
- 21d agoNetBoxCluster-scoped VLANs, tag "any" lookup, audit-trail hardening
- 1mo agoNetBoxMDC connectors, script-module REST updates, Korean support
- 3mo agoSupabaseDeprecation Notice: Dropping Support for Node.js 20
- 3mo agoSupabaseDeveloper Update - May 2026
- 3mo agoSupabaseBreaking Change: OAuth token endpoint will return HTTP 200 instead of 201
- 3mo agoSupabaseBreaking Change: Tables not exposed to Data and GraphQL API automatically ⚡
- 3mo agoSupabaseFragment of the no-auto-expose announcement
- 3mo agoSupabaseFeature Preview: RLS Tester
Frequently asked questions
What is the difference between NetBox and Supabase?
Both compete on the same themes — breaking-changes — within Infra & APIs. 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 Supabase?
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 Supabase?
Top Supabase alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Supabase alternatives" section above for the current picks, or visit /alternatives/supabase for the full list with editorial commentary on each.