Your AI forgets.
Lodestone remembers.
Lodestone keeps a private memory of your work with AI: the decisions, the background and the way you like things done. Every AI app you use can draw on it, so you never have to explain things again. Share it with the people you choose, or publish what you know for anyone to follow.
- Saves your sessions
- Sums them up as short notes
- Brings them back when needed
You're trusting us with your memories. Here's how we keep them safe.
That trust is a responsibility, not a feature, and it shapes every decision we make: what we store, who can see it, and how easily you can take it all back.
Secrets stripped on your machine
Known secret formats (API keys, tokens, passwords in links) are removed on your device before anything is stored.
Encrypted in transit, secrets at rest
HTTPS only in transit. Lodestone Cloud encrypts your tokens, keys and backups; a key per account for your memory comes in Phase 1.
You decide who sees what
Each device gets its own key, limited to what you choose. Nothing is shared unless you share it, and you can switch any of it off in one click.
No one at Lodestone reads it
Self-hosted, it never touches our servers. In Cloud, nobody at Lodestone reads it, and if we ever need to look, we ask you first.
Your context is scattered, and none of it is yours.
Every chat starts from zero
You explain the project, the decisions and your preferences again, in every new chat and every new session.
Memory is stuck in one app
What Claude learns in the browser is invisible to your other apps, your other account and your work laptop.
Lose the account, lose the history
When an app, an account or a laptop goes away, months of context go with it. There's no copy you control.
It saves, it sums up, it remembers.
You don't have to tell your AI to remember things. Lodestone keeps up as you work, so nothing depends on anyone's good habits.
Saves your sessions
Claude Code sessions are saved automatically as you work. Your claude.ai chats come in from claude.ai's data export. Passwords and keys are removed before anything is stored.
Sums them up
Each session becomes a few short notes: facts, decisions, your preferences, and where each project stands. When something changes, the old note is kept and marked out of date, and every note shows where it came from.
Brings it back
Ask any of your AI apps about a project and it catches up from your notes in seconds. When nothing relevant is there, it says so instead of guessing.
The same Lodestone. You choose who runs it.
Self-hosted
Free
Run it on your own computer or server. For people comfortable with a terminal: bring your own git repo and your own AI model for the summaries.
- Everything: the server, automatic saving and the web app
- Runs on a laptop, a VPS or Railway
- Summaries with your Claude subscription, the API or a local model
- Shares with every other Lodestone, hosted or not
Lodestone Cloud
From $5 a month
The memory, without running a server. We look after hosting, upgrades, backups and security.
- Your own private Lodestone, ready in minutes
- Connect claude.ai and Claude Code without opening a terminal
- Summaries on your computer, or on our server with your own API key
- Take all of it with you, or move to self-hosting, at any time
Plain files, an open protocol, nothing hidden.
For engineers: your memory is a git repo of Markdown files, served to any MCP client. Here's what that means in practice.
---
namespace: proj/lodestone
kind: decision
title: Railway hosts the MCP server
status: active
created: 2026-10-05T12:01:42+00:00
sources:
- archive/claude-code/macbook/2026/10/0c1f….jsonl#msg-41
- archive/claude-code/macbook/2026/10/0c1f….jsonl#msg-44
---
Deployed from main with the Dockerfile. A volume mounted at
/data holds the data clone, the index and the model cache.
Why: one always-on endpoint every client can reach.lodestone-memory/
├── archive/ # every transcript and artifact, append-only
├── memory/ # distilled notes, one subject per file
│ ├── me/preferences/
│ └── proj/lodestone/{facts,decisions,threads}/
├── digests/ # one line per session, per day
└── config/ # namespaces, relations, sharesWorks with every MCP client
Local over stdio, or remote over HTTPS with OAuth, so claude.ai, Codex and others connect from web, desktop and phone. Agents call context to catch up on a project in about 2k tokens, or recall to search everything.
Files are the source of truth
The archive is append-only, notes are versioned by git, and the search index is a cache you can rebuild at any time. No proprietary database to lose.
Search that knows when to stop
SQLite full-text search plus local embeddings, merged and filtered by relevance thresholds you can tune live. Distilled notes rank above raw transcripts.
A token per device, scoped
Give your work laptop access to proj/acme and nothing personal. Read-only or read-write, revocable in one click. Tokens are stored hashed.
Federation over an open protocol
Servers share with each other over the Carrick Protocol, an open standard. A peer's shared notes show up in your recall, labelled with their name; publications are pinned releases any MCP client can read.
Nothing fails silently
Health checks for storage, push access and sync run at startup and after every sync. While data is at risk, writes are refused with the reason, not silently lost.
Frequently asked
Do I need to be technical?
Which AI apps does Lodestone work with?
Where does my data live?
Can anyone else read my memories?
What happens when I share or publish?
What model writes the notes?
Will self-hosting stay free?
Can I move between Cloud and self-hosting?
What about passwords and keys in my chats?
[REDACTED:<type>]. You can add your own patterns.Give your AI a memory you own.
We'll look after it as if it were our own.