dropthejase rips out Supabase auth for Cognito
A full identity rebuild on AWS, with optional multi-factor login and a delete flow built for compliance.
The team has swapped Supabase - the all-in-one backend service that handled login - for Amazon Cognito, AWS's native identity system. Sign-up now requires email verification, login can be protected with an authenticator-app code, and every request to the backend is checked against AWS's own gatekeeper rather than custom code.
The more interesting move is around account deletion. When a user closes their account, the fork purges all of their data first, then removes the identity record - in that order, synchronously. That sequencing matters for anyone fielding right-to-be-forgotten requests, because it means there is no window where the login is gone but the underlying data still lingers.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?