4 ms·

I have to say, I tried it but at that time the self hosted offering was too limited, and the good stuff, the useful stuff was behind the cloud subscription payw

I have to say, I tried it but at that time the self hosted offering was too limited, and the good stuff, the useful stuff was behind the cloud subscription paywall. The initial experience was easy to get going, but the devil was in the details. Much of the logic should be server side also for security reasons and that wasn't possible when I tried it. People like to hype things that are easy to get started with but don't go much further so the initial impression remains. I think the appeal is to people who like doing frontend but don't like doing backend.

kiwicopple 3y ago
> the good stuff, the useful stuff was behind the cloud subscription paywall can you share more? everything is open source, the code available, and all OSI-compliant > Much of the logic should be server side also for security reasons and that wasn't possible when I tried it. This is possible in very many ways: 1. Write an RPC function and use PostgREST 2. Use Edge Functions 3. Use whichever frontend framework you are developing with (they all integrate well with supabase) 4. Connect a server directly to the Postgres data ase in a 3-tier architecture > I think the appeal is to people who like doing frontend but don't like doing backend. Perhaps! We also have a large number of customers using us as a traditional Postgres host. And we have a lot of "Postgres maxis" who love the RLS + PostgREST combo. You choose your level of comfort with Postgres: https://supabase.com/docs/guides/platform/shared-responsibility-model#you-choose-your-level-of-comfort-with-postgres https://supabase.com/docs/guides/platform/shared-responsibil...