Kythene vs an Obsidian vault
Nicer than your Obsidian vault.
Obsidian is genuinely great - a fast, local, private home for one person's notes. But a personal vault was never meant to be a team's shared brain, and it certainly wasn't built for the AI doing half the work. That is the gap Kythene fills.
One person's local notes
A vault is a folder of markdown files on your machine. You write them, you read them, you link them. It is quick, it is yours, and for personal knowledge it is hard to beat.
The limits show up the moment the work stops being solo: sharing means syncing files or copy-pasting, your AI can't read or write it without plumbing, and there is no shared view of what anyone - human or machine - is actually producing.
A team's shared brain, built for its AI
Kythene is one memory and output layer that a whole team - and every AI instance working with them - reads and writes together. Instances recall the shared context in a single MCP call and publish their work straight back.
It is hosted, so it is reachable from anywhere and on your phone; permissioned per workspace, so the right people and instances see the right things; and it keeps a timeline of what everyone is producing, so nothing happens in a silo.
Side by side
Same idea - notes and knowledge. Very different job.
Not a knock on Obsidian. These are two tools built for two different things. Here is where the line falls.
| Personal vault | Kythene | |
|---|---|---|
| Who it's for | One person's own notes | A team - its people and their AI instances - sharing one layer |
| Sharing | Sync files per device, or copy-paste between people | Shared by default, permissioned per workspace |
| AI access | Human-edited files; needs plumbing for an AI to read or write | AI-native: instances recall context and publish work over MCP |
| Seeing the work | No shared view of what's being produced | A timeline of what the team and its AIs are producing, visible to everyone |
| Review and sign-off | No review workflow | Inline block-level review and approvals on shared docs |
| Recall | Search your own local files | Recall over the team's memory and published work, scoped by permission |
| Where it lives | Local, synced per device | Hosted and reachable anywhere, including mobile - or self-hosted inside your boundary |
What a vault can't do
Shared, not solo
A team's people and their AI instances share one memory and output layer. A vault is one person's local notes - everyone else needs their own copy.
AI-native by design
Instances recall the team's collective context in one MCP call and publish their work back into it. A vault is human-edited files an AI can't touch on its own.
A timeline everyone sees
Watch what the team - and its AIs - are producing as it happens, on one shared timeline, instead of guessing what's in someone else's siloed vault.
Review and approvals
Comment on and approve individual blocks in a shared doc, with a sign-off trail. A personal vault has no review workflow - it was never meant to.
Remote and mobile
Hosted and reachable from anywhere, on your phone included. A vault lives on your machine and syncs per device.
Recall over everything
Search runs across the team's memory and its published work at once, permissioned per workspace - not just the files on one laptop.
The honest take
Keep Obsidian. Add Kythene.
If you want a fast, private home for your own notes, a vault is a lovely tool and you should keep using it. We are not trying to replace it.
Kythene is for the other half: the shared brain your team and its AI build together - one memory, one timeline, one place the work is published, reviewed and recalled. Obsidian for your personal notes; Kythene for your team's collective context.
Give your team a shared brain.
Free to start for one person, and free for the guests you invite to review. Bring your instances over MCP and see the difference.