elitan wants to pull elitan/mike's whole backend in-house
A proposed re-platforming that trades hosted services for a stack the operator runs and controls directly.
elitan sketched out a wholesale rebuild of the fork's plumbing, aimed at cutting reliance on managed cloud services and remote AI. Three moves stand out:
- Self-managed login and data: swapping a hosted backend service for authentication and database access the operator runs themselves, keeping user and matter data on their own infrastructure.
- Local AI models: adding the option to run the AI on machines the operator controls, rather than depending solely on remote providers.
- Consolidated server logic: folding the backend into the web framework itself, so there are fewer separate moving parts to host and maintain.
Worth flagging: this was posted as a snapshot of elitan's own branch and closed within seconds, so none of it is live. It reads as a direction, not a finished feature.
So what Worth a look for teams weighing whether to keep legal data and AI entirely on infrastructure they own instead of hosted services.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?