Edu-Carone-SA brings Mike's staging stack in-house on AWS
This fork trades hosted building blocks for a self-managed staging environment designed to keep tighter control of deployment, access and spend.
Edu-Carone-SA has assembled an isolated AWS staging setup around Mike, including container-based hosting, secure file storage and a modest monthly budget alert. The notable move is replacing hosted Supabase services with a self-hosted version of its authentication, data-access and gateway layers.
That means the team can operate the same core services inside its own cloud account rather than depend on the managed SaaS tier. It also avoids long-lived cloud storage credentials by granting the running application only the permissions it needs. The work is backed by recovery notes from two staging outages and a basic login and sign-up check for the AWS environment.
The setup is tied to this team's account, but the operating pattern is portable.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?