PasqualeMuraca packages Mike to run on your own servers

A self-hosting kit that lets a firm stand up the whole platform in-house instead of relying on someone else's cloud.

infrastructure

PasqualeMuraca has bundled Mike into Docker - a packaging tool that wraps an application and everything it needs into containers that run the same way on any machine. The result is a one-command starting point: the front end won't even boot until the back end reports healthy, and every secret the platform needs is laid out in a single documented template, so there's no guessing about which keys and credentials are required.

It's deliberately a starting point, not a finished product. There's no bundled database (the platform still expects an external one) and no built-in encryption layer for traffic from the outside world, so a firm adopting this would need to add its own. Even teams that never touch Docker get value from the secrets checklist as plain documentation of what running Mike actually takes.

So what Worth a look for any legal team that wants to keep a legal-AI platform on infrastructure it controls rather than a vendor's cloud.

View this fork on GitHub →

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

Commits in this thread

7 commits from PasqualeMuraca/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
a1b3ea05 Add Docker configuration for backend (Express) Pasquale Muraca 2026-05-13 ↗ GitHub
1d7e7196 Add Docker configuration for frontend (Next.js) Pasquale Muraca 2026-05-13 ↗ GitHub
4865d746 Add docker-compose orchestration for Mike platform Pasquale Muraca 2026-05-13 ↗ GitHub
30a17154 Add Docker environment variables template Pasquale Muraca 2026-05-13 ↗ GitHub
5aa62ed6 Add Docker ignore patterns Pasquale Muraca 2026-05-13 ↗ GitHub
f3e2a1ed Add Docker deployment guide Pasquale Muraca 2026-05-13 ↗ GitHub
70aaf0c2 Pass Supabase env vars to frontend Docker build Pasquale Muraca 2026-05-13 ↗ GitHub
commit body
Add NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY as build-time ARGs in Dockerfile.frontend and export them as ENV so the frontend build can embed Supabase configuration. Update docker-compose.yml to forward those build args with fallback defaults. Also remove the explicit compose version declaration at the top of docker-compose.yml.

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

⬇ Download capture-thread-427.md