Deploy
Mike is open source, so you can run it on your own infrastructure and keep your documents inside your perimeter. Pick the path that fits your team. You can also use Mike in the cloud at mikeoss.com.
Enterprise deployment
Rolling Mike out across a firm, into a private cloud or on-premises, or behind your SSO? Talk to the team that builds Mike about your requirements.
Contact usDeploy on Vercel
The quickest way to run your own Mike, with no Docker or servers to manage. One click deploys Mike to your Vercel account with a Supabase project for the database, sign-in and files.
What the button does
- Copies the repository into your Git account and creates a Vercel project.
- Creates a Supabase project through the Vercel Marketplace for the database, sign-in and file storage.
- Builds and deploys the web app, the API and the background worker. There is nothing to fill in.
Once it is live
- Open the production URL as soon as the deployment is ready. A new deployment has no accounts, and its first visitor creates the first one.
- Add a model provider key under Settings > Bring Your Own Keys, or set
ANTHROPIC_API_KEY,OPENAI_API_KEYorGEMINI_API_KEYon the Vercel project and redeploy. - To let colleagues sign up, connect your own SMTP provider in Supabase. The guide walks through it.
Vercel's Services, Container runtime and Daemons, which this deployment uses, are in beta. Request bodies are capped at 4.5 MB (uploads go straight to storage), and background jobs on the Hobby plan have a monthly quota, so use Pro for a team.
Self-host with Docker
Run the full stack on any machine with Git, Docker with the Compose plugin and openssl. Follow the steps below, or hand them to a coding agent such as Claude Code.
Clone the repository
The Docker Compose stack runs Mike, Supabase, object storage and local email capture, with no managed infrastructure to set up.
Terminalgit clone https://github.com/open-legal-products/mike.git cd mike
Copy the environment templates
One file for Compose itself and one for the backend.
Terminalcp .env.example .env cp backend/.env.example backend/.env
Generate the secrets
Run this twice and set
DOWNLOAD_SIGNING_SECRETandUSER_API_KEYS_ENCRYPTION_SECRETinbackend/.envto the two different values.Terminalopenssl rand -hex 32
Add a model provider
Set an Anthropic, Gemini or OpenAI API key in
backend/.env, unless you plan to use Ollama exclusively.backend/.envANTHROPIC_API_KEY=your-anthropic-key
Start the stack
Pin the release in the checkout and run the published images, built once in CI. To build from source instead, run
docker compose up --build.Terminalecho "MIKE_IMAGE_TAG=$(cat VERSION)" >> .env docker compose pull && docker compose up --no-build -d
Open Mike
Go to
http://localhost:3000and create an account. Stop the stack withnpm run stack:down, which also removes the stopped containers.
The bundled credentials and infrastructure are meant for local use. For production, connect managed Supabase and S3-compatible storage as described in the deployment guide (opens in a new tab). Service endpoints and first-run details are in local development (opens in a new tab).