hoogvliets/mike

A privacy-minded, production-shaped Mike deployment with stronger accounts, project workflows, and tenant-aware data handling.

The tracked work is substantial, but with no commits ahead and no push since May 2026, current momentum appears paused.

View on GitHub →

@hoogvliets has disclosed a substantially adapted Mike application, presented as a real legal-AI interface rather than a small cosmetic variation. Visitors would encounter account and profile handling, project-focused workspaces, and support for routing work across AI providers.

The direction is pragmatic hardening: stronger account lifecycle controls, including deletion, per-user AI-key handling, usage guardrails, and clearer separation between customers' data. hoogvliets has also made the work unusually inspectable through a broad public disclosure and focused review slices for those who want to explore it on GitHub.

What's in it

Project-oriented workspace Organises work around projects, with dedicated panels and shared application context.
Account lifecycle controls Includes profile and authentication handling alongside a visible route for account deletion.
Per-user AI access Emphasises individual AI-provider credentials and guardrails around usage.
Tenant-aware data protection Treats separation between users' data as a first-class concern.
Operationally hardened service Pairs the user-facing product with stronger backend safeguards and a more managed approach to evolving data.

Direction

securitymulti-tenantworkflow

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.

⛔ #131 Disclose backend hardening and route changes +9,750 -5,851 4mo ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates backend hardening and route changes for easier review.

⛔ #130 Disclose database migrations and Supabase config +4,937 -517 4mo ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates database migration and Supabase configuration changes for easier review.

⛔ #129 Disclose backend test coverage and CI workflow +11,471 -143 4mo ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates backend test coverage and CI additions for easier review.

⛔ #128 Disclose frontend app and project workflow updates +4,295 -6,166 4mo ago by hoogvliets ↗ analysis ↗ GitHub

Part of the downstream AGPL disclosure. This PR isolates the frontend app and project workflow changes for easier review.

⛔ #127 Disclose downstream AGPL changes +25,156 -12,156 4mo ago by hoogvliets ↗ analysis ↗ GitHub

This PR discloses the complete downstream source changes made to this AGPL-3.0 project. It is intentionally broad so the original maintainer can inspect the full modified codebase in one place. Smaller topic PRs are also…

📝 hoogvliets opens a full-fork AGPL disclosure PR against upstream 0 commits — infrastructuresecurity draft

@hoogvliets has filed a single umbrella PR against willchen96/mike exposing an entire production-modified codebase. It's an AGPL source disclosure, not a merge request - but it's the most complete window into what a heav…

📝 Frontend slice: app-tree consolidation, new project panels, account deletion UI 0 commits — chat-uiworkflow draft

@hoogvliets isolated the frontend changes from backend and database work into a standalone AGPL disclosure slice. The structural core is an app-tree consolidation; the surface additions include project panels, an account…

📝 Backend hardening slice: multi-provider LLM routing, account lifecycle, typed env 0 commits — infrastructuresecurity draft

@hoogvliets carved the backend out of a larger AGPL disclosure into its own PR - server-side hardening, account lifecycle, and LLM routing as a reviewable unit. Useful if you want to understand what a production-hardened…

📝 Database slice: node-pg-migrate replaces monolithic schema, RLS and lifecycle work added 0 commits — multi-tenantinfrastructure draft

@hoogvliets carved the data layer out of a larger disclosure into a standalone PR. The main move is a shift from a one-shot schema apply to a managed `node-pg-migrate` system - worth evaluating if you've been wrestling w…

📝 Test infrastructure slice: Vitest suites, CI workflow, and broad backend coverage 0 commits — infrastructurecompliance draft

@hoogvliets isolated the test additions from the backend source changes they exercise, making this the easiest slice to evaluate for test quality. It's also the most useful reference if you're standing up a test suite fo…

Threads of work (detailed view)

5 threads have been distilled into posts.

Pull requests (detailed view)

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