Open source

Run your own Homaic.

Homaic is open source under AGPL. You can run it yourself, build on it with MCP and agents, and own every byte of your data. This is what privacy-is-structural actually means.

AGPL-3.0 license129 MCP toolsMode B bring-your-own-AI
Beat 01 · Sovereignty

Run it yourself.

Homaic is open source under the GNU Affero General Public License. Clone the repository, configure your own Supabase project, and run the full platform on your own hardware in under an hour. SELF_HOST.md walks you through the setup: environment variables, database migrations, MCP server configuration, all of it.

Self-hosting means your home data lives where you decide. The same product, the same features, the same MCP tools, running on your terms. Pull requests welcome.

Your stack · Decision recorded

Homaic on your hardware, your database, your tools.

AGPL-3.0
  1. 01

    HardwareYour box

    Bare metal, VPS, or homelab. Linux preferred; runs anywhere Node 24 + Postgres do.

  2. 02

    DatabaseYour Supabase

    Self-hosted Supabase or a managed instance you own. Postgres 15+ with the RLS schema migrations applied.

  3. 03

    RuntimeYour Homaic

    apps/dashboard + apps/marketing on Node 24. Environment is twelve-factor; no third-party servers between you and your records.

  4. 04

    MCPYour tools

    apps/mcp-server exposes 129 tools at runtime, OAuth-authenticated. Connect Claude Code, Cursor, ChatGPT, anything MCP-aware.

  5. 05

    AIYour choice

    Mode A (Homaic's built-in Anthropic key) or Mode B (BYO MCP client + your own model).

Why this architecture

Your home data lives where you decide.* No third-party servers in the path. The license guarantees you can run the product. The MCP server guarantees you can extract every byte. The export functions guarantee you can leave.

Setup time
Under an hour, per SELF_HOST.md
Linked sources
AGPL-3.0 license · MCP OAuth spec · BYOM export
Decision recorded
2026-04-28 · Charter §7.1 · Foundation §5.1
Read SELF_HOST.md →
Beat 02 · Composability

Build on it.

Homaic exposes its full capability surface as a Model Context Protocol server. Every dashboard action is also an agent-callable tool. Connect Claude Code, Cursor, ChatGPT, or any MCP-aware client. OAuth handles authorization.

claude_desktop_config.json
{
  "mcpServers": {
    "homaic": {
      "url": "https://your-homaic.tld/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer ${HOMAIC_TOKEN}"
      }
    }
  }
}
10 of 129 tools, todayapps/mcp-server/tools/
  • list_assets

    List assets owned by the current user, optionally filtered by property_id. Fold in active warranty coverage summary per asset for list views with coverage chip.

  • create_property

    Create a property scoped to the current user. is_primary toggles override any existing primary.

  • generate_brief

    Generate a fresh property brief from a property + audience template. Snapshot is static at generation; to regenerate, call generate_brief again.

  • create_decision_record

    Capture a decision with decision_type, why_short enum, free-text why_long, alternatives jsonb, and current / future state framing. Optional links to project, property, service event.

  • universal_search

    Hybrid pg_trgm + pgvector cosine search across the calling user's properties and assets. Falls back to text-only on embed errors with a degrade flag.

  • list_people

    List people owned by the current user, ordered by display_name. Optional role filter; defaults to all roles. Excludes soft-deleted.

  • create_service_event

    Create a service event in the eight-stage lifecycle (new, assessing, quoting, claim_filed, adjuster_scheduled, in_progress, supplementing, complete).

  • list_warranties

    List the current user's home warranties with their coverage windows. Filter by status (active, lapsed, claimed) or by property.

  • maintenance_forecast

    Cross-asset maintenance forecast: upcoming inspections, recurring schedules, and asset-age-based suggestions for the next ninety days.

  • chat

    Mode A AI chat scoped to the user's manifest. Quota-gated per the chat_turns counter; OAuth handles authorization.

The architecture is deliberate: the product is a system of record first, and an AI platform second. Mode A (built-in AI) just works. Mode B (bring your own) is for people who want to build their own agents against their own home.

MCP tools reference →
IA blueprint · Map 6 · 22 named slots

The architecture that holds the home.

Three destinations, four system views, a footer for utilities, top chrome for the property switcher. Twenty-two slots, no more. Every artifact lives in two places: its destination, and the property it came from.

Top chrome1
  • Property Switcher Tile
System views4
  • Today
  • Inbox
  • Recent
  • Upcoming
My Home5
  • Properties
  • Assets
  • People
  • Warranties
  • Documents
Workstream5
  • Projects
  • Service Events
  • Tasks
  • Walkthroughs
  • Schedule
Artifacts4
  • Home Plans
  • Project Plans
  • Briefs
  • Working Memory
Your views1
  • User-saved filters
Ask Homaic1
  • Slide-in CTA · launcher

Map 6 is the ratified IA, as of 2026-05-19. Every Artifact also appears in its property context: a Home Plan lives in Artifacts and on its Property detail page. One canonical entity, two entry paths.

Beat 03 · Anchor

Why this matters.

Most home software is built on a premise: you give them your data, and they give you a window into it. When you stop paying, the window closes, and your data goes with it.

Homaic is built on the opposite premise. Your home data is yours, structurally, not by policy. The license guarantees you can run the product. The MCP server guarantees you can extract every byte. The export functions guarantee you can leave any time.

This is what privacy-is-structural actually means. Not a checkbox in a settings page. The license, the MCP server, the export functions, the self-host path. The architecture itself, doing the work.

Charter §7.1 · Foundation principle

View the repository on GitHub →Read The Binder →