hoogvliets ↗ analysis ↗ GitHub hoogvliets/mike
A full, deliberate AGPL source disclosure of a heavily production-modified Mike - the most complete public window into what a hardened downstream Mike actually looks like.
This fork is @hoogvliets's open-book disclosure of a production Mike deployment. Rather than merge changes upstream, @hoogvliets published the entire modified application - backend, frontend, database, and infrastructure - to satisfy the upstream project's AGPL-3.0 license. Instead of one unreadable dump, the disclosure is carved into reviewable slices so anyone can evaluate the backend, the data layer, the frontend, or the test suite on its own.
What surfaces through those slices is a Mike that's been meaningfully hardened for real use: multi-provider LLM routing, an account lifecycle with a proper deletion flow, typed configuration, a managed database migration system with row-level security, and a real test suite backed by CI. It reads less like an experiment and more like someone's actual deployment, opened up for inspection.
If you're running or planning your own Mike fork, this is a useful reference - especially for how to evolve the schema over time or stand up test coverage from scratch. It's a disclosure, not a roadmap, so don't expect a rebrand or a niche pitch; expect an honest look at a production-grade build.
What's in it
- Multi-provider LLM routing Backend routing that isn't locked to a single model provider - a sign of a build tuned for real-world flexibility and cost control.
- Account lifecycle & deletion A proper account lifecycle including a user-facing account-deletion flow, the kind of thing production deployments need and prototypes skip.
- Managed database migrations A shift to a managed migration system with row-level security, aimed at evolving the schema safely over time rather than reapplying it wholesale.
- Typed configuration Typed environment handling on the backend - quieter reliability work that pays off when a deployment grows.
- Test suite & CI Real backend test coverage wired into CI, making this the easiest slice to judge for quality and a solid starting point for your own fork's tests.
- Project workflow panels Frontend project panels and workflow additions layered onto a consolidated app structure.
Direction
infrastructuresecurityworkflow
Activity
hoogvliets ↗ analysis ↗ GitHub hoogvliets ↗ analysis ↗ GitHub hoogvliets ↗ analysis ↗ GitHub hoogvliets ↗ analysis ↗ GitHub hoogvliets ↗ analysis ↗ GitHub hoogvliets ↗ analysis ↗ GitHub hoogvliets ↗ analysis ↗ GitHub Threads of work (detailed view)
hoogvliets opens the books on its downstream Mike frontend
An AGPL-compliance disclosure that doubles as a tour of a real, in-use legal-AI interface.
hoogvliets puts the fork's test receipts on the table
As part of an open-source disclosure, hoogvliets carved out the fork's entire backend test suite so reviewers could see exactly how it proves itself.
hoogvliets rebuilds Mike's data layer with tenant walls and a real migration system
A ground-up overhaul of how Mike stores, secures, and versions its data - proposed, but never merged.
hoogvliets opens up a rebuilt Mike backend that upstream wouldn't take
A license-driven code disclosure reveals per-user AI keys, real account deletion, and usage guardrails - none of which the main project accepted.
hoogvliets lays the whole fork open for the maintainer
A license obligation became a full-source disclosure, and what it reveals is a hardened, privacy-minded build.
Test infrastructure slice: Vitest suites, CI workflow, and broad backend coverage
@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 for your own Mike fork from scratch.
Database slice: node-pg-migrate replaces monolithic schema, RLS and lifecycle work added
@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 with how to evolve the upstream schema over time.
Backend hardening slice: multi-provider LLM routing, account lifecycle, typed env
@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 Mike backend looks like without wading through schema and frontend noise.
Frontend slice: app-tree consolidation, new project panels, account deletion UI
@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-deletion banner, and manifest context.
hoogvliets opens a full-fork AGPL disclosure PR against upstream
@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 heavily modified Mike deployment actually looks like.
Pull requests (detailed view)
🟢 Open (5)
hoogvliets · opened 2mo ago hoogvliets · opened 2mo ago hoogvliets · opened 2mo ago hoogvliets · opened 2mo ago hoogvliets · opened 2mo ago ⛔ Closed without merge (5)
hoogvliets · opened 2mo ago · closed 20d ago hoogvliets · opened 2mo ago · closed 20d ago hoogvliets · opened 2mo ago · closed 20d ago hoogvliets · opened 2mo ago · closed 20d ago hoogvliets · opened 2mo ago · closed 20d ago