Rootly
Rootly's AI stops summarizing incidents and starts investigating them.
A side-by-side editorial comparison of Supabase and Mixpanel — 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.
Mixpanel is pushing analytics out of its own tab — into Postgres, Slack, and now Glean's assistant.
A dense April run covered three fronts: enterprise administration with Custom Roles and an organization-wide Audit Log, collaboration with threaded comments and a notification center, and data reach with the Postgres Connector reaching general availability. Alerts were reworked with evaluation windows, retroactive simulation, trigger history, and webhooks. The outlier is a Glean integration that exposes Mixpanel as an MCP app inside an enterprise AI assistant.
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.
A dense April run covered three fronts: enterprise administration with Custom Roles and an organization-wide Audit Log, collaboration with threaded comments and a notification center, and data reach with the Postgres Connector reaching general availability. Alerts were reworked with evaluation windows, retroactive simulation, trigger history, and webhooks. The outlier is a Glean integration that exposes Mixpanel as an MCP app inside an enterprise AI assistant.
Mixpanel is treating the query builder as a bottleneck rather than a product, and routing answers to where non-analysts already work. The Postgres Connector attacks the same problem from the other end, pulling transactional data in without ETL so fewer questions require a pipeline first. Custom Roles and the Audit Log are the enterprise prerequisites that make wider distribution sellable to security teams.
Expect more assistant-side distribution — additional MCP surfaces or chat clients querying Mixpanel directly — and further first-party connectors that skip the warehouse for common transactional sources.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Supabase.
Rootly's AI stops summarizing incidents and starts investigating them.
Notification infrastructure grows a memory: workflows can now wait on the real world.
Auth infrastructure that agents can drive and developers can run locally.
Expo shut down its own coding agent and kept the MCP server — it wants to be the substrate.
Clerk is building auth for machines: API keys, a CLI agents can drive, per-verification pricing.
Airbyte 2.0 made the pipeline run both ways: data activation turns the warehouse into a source.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Tap any card for the full editorial trajectory or compare directly with Mixpanel.
Marketing reporting quietly rebuilding itself around stored data instead of live API calls.
Steady administrative depth for M365, punctuated by a run of serious security fixes.
An on-prem M365 auditing tool whose releases are mostly dependency hygiene.
DuckDB in the cloud is turning into an agent's workspace, not just a query engine.
Airbyte 2.0 made the pipeline run both ways: data activation turns the warehouse into a source.
Redshift's feed is AWS documentation pages, so a patch number is the only release visible.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Supabase and Mixpanel are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Supabase and Mixpanel are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 Mixpanel alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Mixpanel alternatives" section above for the current picks, or visit /alternatives/mixpanel for the full list with editorial commentary on each.