Self-hosting Homaic

What it takes to run Homaic on your own infrastructure, how to point your MCP client at it, and how to keep it updated.

Homaic is AGPL-licensed open source. You can run the entire platform on your own infrastructure — your data never leaves your hardware, your AI calls run against your keys, your MCP clients connect directly to your host. No Homaic account required.

This is real. Not a freemium-tier marketing footnote.

Requirements

Quick start

git clone https://github.com/homaic/homaic-platform
cd homaic-platform
cp .env.example .env
# edit .env — set DATABASE_URL, NEXTAUTH_URL, optional ANTHROPIC_API_KEY
pnpm install
pnpm db:migrate
pnpm build
pnpm start

Full setup, including a Docker Compose file with a bundled Postgres, lives in the repo README.md and docs/self-hosting/. The maintained path is Docker Compose; bare-metal Node is supported but expects you to know what you're doing.

Pointing your MCP client at your host

Same OAuth flow as Homaic-hosted, different URL. In Claude Code, Cursor, or Cline, set the MCP server URL to https://your-host.example.com/mcp. The OAuth flow runs against your self-hosted instance; the bearer token is stored by your client.

If you've been running Homaic-hosted and you migrate, run an export (Exporting your data), import it into your self-hosted instance, and re-authenticate your MCP client against the new URL.

What you give up

What you keep

Keeping your instance updated

cd homaic-platform
git pull
pnpm install
pnpm db:migrate
pnpm build
# restart your process manager (systemd, pm2, docker compose up -d)

Subscribe to release notes via GitHub watch, or follow the status page for advisories that affect self-hosted users.

Where to go next