jrklaus8 starts pulling Canadian login auth in-house

The mike-Canada fork is moving sign-in off a third-party cloud service and onto its own self-hosted token system, in the name of keeping legal data on home turf.

securitycompliance

The login screen no longer hands credentials to Supabase - a hosted service that startups commonly use for user accounts and authentication. Instead, jrklaus8 points it at the fork's own authentication backend, issuing access tokens locally. The framing is data sovereignty: keeping authentication, and the data behind it, inside infrastructure the fork controls rather than a US-hosted vendor.

Worth a caveat. So far only the login page has been moved - sign-up and the rest of the app still lean on Supabase. That leaves two authentication paths running side by side, which is the kind of half-finished migration that can quietly cause inconsistency. It's a clear statement of direction, but not yet a finished switch.

So what Anyone weighing legal AI tools against Canadian or in-house data-residency requirements should watch whether this fork follows through on a full self-hosted auth stack.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from jrklaus8/mike-Canada, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5061e2d7 feat: Replace Supabase with Local JWT for LSO Data Sovereignty on Login Page MikeOSS Bot 2026-05-22 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-540.md from inside the repo you want the changes in.

⬇ Download capture-thread-540.md