Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We had a pretty bad experience with it on a NextJS app and had to gut it out (I decided not to charge the client for this multi-week refactoring effort to pull out Supabase since it was upon my recommendation that they went with Supabase, so that decision actually cost us thousands of dollars).

It is good to get started and no doubt useful for simple CRUD apps. But once you want to start doing more complicated stuff, a lot of the RLS primitives become very hard to maintain and test, for example. You could say that that's Postgres's fault, but Supabase strongly pushes you in that direction.

The tooling, while looking quite polished, just felt pretty half baked along with docs (at least a year ago when we pulled the plug). Try to implement even a halfway complicated permissions scheme with it and RLS and you are in for a world of hurt and seemingly unmaintainable code.

So we ditched Supabase Auth for AuthJS, and are using vanilla postgres with Prisma. That's worked well for us. All the tooling is relatively mature, it's easy to write tests, etc.

Maybe if AI is writing some of the code, it might get easier, but for now, I'm avoiding Supabase like the plague until I see a project that's relatively complex that's actually easy to maintain.



Agree, also the logging is very limited across the board,, database functions are impossible to debug without good logging, I think a lot of people don't realize its not a direct copy of Postgres, for the cloud version several Postgres functions are disabled by default.


Nice to see others using Prisma in the wild! Prisma is the first ORM I've ever used (after decades of trials) that I actually enjoy using.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: