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 Prowler — 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.
Prowler's agentic defender arrives — and it lives entirely behind the subscription line
Prowler is a cloud security posture platform with an open scanner at its base and a hosted product above it. The recent releases are dominated by Lighthouse AI, which arrived in 5.33.0 as an agentic assistant wired to the Prowler Cloud backend that discovers and runs Prowler's own tools to answer questions about findings, compliance posture and risky resources, then gained a persistent side panel in 5.35.0. Every one of these features carries the same note: available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription. The 5.34.0 release renamed the product family to match that structure.
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.
Prowler is a cloud security posture platform with an open scanner at its base and a hosted product above it. The recent releases are dominated by Lighthouse AI, which arrived in 5.33.0 as an agentic assistant wired to the Prowler Cloud backend that discovers and runs Prowler's own tools to answer questions about findings, compliance posture and risky resources, then gained a persistent side panel in 5.35.0. Every one of these features carries the same note: available exclusively in Prowler Cloud and Prowler Private Cloud with a subscription. The 5.34.0 release renamed the product family to match that structure.
The direction is a platform sorting its value above the scanner. Findings are becoming workflow objects rather than report rows — grouped or separate Jira issues carrying Prowler context and deep links — while the AI layer moves from a page you visit to a panel that follows you through the app. The patch releases underneath tell the other half of the story: Attack Paths graph mutations retrying Neptune concurrency failures, bounded node identifiers to avoid Neo4j index key limits, deterministic upsert ordering to prevent PostgreSQL deadlocks. That is a graph-backed analysis engine being scaled under load while the differentiated surface is built on top.
Expect Lighthouse AI to keep absorbing workflow actions — ticketing, remediation suggestions, compliance queries — and for the gap between the open scanner and the subscription platform to keep widening.
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 Prowler.
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.
NetBox ships fortnightly, and the headline work is query performance rather than new surface
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 Prowler alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Prowler 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. Prowler 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 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 Prowler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Prowler alternatives" section above for the current picks, or visit /alternatives/prowler for the full list with editorial commentary on each.