heaventree/mike

heaventree is quietly rebuilding Mike on a Supabase foundation, starting with the data model the upstream project never published.

Early days - two distinct threads of work over a handful of commits, with the most recent push just before this fork was first noticed.

View on GitHub →

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

Direction

infrastructureintegration

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.

📝 Root monorepo wrapper and Supabase env-var rename (no public page) 2 commits 7d ago not yet rewritten

Threads of work (detailed view)

1 thread have been distilled into posts.