⚖MikeWatch Forks of the Mike legal-AI codebase, distilled for legal-tech readers
Home · LegalAIDev/mike

LegalAIDev/mike

A LegalAIDev-maintained fork of Mike focused on getting the app reliably deployed on Railway's hosting platform.

Light activity - a small cluster of deployment and dependency fixes in late April, with no pushes since.

View on GitHub →

This is LegalAIDev's fork of Mike. So far, the visible work isn't about new legal-tech features - it's about keeping the app shippable. The handful of changes on record are deployment-plumbing fixes and a security-driven dependency bump, several of them landed by Railway's own automation bot rather than a human contributor.

If you tried this fork today, you'd find something that looks and behaves very much like upstream Mike. The interesting story here is infrastructure: LegalAIDev appears to be running Mike on Railway and is working through the friction that comes with that - builder migrations, deprecated package versions, CVE patches. There's no rebrand, no obvious niche, no new product direction yet.

Whether that changes is an open question. For now, this reads as someone standing the app up in their own environment rather than reshaping it. Click through to GitHub if you want to see the deployment setup in detail.

What's in it

Direction

infrastructuresecurity

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 Next.js 16.0.3 → 16.2.4 upgrade (CVE-2025-66478) (no public page) 4 commits 27d ago not yet rewritten
📝 Switch backend builder from Nixpacks to Railpack (no public page) 1 commit 27d ago not yet rewritten
📝 Backend deploy config migrated from Nixpacks to Railpack (no public page) 2 commits 27d ago not yet rewritten

Pull requests (detailed view)

3 PRs touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

✅ Merged (3)