It would be great if Supabase Cloud could provide frontend hosting for frameworks like Next.js, React, Vite, and others.
This would allow developers to host complete full-stack applications directly on Supabase instead of using separate providers for the frontend (such as Vercel, Netlify).
Having frontend hosting, database, authentication, storage, edge functions, and MCP integrations all in one platform would simplify deployment, management, and billing.
I think this idea is even more relevant today with AI-assisted development. Developers can build applications much faster, but still need to manage separate frontend and backend platforms.
Users are requesting Supabase Cloud to provide frontend hosting for frameworks like Next.js, React, and Vite. This would enable developers to host full-stack applications directly on Supabase, simplifying deployment and management by consolidating frontend and backend services. Currently, users pair Supabase with other providers like Vercel or Netlify for frontend hosting.
+1 for this feature request! As someone who has built and deployed full stack apps using Supabase as the backend (PDF Ghar - pdfghar.in and Cresolve - cresolve.in), I've felt this pain firsthand. Currently I use AWS Amplify and Vercel for frontend hosting alongside Supabase, which means managing separate dashboards, billing, and deployment pipelines. Having frontend hosting natively on Supabase Cloud would make it a true full stack platform especially useful for indie developers and small teams who want a single place to manage everything. The unified billing alone would be a big win. This would also pair really well with Edge Functions and the existing auth/storage/database setup. Would love to see this on the roadmap!
This comes up a lot, and the "everything in one platform, one bill" appeal is real — especially for the AI-assisted, build-fast workflow you describe.
For now Supabase is deliberately the backend half (Postgres, Auth, Storage, Edge Functions, Realtime), and the expected pattern is to pair it with a dedicated frontend host — Vercel, Netlify, or Cloudflare Pages/Workers for SPAs and SSR frameworks. In practice that pairing is pretty smooth (the framework guides cover the env-var wiring), so the gap today is more about consolidation of billing/ops than capability.
Static/SPA builds (React, Vite, plain SPA) will deploy to any of those hosts with basically zero backend-specific config; Next.js SSR is the one where the host choice matters more (Vercel or Cloudflare for the server runtime).
As a product direction it's a legitimate thing to want, so keep it as a Feature Request and let it accumulate upvotes — "first-party frontend hosting" is a recurring ask and the vote signal is what helps it get prioritized. I don't think there's a native option coming that I can point you to today, so the honest answer is: pair with a frontend host for now.
Frontend hosting for SSR frameworks like Next.js would require a substantial amount of additional infrastructure that is quite different from what Supabase runs today: a build system, edge CDN, cache invalidation, and runtime environments for server-rendered pages. That is essentially what Vercel and Netlify have spent years building, so it is a large addition to the platform scope.
A simpler version of what you are asking already exists. Supabase Storage supports serving static files from a public bucket with a custom domain, which covers Vite and Create React App SPAs without any additional hosting service. You build locally or in CI, upload the dist folder to a public bucket, and point your domain at the storage URL.
For Next.js specifically, the native Vercel integration with Supabase is fairly tight: it handles connection string injection, connection pooling via the Supabase integration, and environment variable sync. The free tiers of both platforms together cover most hobby and early-stage projects without adding billing complexity.
For those who want everything in one place, the most practical near-term option is to deploy Next.js to a Supabase Edge Function using the Next.js edge runtime adapter, which keeps compute and database in the same region and under the same billing account. It is more setup than a managed platform but it achieves the co-location goal. Worth exploring if consolidation is the main driver.