# Hearthloom — A Local-First Personal Second Brain

> Hearthloom is a free, open-source, local-first personal second brain. Email, calendars, messages, photos, health data, code and AI conversations become one knowledge graph in a single file you own: ask it anything, see what's waiting on you, and give your AI agents a memory of you that you control. Rust, MIT licensed.

Source: https://metavert.io/hearthloom  
Published: 2026-11-06  
Updated: 2026-11-06

# Your whole life, one record you own

Hearthloom turns the exhaust of your life — email, calendars, messages, photos, health data, browsing, code and your AI conversations — into one knowledge graph that lives in a single file on your own computer. Ask it anything about your past, let it keep track of what's waiting on you, and give your AI agents a memory of you that stays under your control.

[View on GitHub](https://github.com/metavert-io/hearthloom) [Get a hosted Hearthloom](https://hearthlaunch.com)

Open source (MIT). Local-first. One Rust binary, one SQLite file.

---

## A second brain with no gardening

Most "second brain" tools ask you to file, tag and link everything yourself, and they stop being useful the week you stop. Hearthloom does that work for you. It reads what your life already produces, works out who and what each piece is about, links it into a graph, and keeps every fact tied to the evidence it came from. You never maintain it; at most it asks you a yes-or-no question ("is this the same person?").

- **Everything comes in** Gmail (live, within seconds of arrival, plus a full Takeout archive), calendars, iMessage, Apple Photos (a location trace — never the images), Apple Health, Chrome history, Claude and ChatGPT conversations, Claude Code sessions, git repositories, Facebook and LinkedIn exports, Notion and Markdown vaults (Obsidian, Logseq), Substack — and an iPhone companion that streams health, places, contacts and reminders as they happen. Every import is idempotent: run it again and nothing doubles.
- **Ask Hearthloom** Ask a question in plain English and Hearthloom searches your own record — and the whole of your mail, wherever it's stored across your machines — then answers with citations to the exact emails, messages and events it used. Follow-up questions keep the thread; numbers come back as charts.
- **What's waiting on you** The Desk is the present tense: tasks, notes and goals, and *Waiting on you* — new mail sorted by what it needs from you (a reply, a time, a look), each with the words that decided it. Ask for a reply and Hearthloom writes a draft into your Gmail Drafts — with Google Calendar connected, offering times you're actually free. It never sends anything: you review, edit and send.
- **Private by construction** Your record never needs a cloud. A vault keeps what you mark private locked away unless you open it; privacy rules mark whole topics, senders or places private automatically, and private mail never reaches an AI model. Keys you hand to other tools see only what you grant, and everything that writes to your record is recorded under its own name.
- **A memory for your agents — on your terms** Hearthloom is an MCP server: Claude, Claude Code and any agent that speaks MCP can search, recall and walk your graph, and propose memories for you to approve. When an agent acts for you, every action goes through rules you set — ask first, by default — and anything an agent reads from someone else's words makes it ask before acting.
- **All your machines, one brain** Run it on your laptop, an always-on home machine and a private hosted node, and they stay in sync: write a note on one, find it on the others. Big archives live on the always-on machine, and Ask on any of them can still reach them.
- **See your life** The Galaxy shows the people and projects that bridge the parts of your life; the Atlas maps where you've been over the years; the Loom, Biography, Pulse and Ribbons turn your record into timelines you can scrub through.
- **Embers: extend it** Embers are plugins with permissions you grant at install — your computer presence, your car's drives, your own ideas. Their pages run sandboxed inside the dashboard, and each one's key reaches only what you allowed.

---

## Your Google data

Hearthloom runs on your own machine, or as your own private hosted instance. Gmail connects with an app password you create. If you connect Google Calendar, Hearthloom asks only for read-only access to your free/busy times and the list of your calendars — when you're busy, never what your events are — and uses it only to suggest times you're free in reply drafts you ask for. It reads them when a draft needs them and doesn't store them; the suggested times go to the AI model that writes the draft (your own Claude subscription or AI key), and Hearthloom uses them for nothing else. See the [Metavert privacy policy](https://metavert.io/privacy-policy).

---

## Built with

- **Core:** Rust, axum, SQLite (FTS5 full-text search, sqlite-vec), local ONNX embeddings
- **Interfaces:** a dependency-free web dashboard, a CLI for every feature, an MCP server, an iPhone companion
- **Runs on:** macOS and Linux; self-hosted, or hosted by [Hearthlaunch](https://hearthlaunch.com)

---

## Get started

Clone the repository, run the installer, and open the dashboard: a first-run wizard walks you through your first imports. Or get a private hosted Hearthloom at Hearthlaunch in a few minutes.

[View on GitHub](https://github.com/metavert-io/hearthloom) [Get a hosted Hearthloom](https://hearthlaunch.com)

MIT License · Copyright 2026 Metavert LLC
