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 ↓

Damn, Supabase really is locking in 🥶

Dear team can you make yearly subscription please

Per-request logic that works across runtimes + Hono/H3/Elysia/Nest bridges is super handy

this is huge, write once run anywhere with fetch is exactly what we needed

I got narrative that hit massively honestly

write once, run anywhere, and now the bug in your auth check ships to every runtime at the same time

写一次到处跑这点挺省心，鉴权终于不用每个框架都写一遍了。

Write it once, run it on any runtime with fetch is the right design. Auth checks are exactly the kind of logic that drifts when every runtime has its own copy.

Middleware that runs on any runtime with fetch, bridges into Hono/NestJS without rewriting. That's what I need for per-request watcher checks.

Per-request logic that runs on any fetch runtime is clever

When are passkeys going GA?

withOAuthProtectedResource covers the whole mcp oauth discovery flow in one entry. no private api behind defineMiddleware either

Is this a long term run

How does the middleware integrate with existing authentication systems?

"run it on any runtime that has fetch" is the part that matters. bridge into Hono/TanStack Start means I can stop copying auth checks into every route.