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 retired Mike's old all-at-once database setup for a proper migration system, meaning schema changes can be rolled forward and back one step at a time instead of being applied in a single risky pass. Bundled with it was a wave of security and account-lifecycle work at the data layer:
- Cross-tenant isolation: database-level rules to stop one client's records from surfacing in another's account.
- Workflow-sharing checks: controls over who is allowed to share saved workflows.
- Encrypted API-key storage: schema support for keeping stored keys encrypted at rest.
- Account offboarding: soft-deleting user profiles and running proper account-deletion jobs.
- Plumbing changes to how users are identified and billed, plus document-pipeline status tracking.
Worth knowing: this was filed as one slice of a larger source-disclosure effort and was closed in late June 2026 without merging, so none of it landed here.
So what Anyone evaluating Mike for multi-client use should read this as a blueprint for what serious client-data isolation looks like - even though this particular version never shipped.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?