🟢 #1 Replace Supabase with Auth0 + Heroku Postgres + S3 +3,401 -1,280 7d ago self by
mosha101 ↗ analysis ↗ GitHub ## Summary
rainylabs/mike
A rainylabs fork of Mike rewiring the platform onto Auth0, Heroku, and AWS - an infrastructure play more than a product pivot.
This is @rainylabs's fork of Mike, and at this early stage it reads as an infrastructure project rather than a new product direction. The work tracked so far centers on a single proposal from @mosha101: move Mike off its original Supabase-and-Cloudflare footing and onto an Auth0 tenant, a Heroku-hosted backend, and AWS storage.
The motivation appears to be operational consolidation - leaning on an existing drizzling.auth0.com identity setup and running Mike alongside whatever else this team already operates on Heroku and AWS. There's no sign yet of a rebrand, a vertical niche, or changes a user would notice in the product itself.
If you're curious how far along the migration is, or what the target architecture looks like in practice, the GitHub repo is the place to dig in.
What's in it
- Auth0-based identity Plans to consolidate authentication on an existing Auth0 tenant the team already runs.
- Heroku-hosted backend Intent to run Mike's backend as a container on Heroku rather than its original serverless footing.
- AWS storage Storage moves to S3 as part of the same platform swap.
Direction
infrastructure
Activity
📝 rainylabs is moving Mike onto a brand-new stack without touching the app 0 commits — infrastructuresecurity draft
A proposed migration would relocate this fork's login, database, and document storage to different vendors - while leaving the actual product code essentially untouched.
Threads of work (detailed view)
rainylabs is moving Mike onto a brand-new stack without touching the app
A proposed migration would relocate this fork's login, database, and document storage to different vendors - while leaving the actual product code essentially untouched.
Pull requests (detailed view)
🟢 Open (1)
by
mosha101 · opened 7d ago