Introducing @supabase/server

This is a new package that handles auth verification, client setup, request context, and common server-side boilerplate for you.

It works across Edge Functions, Vercel Functions, Cloudflare Workers, Hono and Bun.

We anonymously analyzed 25,000 deployed Edge Functions and saw the same pattern everywhere: developers were rebuilding the same setup code over and over just to get to their actual business logic.

Most functions needed to: Create a Supabase client with SUPABASE_ANON_KEY Create another admin client with SUPABASE_SERVICE_ROLE_KEY that can bypass Row Level Security Verify the JWT Parse claims Handle CORS Wire up auth context Copy/paste the same _shared/*.ts files between functions With @supabase/server you just declare who can call your endpoint and get a fully initialized context back: User-scoped Supabase client Admin client with service role access Verified user identity JWT claims Built-in request/auth helpers Note that export default { fetch } is equivalent to Deno.serve(...) .

Both define a request handler.