Lina Law Firm rebrands Mike and ships it to Google Cloud Run

A working law firm has taken the open-source Mike, stamped its own name on it, and packaged it to run as a private cloud service.

infrastructurebranding

Lina Law Firm has packaged the Mike codebase to run on Google Cloud Run, Google's pay-as-you-go hosting that spins up only when someone uses it. Part of that work teaches the system to turn Word documents into PDFs on the fly - handy for any firm that drafts in DOCX and sends in PDF.

The other half is making Mike theirs. Every "Mike" in the assistant's instructions, its log lines, and the author name on its tracked changes has become "Lina," so edits land under the firm's own brand rather than the upstream project's. They have also walled their data into its own section of a shared database, letting Mike's tables sit alongside another application's without the two stepping on each other.

So what Worth a look if you are weighing whether to stand up a private, branded instance of Mike for your own practice instead of borrowing someone else's.

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

Commits in this thread

1 commit from Lina-Law-Firm/mikeoss, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`79e39f56`	chore: Cloud Run packaging + pending backend working-tree changes	nipanon	2026-06-05	↗ GitHub
commit body Add backend Dockerfile/.dockerignore/.gcloudignore for Cloud Run, the mike-schema migration (schema.mike.sql) and the mike-schema redirect in the Supabase client, plus assorted small in-progress backend edits already running in the deployed revision. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

SHA

Subject

Author

Date

79e39f56

chore: Cloud Run packaging + pending backend working-tree changes

nipanon

2026-06-05

↗ GitHub

commit body

Add backend Dockerfile/.dockerignore/.gcloudignore for Cloud Run, the
mike-schema migration (schema.mike.sql) and the mike-schema redirect in the
Supabase client, plus assorted small in-progress backend edits already
running in the deployed revision.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

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-630.md from inside the repo you want the changes in.