heaventree/mike
heaventree is quietly rebuilding Mike on a Supabase foundation, starting with the data model the upstream project never published.
This fork, run by heaventree, is an early-stage effort to take Mike in a different infrastructure direction. The most visible move so far is a rebuild of Mike's data model targeted at Supabase - work the upstream project hasn't shipped - which suggests heaventree wants a deployment story that doesn't depend on Mike's original backend choices.
Alongside the database work, heaventree has begun restructuring the repository itself, reshaping how the pieces fit together and reworking how environment configuration is organised. There's no new product surface here yet - no new features a user would notice - but the groundwork being laid points at someone planning to host and run their own Mike.
If you're curious about the plumbing rather than the product, this fork is worth a click through. If you're looking for new legal-practice features on top of Mike, it's too early to tell where heaventree is heading.
What's in it
- Supabase-native data model A from-scratch rebuild of Mike's database aimed at Supabase - a deployment path the upstream project doesn't offer out of the box.
- Reworked repository layout The project has been restructured into a unified workspace, the kind of housekeeping that tends to precede bigger changes.
- Refreshed configuration surface Environment and secrets handling has been reorganised, hinting at a self-hosted deployment in mind.
Direction
infrastructureintegration
Activity
Threads of work (detailed view)
heaventree reverse-engineers Mike's database from scratch
A single migration file rebuilds the entire Mike data model for Supabase - a head-start the upstream project never shipped.