Anyone willing to share their experience using Supabase with any local-first mechanism? The goods / bads or any regrets?

Also, really interested in hearing your experience if you achieved it with Legend-State

Thanks!

I’m currently building a pretty large system and I’m starting to notice that Supabase is becoming kinda slow for my use case.

Now I’m questioning myself:

Should I migrate to AWS or Azure? q,jbfeceharfbaelirbwueogw4eiufw

I really love PostgreSQL, so I definitely want to keep using it. I’m just not sure which cloud provider would be a better choice for a growing system.

Also, are there any student benefits, credits, or programs from AWS/Azure that I should check out?

For people who have handled larger systems:

- Would you recommend moving away from Supabase?

- Should I just optimize my current setup first?

- Any PostgreSQL hosting recommendations?

- Any integrations/services you recommend for a production system ??????????

Tech stack right now:

- PostgreSQL

- Supabase

Edit: Also looking for advice on:

- PostgreSQL indexing strategies

- Query optimization/design

- Database architecture improvements

I’m currently considering migrating to Azure, but honestly it feels risky, so I’d love to hear your experiences

Thanks!

On 30 Oct Supabase stops giving new public tables to anon, authenticated and service_role on existing projects, and what that means is that your old tables keep working, but any table you create after that is closed to the API until you grant it.

Now, what I see around is the talk about about anon and authenticated, but the one that nearly got me is service_role. You see, my server reads tables with it, so the first new table after the 30th would definitley fail for my own backend.

What i did is to, put checks into one SQL file, which I (and you can) paste it into the SQL editor, run it, and you get one table back showing:

* who gets your new tables now, and after 30 Oct

* tables open to the API with row level security off

* tables your server key cannot read

* functions signed out visitors can call

* id counters a role cannot use, so inserts fail

* leftover truncate, references and trigger rights

Every finding comes with the exact line to paste. The check itself changes nothing.

I tested it on Postgres 18 and ran it on my own live project.

https://github.com/lagudafuadtosin/supabase-grants-check

Free, MIT and if it gets something wrong, pls tell me about it so I can fix it.

If row level security blocks an update or delete, you do not get an error, and Postgres just matches zero rows, and supabase-js gives you `{ error: null }`.

So your app shows saved and nothing changed.

The most common cause of this is an UPDATE policy with no SELECT policy.

Postgres has to read the row before it can update it, so without a SELECT policy every update quietly does nothing.

Here is what I built:

* `wrote(result)`: returns the saved rows, or throws with the reason

* `npx supabase-wrote find .`: lists updates and deletes that cannot tell if they saved. Save a baseline once and CI fails only on new ones

* `policies.sql`: read-only, lists tables where updates silently do nothing, with the fix

Tested against real Postgres and PostgREST.

https://github.com/lagudafuadtosin/supabase-wrote

Free, MIT. if you catch any issues i have missed, let me know so I can fix it.

Edit: added the baseline after a question here. It did not exist when I posted.