punyaslokdutta folds document storage into one vendor
This fork stops running documents through a separate cloud-storage service and routes them through the same platform that already handles its login and database.
Most builds of Mike keep their files in one place and their accounts and records in another - uploads land in Cloudflare's object storage while everything else lives in Supabase, the platform that handles sign-in and the database. punyaslokdutta cut the split. Documents now go through Supabase too, so the whole stack leans on a single service with one set of credentials instead of two.
The upside is fewer moving parts: one account to manage, one bill, one place where things can break. The trade-off is that document storage now lives inside Supabase's size and bandwidth ceilings rather than the flat per-action pricing of the storage service it replaced. Whether that pinches depends on how many documents you expect to push through it.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?