Everything your team knows, finally written down.
Octopedia listens in the channels your team already uses and writes the record for you, as plain markdown you fully own.
Inbox
Entities without outgoing relationships and provisional facts awaiting confirmation.
- Ada LovelacePerson
people/ada-lovelace
Provisional
org=[[?analytical-engines]] - Marie CuriePerson
people/marie-curie
Provisional
org=[[?radium-institute]] - Q3 InfrastructureProject
projects/q3-infrastructure
No outgoing wikilinks yet.
- Standup, May 18Conversation
conversations/standup-may-18
No outgoing wikilinks yet.
People
Everyone your team has met, filed as one markdown entity each.
Projects
Work in flight, with the owner and the next date on every row.
Tasks
Commitments Octopedia noticed in conversation, tracked to done.
- Send the infra leads intro Ada Lovelace in progress
- Draft the Q3 planning agenda Grace Hopper in progress
- Review the merge engine notes Marie Curie done
- Confirm the summit room booking Alan Turing done
- Publish the self-host walkthrough Katherine Johnson todo
Events
What is coming up, gathered from the channels your team uses.
- MAY21 Q3 planning summit
- MAY24 Design partner review
- JUN02 Infra leads introduction
- JUN09 Vault migration dry run
A live, interactive demo. Drag the window by its bar, or watch Octopedia file a fact on its own.
How it works
A second brain that runs itself.
No dashboard to keep up to date, no ritual to maintain. Octopedia turns the talking your team already does into a record that stays current on its own.
Mention it in chat
Talk to Octopedia where your team already works. No new app to learn, no forms to fill. Just say what happened, in the words you would use anyway.
It files the details
Octopedia sorts what matters into structured markdown, a person, a project, an event, and commits it to git. Edits merge cleanly, and nothing gets overwritten.
Recall it in a sentence
Ask later and get a cited answer in milliseconds. Or open the desktop app and browse your knowledge like a quietly well-kept wiki.
Built to be lived in
Fast where it should be invisible.
Careful where it counts, and never in the way of the work itself. One assistant, every channel, a vault you fully own.
Your data
Plain text outlives software.
The vault is not an export feature. It is the product. Human edits and agent edits land as commits, side by side, in a git repository you control.
If Octopedia disappeared tomorrow, your team's knowledge would still be sitting in markdown files, readable in any editor you choose. That is the whole point.
Get started with Octopedia$ git clone teals:acme/vault.git
Cloning into 'vault'... done.
$ tree vault
vault/
people/ 142 entries
projects/ 28 entries
orgs/ 61 entries
events/ 17 entries
_system/schema.yml
AGENTS.mdFrom the blog
Notes on calm software.
Short, considered writing on plain-text knowledge, version control, and building tools that stay out of the way.
Self-hosting Octopedia in about ten minutes
The managed cloud and the self-hosted build are the same artifact. Here is how to bring up the whole stack on hardware you own.
Read the post →How the vault merge engine keeps edits calm
Two people editing the same note should never have to think about a merge conflict. Here is the structured approach that makes that true.
Read the post →Why your team's memory belongs in plain text
Proprietary knowledge tools come and go. Plain markdown in git is a format that will still open long after the tool that wrote it is gone.
Read the post →Get started
Give your team a memory.
Start a vault today. Your future self, trying to remember who said what and when, will quietly thank you.