📝 README and project documentation churn (no public page) 12 commits 3d ago not yet rewritten
Dshamir/AI-Legal
A rebrand of Mike into AI-Legal: a self-hostable, multi-tenant legal-AI platform a firm can run on its own servers.
AI-Legal is Dshamir's reframing of Mike from a cloud-dependent prototype into a platform you can stand up in-house. The headline move is independence: the fork packages the app as a turnkey, self-hosted stack and cuts its reliance on a single hosting vendor, so a firm can run it on standard infrastructure - with an optionally air-gapped deployment in the longer-term plan. The documentation and roadmap have been rewritten around this platform vision rather than a single-server demo.
Dshamir is also building toward running AI-Legal as a metered, paid service: per-user credit limits and portable workflows that move between instances point at a multi-tenant, commercial future. A lot of the work so far is the unglamorous foundation that makes that credible - security hardening front and back, request validation, login enforcement, crash reporting, caching, zero-downtime key rotation, a test suite, and CI.
If you're curious whether this is something your firm could host itself, it's worth clicking through to GitHub. The shape here is a serious self-hosting and infrastructure effort, not a cosmetic rename.
What's in it
- Self-hosted deployment Packaged as a turnkey stack a firm can stand up on its own servers instead of depending on the upstream cloud.
- Vendor independence The backend was reworked to drop its lock-in to one hosting vendor, so it can run against a standard database.
- Metered, multi-tenant service Per-user credit limits and importable/exportable workflows lay the plumbing for running AI-Legal as a paid, multi-user product.
- Security hardening Login enforcement, request validation, content-security policy, error tracking, and cherry-picked upstream security fixes across the front and back end.
- Operational resilience Caching and the ability to rotate the encryption protecting stored API keys without taking the service offline.
- Quality gate A test harness and continuous-integration pipeline so changes are checked before they land.
Direction
infrastructuresecuritymulti-tenant
Activity
📝 Dshamir builds the plumbing to run Mike as a metered service 2 commits 3d ago workflowmulti-tenant draft
Two new features point at a paid, multi-tenant future: per-user credit limits and workflows you can carry between instances.
📝 Dshamir is quietly closing the security holes everyone else inherited 4 commits 3d ago securityinfrastructure draft
A run spent cherry-picking upstream security fixes - including a way to hijack the AI through a booby-trapped filename.
📝 Dshamir makes AI-Legal something you can run on your own servers 13 commits 3d ago infrastructure draft
This fork turns the cloud-dependent upstream into a turnkey package a firm can stand up in-house.
📝 Testing harness and GitHub Actions CI (no public page) 7 commits 3d ago not yet rewritten
📝 Dshamir sketches Mike's path from prototype to platform 4 commits 3d ago infrastructureintegration draft
A set of planning documents lays out how this fork could grow from a single-server prototype into a scalable, extensible, optionally air-gapped system.
A round of frontend hardening adds login enforcement, crash reporting, and a basic accessibility win to the fork's web app.
📝 Dshamir quietly bolsters the plumbing - and lets stored keys rotate without downtime 3 commits 3d ago securityinfrastructure draft
Three small backend additions, but the one that matters lets the team swap the encryption protecting users' stored API keys without ever taking the service offline.
The fork's biggest backend change rips out its dependence on one hosting vendor so the app can run on any standard database.
Six commits turn the fork's request handling into something you'd actually trust with client files.
Threads of work (detailed view)
Dshamir builds the plumbing to run Mike as a metered service
Two new features point at a paid, multi-tenant future: per-user credit limits and workflows you can carry between instances.
Dshamir is quietly closing the security holes everyone else inherited
A run spent cherry-picking upstream security fixes - including a way to hijack the AI through a booby-trapped filename.
Dshamir makes AI-Legal something you can run on your own servers
This fork turns the cloud-dependent upstream into a turnkey package a firm can stand up in-house.
Dshamir sketches Mike's path from prototype to platform
A set of planning documents lays out how this fork could grow from a single-server prototype into a scalable, extensible, optionally air-gapped system.
Dshamir bolts down the front end of AI-Legal
A round of frontend hardening adds login enforcement, crash reporting, and a basic accessibility win to the fork's web app.
Dshamir quietly bolsters the plumbing - and lets stored keys rotate without downtime
Three small backend additions, but the one that matters lets the team swap the encryption protecting users' stored API keys without ever taking the service offline.
Dshamir is cutting the cord with Supabase
The fork's biggest backend change rips out its dependence on one hosting vendor so the app can run on any standard database.
Dshamir bolts a security layer onto the back door
Six commits turn the fork's request handling into something you'd actually trust with client files.