Supabase

we support all developers, even the ones who use light mode

Introducing Supabase Middleware. Write per-request logic once, like checking who's calling, and run it on any runtime that has fetch. The same middleware also works inside Hono, H3, Elysia, NestJS, and TanStack Start with a bridge you copy. Learn More ↓ https://lnkd.in/gXBJ2AHw

People have been asking to run Supabase locally without Docker for a while. You can do that now. 🐳 Plus, every coding agent gets its own local project, so one can reset its database while another is mid test run. https://lnkd.in/gSGGnRn7

🧾 Stripe Data Pipeline now syncs real-time data to Supabase. Pick a Supabase project from the Stripe Dashboard and your payment, customer, subscription, and other Stripe data land in your own database, backfilled and kept in sync. Learn more ↓ https://lnkd.in/gyJy-bh9

wait... 🤨

Declarative schemas in the Supabase CLI now run on a rebuilt diff engine, pg-delta. You keep your schema in versioned .sql files and the CLI writes the migration. Generated migrations now cover: • RLS policy changes • Grants • Views and materialized views • Partitions Currently in alpha. To opt in, add [experimental.pgdelta] with enabled = true to config.toml. Learn more ↓ https://lnkd.in/gbHiE8dr

Supabase now works with Grok Bot. 🤖 Request a change in chat, and Cursor builds and runs it on your Supabase backend through the Supabase MCP server. Learn more ↓ https://lnkd.in/g8jRqBPv

Make something agents want. We're sponsoring the YCombinator hackathon for builders whose primary user is an agent. Oct 17–18 · YC HQ, San Francisco Apply ↓ https://lnkd.in/gPW9ze6D

🧠 Google DeepMind sponsored the Supabase Select 2026 after party and hackathon. Here's to giving builders a reason to stay late and come back early ✨

Regarding the recent Deno acquisition: Edge Functions are built on the Deno runtime today, but importantly, we operate our own infrastructure and don't depend on Deno's hosted services. While Deno is winding down active development over the next year, the Deno team has committed to contributing bug and security fixes until then. And we'll continue our work with the Deno team to incorporate critical improvements to the Edge Function runtime during this transition. Our next-generation offering, Compute, is already in an advanced stage of development and will support Deno as well as other runtimes like Node.js and Bun. We'll provide a seamless migration path from Edge Functions to Compute. Our goal is to make Compute available for new workloads and existing Edge Functions well before Deno's support window closes. Existing Edge Functions will continue to be supported, and there's no need to migrate today, and no need to stop writing them. Longer term, Compute will give you more flexibility in choosing your runtime, and we expect it to become the recommended path for new workloads. We don't have a public timeline to share yet, but we'll provide updates as soon as we do. https://lnkd.in/g9Ar8V6A