LevelFive-Studio drafted a total AWS rebuild, then closed it in eight seconds

@saratpediredla-level5 put together a nine-step migration that would have rebuilt every layer of Mike on Amazon's cloud: hosting, database, authentication, file storage, and email. Supabase (an open-source Firebase alternative that bundles a Postgres database with built-in auth) would have been replaced by Aurora, Amazon's managed Postgres, with sign-in handled by Clerk, a hosted identity service. Cloudflare's edge workers would give way to AWS's CloudFront and Lambda, and the whole environment would be described in a single infrastructure-as-code file.

The author considered a shim that would have let existing code keep talking to the database the old way, and explicitly rejected it in favour of rewriting every callsite cleanly. A detailed deployment checklist and a forecast of which future upstream changes would conflict were included. The pull request was closed without merging eight seconds after it opened. The work sits on the fork as a reference design - a fully worked answer to "what would it take to leave Cloudflare entirely?"