Self-host
Run the full stack on your own infrastructure.
Homaic is AGPL-3.0. The canonical schema is published row-by-row. You can clone the repository, deploy against your own Supabase, point your AI client at it, and run indefinitely — with or without Homaic-the-company. Built to outlive any vendor, including Homaic.
What you get
The same primitives, in your hands.
AGPL license
The full stack — mcp-server, dashboard, marketing, Edge Functions, migrations — under AGPL-3.0. Run it. Modify it. Deploy it. The license guarantees the next person gets the same rights you did.
BYOM portability
Three export formats: PostgreSQL dump, JSON, and CSV. The canonical schema is documented at row-by-row granularity, so a future-you can read the manifest twenty years from now in its native form.
Mode B via MCP
Connect Claude Desktop, Claude Code, Cursor, Cline, or any MCP-aware client to your self-hosted instance. The OAuth + RLS + audit-log surface ships in the open-source core.
Mode A (optional)
Photo-to-asset extraction and other vision-model features require an Anthropic API key — bring your own. Self- hosters who don’t want Mode A can run the rest of the stack without it.
Requirements
- Node.js 20+
- pnpm (workspace package manager)
- Supabase project — the free tier is sufficient for one household
- Anthropic API account — optional; only needed for Mode A
- Vercel, Fly, Railway, or your own server for the Next.js apps
Quick start
Five commands from clone to local dev. Configure your Supabase keys in .env.local before pnpm dev.
git clone https://github.com/homaic/homaic-platform cd homaic-platform cp .env.example .env.local # Fill in SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY pnpm install pnpm db:migrate pnpm dev
Point your AI client at your instance
Mode B (MCP) is the differentiator. Once your stack is up, configure the MCP endpoint in your AI client of choice — Claude Desktop, Claude Code, Cursor, Cline. Authorize the tools your agent should be able to read or write; revoke anytime.
The MCP server URL on a self-hosted instance is https://your-domain/api/mcp. OAuth flow is documented in the repository /docs/mcp.md.
Data portability
Export your manifest anytime in three formats. The export flow is identical on hosted and self-hosted instances; round-trip fidelity is verified by a CI test that exports and re-imports the canonical sample dataset on every PR.
If Homaic-the-company shuts down tomorrow, your self-hosted instance keeps running. If you want to migrate from hosted to self-hosted, export → import → done.
Or skip the operations
Prefer managed hosting? That’s pricing.
Homaic-hosted runs the same stack you would self-host — same license, same export, same portability — with the ops, upgrades, and backups handled. The hosted tier is free during beta.