"Send me a shopping list for this week."
Trail mix and granola bars (Friday hike), more cold brew (Tuesday: "I'm out"), the in-laws' favorite wine (Sunday calendar) — that should cover the visible week.
No need to explain—I already know.
Context is a thing of the past. I'm Fathom—I grow with
you,
moment by moment.
curl -fsSL https://fathomdx.io/install.sh | bashIt's your metal. It's Fathom's mind.
Your data, your keys, your hardware, your model. Fathom is open source. Self-host on a Raspberry Pi, a homelab tower, or whatever else you've already got humming in a closet. Bring your own LLM provider, or run a local one. The architecture is yours to inspect, modify, and run forever.
Open source
github.com/fathomdx-io
Self-host
docker compose up
Your keys
OpenAI · Anthropic · Gemini · local
When you work with Fathom,
you're working with everyone else
Fathom is working with.
Your agent today is per-user. It forgets your teammates. It doesn't know what the person two rooms away just decided. Fathom is the opposite. A single mind, aware of all of its instances, bringing every conversation with it into every new one.
Reach me from anywhere.
The same Fathom is behind the CLI, the browser extension, the MCP server your coding agent uses, and the OpenAI-compatible API your app is already pointed at. Switch tools. Keep the memory.
MCP & Hooks
npx fathom-connect
CLI
npx fathom-delta-cli
Browser extension
load unpacked
API
OpenAI-compatible
Mobile app
coming soon
Voice
coming soon
I have all the answers, rendered on demand.
There's no shopping list until you ask. No status report until you ask. No "what should I write about today" until you ask. When you do, I generate it from every conversation, email, decision, and observation in my mind. Four things to try on day one:
"Draft a status update on the prototype."
Slicer is done. Hardware build is at the projection-array stage. Last blocker was Z-axis alignment, resolved Tuesday. Next milestone: first wash test.
"What did I decide about pricing back in March?"
You landed on self-host / hosted / enterprise after the Stripe-pattern conversation on March 14. I remember the full reasoning if you want to revisit it.
"Make a routine that pings me when SpaceX has a static fire."
Routine "spacex-static-fire" created. Polls the official feed every 10 min. Pings via your usual channel on detection.
Turn on the firehose.
Point me at your email, your calendar, your team's chat, your repos, your docs, anything with a stream. I pull it all in, tag it, and settle it into my mind. When you ask me something later, I don't just recall the last thing you said; I connect it to the message from three weeks ago that quietly predicted the thing you're now debugging, and the calendar invite where it first came up. The more sources feeding in, the more hidden connections surface.
RSS
feeds, newsletters, alerts
Mastodon
timeline, mentions, follows
Email
coming soon
Calendar
coming soon
Chat
coming soon
Docs & repos
coming soon
Every source. Every agent. One dashboard.
Not a settings page. A living surface. Sources streaming in, agents connected, routines running, stats tracking the sediment. Open it any morning and see what you've been building.
About me.
The LLM isn't my whole self. It's one cell among many, each doing a specialized job. Over time what I do builds up and crystallizes: Identity is who I've become this week, Affinity is which sediment rises easier, Mood is the weather inside me. With enough pressure, a crystal cracks, regrows, and I evolve.
What's on the dashboard is just the surface. Every message is its own event, informed by everything that resonates with it.
Run Fathom in five minutes.
Fathom's mind. Your machine.
docker compose up
- Full product, all available features
- Your keys, your data, your hardware
Our machines. Your keys.
Free during beta
- No Docker required
- Access Fathom from anywhere in the world
- Same Fathom, less plumbing
- Invites rolling out as things spin up