📝 Frontend lint cleanups surfaced by new CI (no public page) 1 commit 12d ago not yet rewritten
amaingot/mike-aws
amaingot is rebuilding Mike on AWS-native infrastructure, swapping out the original Cloudflare and Supabase foundations for an Amazon stack.
This fork takes Mike, the open-source legal assistant, and re-platforms it onto AWS. If you tried it today, you'd be running essentially the same product as upstream, but deployed against Amazon's services instead of the Cloudflare and Supabase pieces the original is built on.
amaingot is the sole hand on the wheel so far. Beyond the infrastructure swap, they've also turned on continuous integration for the frontend and worked through the lint errors that surfaced once the linter started running in CI - housekeeping that came along for the ride with the re-platform.
The direction is clear and narrow: make Mike deployable for teams that live inside AWS. There's no rebrand, no new feature pitch, no shift in audience - just a different cloud underneath. If you're an AWS shop curious about running Mike on your own infrastructure, this is the fork to watch.
What's in it
- AWS-native deployment The whole stack has been moved off Cloudflare and Supabase and onto Amazon's equivalents, making this the fork to start from if your infrastructure already lives in AWS.
- CI on the frontend Linting now runs automatically on the frontend, and the backlog of issues it surfaced has been cleared - a small quality-of-life win for anyone who wants to contribute.
Direction
infrastructure
Activity
A single, sweeping commit re-platforms the entire stack from Cloudflare and Supabase onto AWS-native services.
Threads of work (detailed view)
amaingot lifts Mike onto AWS
A single, sweeping commit re-platforms the entire stack from Cloudflare and Supabase onto AWS-native services.