A full Docker stack so you can run Mike on your own boxes instead of leaning on hosted cloud services.
osama-ata/mikeoss
A self-hosted take on Mike, packaging the whole stack for teams that want to run it on their own infrastructure.
This fork, maintained by osama-ata, is focused on turning Mike into something you can stand up on your own hardware. Rather than chasing new product features, the work so far has been about deployment: bundling the application and its dependencies so the whole thing comes up locally or on a self-hosted box.
The direction is infrastructure-first. There's an open-source Supabase stack acting as the data and auth layer, with MinIO standing in for S3-compatible object storage - the building blocks of a Mike instance that doesn't need any managed cloud services to run.
It's early, and there's no sign yet of a rebrand or a vertical pitch. If you're curious whether Mike can live entirely inside your own walls, this is a fork worth a click through to GitHub.
What's in it
- Self-hosted deployment A docker-compose setup that brings the whole application up locally, without depending on managed cloud services.
- Open-source Supabase backend Uses the self-hostable Supabase stack - Postgres, auth, and API gateway - as the data layer.
- S3-compatible object storage via MinIO Files and uploads live in a self-hosted MinIO bucket, keeping storage in-house.
- Containerised application services Both the backend and frontend ship as their own containers, ready to run alongside the rest of the stack.
Direction
infrastructure
Activity
Threads of work (detailed view)
osama-ata makes Mike self-hostable in one command
A full Docker stack so you can run Mike on your own boxes instead of leaning on hosted cloud services.