Retool
The app builder is now agent-first; the admin console is racing to catch up.
A side-by-side editorial comparison of Supabase and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
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 ships fortnightly, and the headline work is query performance rather than new surface
NetBox is on a steady two-week release rhythm through the 4.6 line, and each drop follows the same structure: a handful of modelling enhancements, a block of performance improvements, then bug fixes. Recent additions are practical rather than expansive — bulk VLAN creation, VLAN scoping to a device's cluster, MDC and MU fiber connector types, colored badges for custom field choices, a header_safe Jinja2 filter, Korean language support. The most recent release, 4.6.7, contains no new features at all.
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.
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.
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.
NetBox is on a steady two-week release rhythm through the 4.6 line, and each drop follows the same structure: a handful of modelling enhancements, a block of performance improvements, then bug fixes. Recent additions are practical rather than expansive — bulk VLAN creation, VLAN scoping to a device's cluster, MDC and MU fiber connector types, colored badges for custom field choices, a header_safe Jinja2 filter, Korean language support. The most recent release, 4.6.7, contains no new features at all.
The performance section is where the direction shows. Release after release removes extraneous database queries from the GraphQL API — custom field data, rack reservation units, IP and prefix family lookups — and adds prefetch hints and serializer caching to list endpoints. That is the profile of a tool whose users have grown their datasets past what the original query patterns handled, so the work has moved from modelling more infrastructure to serving existing models faster. The enhancement stream continues in parallel, filling in connector types and bulk operations as operators hit gaps.
Expect the 4.6 line to continue on its fortnightly cadence with further GraphQL and list-endpoint query optimisation, alongside incremental modelling additions driven by operator requests.
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 Supabase or NetBox.
The app builder is now agent-first; the admin console is racing to catch up.
Buildkite is rebuilding CI so an agent, not a human, reads the failed build
Windmill let its AI build deployable drafts, then handed two paid runtimes to the free tier.
Prowler's agentic defender arrives — and it lives entirely behind the subscription line
MinIO narrows its open build to a storage engine and points paying users at AiStor
ElevenLabs is giving voice agents a git workflow - branches, rebases, and merge previews.
See all Supabase 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 5.0 vs 0.0), with 0 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 5.0 vs 0.0), with 0 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 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.
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.