Why you should NOT use Supabase: 1. SDK Trap - not TypeScript by default, type-gen is bad, easy to make mistakes 2. Security with the SDK is terrible - need to set up a lot of things to have something work 3. Vendor lock-in with the Auth, don't have... your keys 4. Pricing way more expensive than a $8/month db + better-auth 5. Better alternative for all tools they provideshow more

1. Totally false, it’s fully typed. 2. There nothing to setup besides one RLS by CRUD action by table. Like Firebase 3. Same as most hosted solutions But keep trying maybe at one point you will say something valid, who knows😂😂

❤️ i lie so you can react

It’s our little thing

The SDK types argument is the weakest one here. Every tool has a setup cost. The real trap isn't Supabase, it's skipping the docs and blaming the tool. What's your actual alternative for a solo dev shipping fast?

convex, simple postgresql

1. Wrong 2. Skill issue 3. Valid 4. Features justify price 5. Maybe, but they work nicely within the ecosystem Their recent outages have been pretty concerning though

Are you getting paid by Convex or something to spread all this false information? Or just rage baiting? I genuinely cannot tell.

None of this, just have vibe-codeur friend using Supabase and making so much mistake

You’d do better with a “how to use Supabase better” post. Try that 😉

Doing this out of hate or what? Cuz it's getting out of hand!!

😂

Literally me right now... After dealing with @awscloud @AWSSupport

@awscloud @AWSSupport ???

@awscloud @AWSSupport I've had my acount for like a month and today they locked it because i wrote the name of a company that does not exist in my company details. I received a sketchy email literally threating me to click links in the email. Which they explicitly say they don't do.

wow great i had no idea

😂

yeah supabase auth sucks, total vendor lock-in nightmare

Was thinking to migrate but glad i read the comments

J’ai jamais compris l’obsession des solo devs aka indie hackers pour le “meilleur” outil ou stack. Ce genre de problématiques se posent après la série A quand il faut scale

oui xD

This is the part I find interesting too: the convenience is real, but once auth, security rules and data access become platform-specific, leaving gets expensive fast. I’m building CrescoDB around the opposite idea — your backend stays in your project, the schema works across SQLite/Postgres/MySQL, access can be audited locally before deploy, and there’s an explicit eject path so you’re not forced to stay with us. Which of those five was the biggest dealbreaker for you in practice?

alternative : neon, convex, railway, any postgresql provider actually so digitalocean, aws, anything works

İ like phpmyadmin with php

Firebase is great and comes with many features

What’s the alternatives

neon, convex, railway, any postgresql provider actually

Either dx, or reasonable infrastructure.

1) Drizzle 2) Drizzle + RLS 3) Auth is cheaper than alternatives, easy to integrate, and you can migrate later, or create custom db auth schemas and functions 4) Saving time > pricing, once profitable, it pays for itself 5) Start simple, migrate later 6) you can self host it

agree. agree. agree

find also the youtube video :

regarding pt 2 RLS security, how is Neon any better? its the same weakness or am i missing something?

no need RLS, just have a backend

2 production apps on Next.js + Supabase shipped this year. The RLS concern is real but solvable. We set up row-level security at day one and enforce it in code review. Auth lock-in is the bigger genuine tradeoff. Once you rely on Supabase Auth, migrating off is painful.

disagree on point 2. RLS is a feature, not a bug. if you set it up right, security lives at the database layer and your app code stays clean. we've shipped 2 production apps with Supabase RLS + Next.js and had zero permission bugs. setup cost is real but it's one-time.

vibe codeur doesn't know what mean rls

fair point. the vibe coder ships without knowing. we fix it later for $15-25K. RLS is always on that list.

the auth lock-in is the real killer. lost a whole migration week to that once

aieee

Security in Supabase is even more awful. By default, Supabase’s browser client persists the session in localStorage, both access and refresh tokens. One XSS or a compromised frontend dependency and you have a session compromise problem.

this is terrible

what about convex?

@acadb3k fun

I’ll never start a new app and use supabase again. Never been less satisfied with my database setup

why not mondogb instead?

even worst

Oh yeah, it’s a real battle 😂 until Supabase catches the KO.

Just focus on building your application. You can use Supabase as a traditional db with managed pool connections.

I love @supabase

@supabase i love u...

@supabase 😍

Can someone elaborate on point #3 please? Thank you. I agree with the security concerns. For example: SQL functions are executable by public and anon by default. 😓

exactly

As the others called you out already. 100% skill issue plus false information. If you skip reading documents, it just doesn’t matter which solution you are using, always gonna be bad. Your suggested solutions are full of these problem too.

happy to read this

The type-gen complaint is real — I switched to Drizzle + raw Postgres and the TypeScript experience went from fighting the SDK to just writing queries that actually make sense.

Pourquoi pas utiliser Notion comme bdd dans les débuts, avez-vous déjà essayé ça ?

bad idea c'est slow

If you use supabase without the sdk calling directly with raw sql or any orm then it works fine, just like any database.

agree but why use suba then

To get all the backend essentials in one place, like auth, db, storage, realtime if needed. Its good for this usecase where the user doesn't have to go and connect with multiple sources. I use Convex and Cloudflare Workers, bdw. Migrated from supabase.

You can self host it

☠️

Supabase must hate to see you coming

???