juanjo puts the Supabase exit on the record, warts and all
A new set of decision documents explains why this fork is cutting ties with its hosted backend, and is unusually frank about what still isn't finished.
Supabase is a hosted service that handled both this fork's database and its user logins. juanjo's latest work doesn't just swap it out for software that runs entirely on a developer's own machine, with no outside accounts needed to get started. It writes down the reasoning: you couldn't develop offline, and the hosted setup tangled logins and data storage together in a way that was awkward to unpick.
What makes it worth a read is the candour. The same record lists what the move left for later, including password resets, email verification, and sign-in through outside accounts, and flatly admits that the app's error messages currently expose internal database details, the kind of leak a security reviewer would flag.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?