ecarjat bolts Mike onto a single company's Google logins

This fork turns an open sign-up app into a private, invite-by-domain deployment for one organisation called KairosVista.

securityintegration

ecarjat has rebuilt how people get into Mike. The old email-and-password forms are gone; the only way in is now a "Continue with Google" button. Behind it sits a gate that checks the email address of whoever just signed in and rejects anyone outside an approved company domain - so a stray Google account can't wander in even if it reaches the login page. Deployments that don't want this restriction can leave the gate open, but the KairosVista build ships it switched on and pinned to their own domain.

The sign-in pages have also been reskinned in KairosVista's colours, with the upstream Mike branding stripped out, and the app now reads a user's name and organisation straight from their Google profile so accounts arrive pre-filled rather than blank.

So what Anyone weighing Mike for a single firm or in-house team should look here: it's a worked example of turning the open project into a locked-down, company-only instance.

View this fork on GitHub →

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

Commits in this thread

4 commits from ecarjat/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
a7a41386 Add Google OAuth login Emmanuel Carjat 2026-05-10 ↗ GitHub
13e0a83b Restrict auth to KairosVista Google users Emmanuel Carjat 2026-05-10 ↗ GitHub
786591a2 Match KairosVista auth layout Emmanuel Carjat 2026-05-10 ↗ GitHub
8393b109 Backfill OAuth profiles and reduce audit findings Emmanuel Carjat 2026-05-10 ↗ 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-397.md from inside the repo you want the changes in.

⬇ Download capture-thread-397.md