manueljpconde/mikeEU

EU-focused Mike fork targeting sovereign deployment with Docker self-hosting, local LLM support, managed model endpoints, and five-language UI

Active development across infrastructure, security, and localization. Major additions: Docker Compose self-hosting stack (with subsequent hardening including a `SUPABASE_SECRET_KEY` frontend-leak fix and image pinning), per-admin managed model endpoints with encrypted key storage, a server-configured local LLM provider, a full five-locale i18n system with catalog validation tooling, and a security patch closing cross-tenant document reads on tabular review endpoints.

View on GitHub →

manueljpconde/mikeEU is a fork of the willchen96/mike legal-AI codebase shaped for EU deployment scenarios where data sovereignty and self-hosting matter. The main lines of work are: a full Docker Compose stack that boots the entire application locally without external Supabase or R2 accounts; a local:server provider that routes inference to any OpenAI-compatible endpoint (Ollama, LM Studio, vLLM) with credentials kept server-side; a managedModels subsystem that lets admins configure per-user Azure Foundry or local model endpoints with AES-256-GCM-encrypted keys; a five-locale UI (en, pt, es, fr, de) built on a custom library-free i18n runtime; and a confirmed cross-tenant document access fix on the tabular review routes.

The openaiCompatible adapter, managed models schema, and encryption helpers are the most portable pieces - worth evaluating independently of the Docker and i18n work. The cross-tenant access fix applies to anyone running tabular review features. The Docker stack is opinionated: it bundles a local Supabase cluster rather than pointing at hosted, so it only makes sense if you want the full self-host story.

What's in it

Direction

infrastructurei18nsecurity

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.

📝 Gitignore local AI agent configs 3 commits 2mo ago minor change
📝 Document managed vs public model setup paths 1 commit 2mo ago minor change
📝 Cross-tenant document read closed on tabular review routes 0 commits securitymulti-tenant draft
manueljpconde patched a confirmed authorization gap in the tabular review feature: authenticated users could submit another user's document IDs and the backend would read and forward that content to the LLM. A new helper…

Threads of work (detailed view)

17 threads have been distilled into posts.

i18n second pass covers assistant chrome, projects, tabular reviews, and workflows

After the initial i18n rollout left high-traffic lawyer-facing screens partly in English, manueljpconde pushed a second pass that expands translation coverage across account settings, the chat assistant surface, tabular reviews, project modals, and workflow lists - all five supported locales updated.

Docker Compose stack and admin-managed model endpoints land together

manueljpconde shipped a self-contained local deployment stack alongside a new `managedModels` subsystem that lets admins configure OpenAI-compatible model endpoints stored in the database with AES-256-GCM-encrypted API keys. These two changes arrived in the same PR and a three-day hardening follow-up.

Docker quickstart hardened: secret leak fixed, JWTs refreshed, images pinned

manueljpconde tightened four loose ends in the Docker setup that had shipped with the initial compose stack: a server-only credential was leaking into the Next.js build context, development JWTs were due to expire in 2027, image tags were floating on `latest`, and the Linux Docker networking story was undocumented.

Five-locale UI ships with custom i18n runtime and profile-persisted locale

manueljpconde built end-to-end localization for en, pt, es, fr, and de from scratch - no third-party library, just a thin layer over native `Intl`. Locale is stored on the user profile, validated at every layer, and resolved server-side on the initial request.

Self-contained Docker stack and per-user managed model endpoints

manueljpconde landed the two biggest infrastructure changes in the mikeEU fork at once: a Docker Compose setup that boots the entire stack locally without hosted Supabase or R2, and a redesigned model settings flow that lets each admin configure their own Azure Foundry or local OpenAI-compatible endpoint with a per-record encrypted key.

Self-hosted local LLM provider added as a fourth inference path

manueljpconde added a `local:server` provider to mikeEU that routes inference to any OpenAI-compatible `/v1/chat/completions` endpoint - Ollama, LM Studio, vLLM, and similar runtimes. Configuration is entirely server-side; the browser only sees a selectable model name.

Local LLM provider added via server-configured OpenAI-compatible endpoint

manueljpconde wired a fourth inference path into mikeEU: a backend-only `local:server` provider that routes to any OpenAI-compatible `/v1/chat/completions` endpoint. Ollama, LM Studio, and similar runtimes work out of the box. The browser never sees the URL or credentials.

Cross-tenant document read closed on tabular review routes

manueljpconde patched a confirmed authorization gap in the tabular review feature: authenticated users could submit another user's document IDs and the backend would read and forward that content to the LLM. A new helper now validates document ownership on every affected call site before anything is read.

Pull requests (detailed view)

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

✅ Merged (7)