For Developers in India, how are you taking in the Supabase blockage thats ongoing in India?
I’m not asking how to fix it, rather, what are the implications of this event on your decision to select Supabase for your future project back end needs, specially when developing for clients? Its scary how your whole project can go down suddenly out of the blue.
My Questions to you are :-
Do you think this was a one off thing and should not be the basis for rejecting supabase as your backend or do you think that since its happened now, continuing with it would be too risky ?
If not Supabase then what are our alternatives apart from Xano(Too expensive for start ups)?
Regarding your backend alternative question, I think at the moment Xano is the only no-code alternative if you want a full backend with authentication and user roles. We’ll be launching a WeWeb backend option soon but it’s still a few weeks away.
Are you in the building phase at the moment or do you have already have people using your app?
I’m still at the building phase Joyce. But i already have a few client projects in the pipeline and since they are fairly complex, i need to be sure of my foundations. For front end of a webapp its weweb and backend was Supabase.
I had selected Xano initially but their sudden U-Turn on pricing in Jan this year (20$ to 100$) within a span of 6 months took me by surprise.
As a startup developing softwares for clients using platforms like Weweb/Flutter flow/Supabase/Xano, more than costs, what matters is reliability. When a company revises its pricing without pre-informed prior notice and that too 5x pricing, it really hits their reliability for me. We build software for clients and clients trust us. We can’t just say sorry “it is what it is” and have the small/micro business client suddenly pay 5x price for just keeping that app alive. Hence my question of reliability of supabase also.
Sorry if i went on a rant there but being new to this field and the whole BaaS thing, it really has me shaken a little bit since Xano and Supabase are two giants in this area and both having some quirks this year really left me bamboozled. I hope i’m overthinking.
That is the next option but i’ve heard self hosting comes with its own set of challenges and the whole reason of choosing a BaaS kind of gets defeated since now i am supposed to do some devops which clearly can be challenging for any devs who are coming from no-code/low code space. Nothing impossible but just something i wouldn’t want to get my hands dirty with at the moment when i’m just beginning to understand split stack development, if that makes sense.
Not sure if you saw but it looks like Supabase are doing their best to find a solution for this issue as quickly as possible. They’ve been posting regular updates on here:
While they figure things out with all the parties involved, I think Fix #2 in the article I shared yesterday may be your best bet to get things to work properly for all your users.
