Pressable
Pressable is shipping near-daily, and MCP is being maintained as a peer surface to its API.
A side-by-side editorial comparison of Supabase and Statsig — 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.
Statsig is packaging its own workflows as skills for someone else's agent to run.
Statsig's experimentation and feature-flag platform opened a public agent-skills repository holding reusable workflows — create dashboard, create cloud metric — written as instructions an AI agent can execute. Its MCP server extended to Segments and Layers, covering user targeting and experiment configuration, and Metrics Explorer gained the ability to abort long-running queries. The crawled feed captures marketing pages as entries, so several rows carry navigation boilerplate rather than release notes.
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.
Statsig's experimentation and feature-flag platform opened a public agent-skills repository holding reusable workflows — create dashboard, create cloud metric — written as instructions an AI agent can execute. Its MCP server extended to Segments and Layers, covering user targeting and experiment configuration, and Metrics Explorer gained the ability to abort long-running queries. The crawled feed captures marketing pages as entries, so several rows carry navigation boilerplate rather than release notes.
The direction is agent-operated experimentation. MCP covering segments and layers means an agent can configure targeting, and the skills repository means the multi-step workflows around that configuration are distributable artifacts rather than documentation. Statsig is betting the console is not where experiments get set up much longer.
Expect the skills catalog to grow toward the analysis side — reading experiment results and proposing rollout decisions, not just creating objects. The query-abort work suggests warehouse cost control is a live concern as agent-driven usage increases.
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 Statsig.
Pressable is shipping near-daily, and MCP is being maintained as a peer surface to its API.
Cosmic retired AI Studio and gave its agents goals — the CMS is becoming an agent runtime.
Pipedream put OAuth on its 10,000-tool MCP server and annotated every tool read or write.
Five of six VictoriaMetrics entries are scraped GitHub page furniture; one is a real LTS patch.
Buildkite is forcing a major agent upgrade and handing agents a shortcut through failures.
Rootly's AI stops summarizing incidents and starts investigating them.
See all Supabase alternatives → · See all Statsig 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 Statsig 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 Statsig 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 Statsig alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Statsig alternatives" section above for the current picks, or visit /alternatives/statsig for the full list with editorial commentary on each.