Supabase

“I build a Supabase security skill for Claude, and now I built its read-only MCP server (open source)”

“our Supabase dashboard can silently drift from your migrations. I built an open-source CI check for it”

“That's a solid stack switch, Cloudflare and Supabase direct gives you way more control than the default Lovable setup especially once health data gets involved.”

“I moved the full app to Cloudflare and used Supabase as the database, but this time I was connecting to Supabase directly and had control over the setup.”

“The extra charge is per supabase project, not per website. I'd keep the backend there and choose frontend hosting separately.”

“Increasingly thankful for Supabase. Their incredibly insecure defaults make data collection so easy :)”

“Am good fan of supabase but check out neo once. They opened storage recently with 5gb”

“Does anybody know a workaround or why I can't copy anything to clipboard from Supabase? Can't get my API keys, can't copy rows, can't get URL, can't do anything”

“Supabase is the backend (Postgres, Auth, Storage, Edge Functions). Your Next/static sites still go on Vercel, Cloudflare Pages, Netlify, or a VPS. People sometimes host a tiny static page from Storage, but that is not a real multi-site frontend setup.”

“Supabase pro is $25 per project. If you want pro features, you need to pay $25 for each project.”

“Je serais toi je prendrais Supabase en self-host dockerisé. Tu prends un petit VPS et adieu les limites (même du pro).”

“you've got it right, Supabase is backend only, frontend still needs Vercel/Netlify/Cloudflare regardless of plan.”

“My understanding is that Supabase handles the backend (database, auth, storage, edge functions) but doesn't host the websites themselves, so the frontends would still need to live somewhere like Vercel, Netlify or Cloudflare. Did I get that right, or is anyone here serving full sites straight from Supabase?”

“Verifying RLS is enabled for every table in a Supabase project”

“start with Supabase unless you already know you want to manage the whole stack yourself.”

“use supabase but keep it behind your own interfaces, so the app talks to your auth/data/storage layer and supabase is just the provider underneath. thats how i do it.”

“The main issue that I have is the pricing when it comes to scalability because if my app reaches 150k, Supabase becomes really expensive and it is a pain to move everything later. So, should I use it anyways or self host it on a VPS that will be cheaper?”

“Clerk vs Supabase auth is honestly the least interesting part of this, the org/membership DIY is where the actual pain lives and you skipped right past it”

“\- Auth pricing is attractive vs Clerk/Auth0 at scale”

“Supabase is Postgres with useful things bolted around it, and if you ever outgrow the platform the data can move.”

“Supabase will handle it fine if you route through the pooler (Supavisor) rather than a connection per request, and put your indexes and RLS policies on the seller and product tables from day one, retrofitting row level security once sellers are writing real data is genuinely painful.”

“I liked supabase as it saved me a lot of effort tbh as a solo developer”

“The only things I still use the supabase sdk for is user management, which, to my current knowledge, is the best way to manage users still. Supabase doesn't want us touching the user namespace in postgres so that they can make improvements without breaking application code.”

“The part that actually hurts is auth and storage, and most people using Supabase for those probably shouldn't be.”

“this is why you shouldn't use Supabase SDK and use a ORM and treat it like a Postgres instance on any VPS.”