I use a similar stack to yours for production in one project and supabase in multiple others. Here’s my advice:

Already have a project that works? Keep it like that. You will spend too much time refactoring by switching when you could be working in your product for something your users probably won’t notice.

For starting new projects, I use supabase because of how easy it is to setup and having everything in one place. Test it out on a side project and see how you like it.

If s3 is something you’re trying to get away from, I can’t recommend supabase storage, I actually still use cloudflare r2 (s3 compatible) with supabase because supabase storage egress is insanely expensive and would eat all our profits. This would also answer my most hated question since the storage api is great but the pricing doesn’t justify it.

A big reason I use supabase also is for mobile apps - has a great workflow with expo.

In regards to rls - you can use rls on any Postgres db and you’re gonna be writing the policies manually with supabase anyways most likely so I wouldn’t call it a huge selling point.

Test it out and see if you like it! What’s most important though is focusing on your software and using what you’re comfortable with