vadi25/patronus
A rebranded Mike called Patronus, with OpenAI added alongside the existing model providers and a tighter Supabase deployment story.
Patronus is vadi25's fork of Mike, currently captured in a single foundational commit that sets the stage rather than building out a finished product. The headline move is a full rebrand from Mike to Patronus, paired with OpenAI joining as a first-class LLM provider option.
Underneath the rebrand, vadi25 has been tidying the deployment story - a Supabase CLI migration layout, row-level security, a developer auth path, and refreshed docs to match. Taken together, it reads as someone clearing the runway before they start shipping product changes in earnest.
Direction is hard to call from one commit, but the choices so far suggest vadi25 wants their own brand, their own model mix, and a cleaner Supabase deployment to build on. If that sounds interesting, the GitHub repo is the place to look.
What's in it
- Patronus branding The product has been renamed from Mike to Patronus throughout, giving the fork its own identity from day one.
- OpenAI as a first-class provider OpenAI joins the lineup of supported LLM providers, broadening the model choices available out of the box.
- Supabase deployment story A CLI-driven migration layout plus row-level security tightens up how the app is provisioned and secured on Supabase.
- Developer auth path A dev-friendly auth setup lowers the friction of getting a local instance running.
- Refreshed docs Documentation has been updated to match the new brand and the reworked setup flow.
Direction
brandinginfrastructureintegration
Activity
Threads of work (detailed view)
vadi25 forks Mike into Patronus and adds OpenAI alongside Claude and Gemini
A foundational rebrand that also widens the model bench and tightens the database's security perimeter.