Hey everyone,
I've been running into issues accessing Supabase from several networks here in India. My web app heavily relies on Supabase for key functionalities: PostgreSQL database, authentication, file storage, and real-time features. Given that my whole backend is tied to Supabase, I'm seriously considering a migration.
I'm currently looking at a couple of options:
1. **Neon (for PostgreSQL) + Clerk (for authentication) + Cloudinary (for file uploads) + Pusher (for real-time features)**
2. **Firebase**, although I'm concerned about compatibility since my current schema is PostgreSQL-based.
Which of these options would be more manageable and offer better long-term flexibility? Also, would it make more sense to use split services like Neon and Clerk, or just transfer everything over to Firebase? Any insights would be greatly appreciated!
4 Answers
Honestly, relying on external services can be risky. I’d suggest building your own application layer and deploying it yourself. That way, you have full control. It’s wild that Supabase is having accessibility issues. Is it just a temporary routing problem or is it a widespread thing?
Following this thread! Interested to see what others think.
Have you thought about self-hosting Supabase on a local VPS, like DigitalOcean or Hetzner in the Mumbai or Bangalore area? This way, you can retain your PostgreSQL schema, authentication logic, and storage APIs without the hassle of a full migration. It could save you time compared to setting everything up on Neon or Clerk.
I hadn't considered self-hosting before, but it seems like a solid alternative now. Just heard that the access issue with Supabase has been resolved.
You might want to think about moving to Google Cloud Platform or AWS. Those options tend to be more stable and you can set things up to suit your needs better than with a single service.
It looks like it works fine if you use a VPN, or you could try changing your DNS server since some ISPs are blocking supabase.co.