Rootly
Rootly's AI stops summarizing incidents and starts investigating them.
A side-by-side editorial comparison of Supabase and Airbyte — 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.
Airbyte 2.0 made the pipeline run both ways: data activation turns the warehouse into a source.
The release line runs from 1.1 through 2.0, each version bundling platform-wide changes: log filtering and OpenShift support, file transfers, schema refresh controls, declarative OAuth in the connector builder, connection health dashboards, and pagination for workspaces with thousands of connections. Version 2.0 in October 2025 is the pivot, taking both faster sync speed and data activation to general availability. The tracked feed has been quiet since, with the only 2026 row being a mis-scraped GitHub profile page.
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.
The release line runs from 1.1 through 2.0, each version bundling platform-wide changes: log filtering and OpenShift support, file transfers, schema refresh controls, declarative OAuth in the connector builder, connection health dashboards, and pagination for workspaces with thousands of connections. Version 2.0 in October 2025 is the pivot, taking both faster sync speed and data activation to general availability. The tracked feed has been quiet since, with the only 2026 row being a mis-scraped GitHub profile page.
Airbyte spent the 1.x line making ingestion dependable at scale — performance, observability, deployment targets, connector authoring — and then used 2.0 to run the pipeline in reverse, delivering modeled warehouse data into CRMs, marketing platforms, and support tools. That puts it against reverse-ETL vendors rather than only extract-and-load competitors, using the same connector catalog for both directions. The 1.7 work on moving files alongside records points at the other demand driver: unstructured data for retrieval systems.
Expect data activation to widen its destination catalog on the operational side, since the value of reverse ETL scales with how many business tools it can write into.
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 Airbyte.
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.
Mixpanel is pushing analytics out of its own tab — into Postgres, Slack, and now Glean's assistant.
See all Supabase alternatives → · See all Airbyte alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Supabase and Airbyte 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 Airbyte 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 Airbyte alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Airbyte alternatives" section above for the current picks, or visit /alternatives/airbyte for the full list with editorial commentary on each.