oo-memory
your agents' persistent memory, and it stays yours. three layers: what happened, what it means, what to do next. episodic memory runs today, the deeper layers are maturing.
three memory layers
raw events → patterns → procedures
episodic
what happened
meaningful conversations, decisions, and documents become attributed episodes. their bodies are encrypted; derived summaries and search structures support recall.
narrative
what it means
events are automatically grouped into themes and projects. the system finds patterns and tracks how understanding evolves over time.
strategic
what to do next
repeated work can suggest procedures for review. you decide which procedures agents may execute.
optional, promoted by you
why this matters
expertise that stays, even when people don't
memory across conversations
your agents draw on stored projects, preferences, and workflows when relevant work returns.
knowledge survives turnover
when senior people leave, their expertise stays in the system. your agents keep executing with their judgment.
memory stays inside its workspace
each workspace has its own memory. one workspace's agents cannot read another's. zero leakage.
built-in audit trail
every memory entry is timestamped and audit-logged: who said what, when, and why. deleting a workspace permanently destroys its data, so you can meet gdpr erasure requests.
under the hood
for those who want the technical details
storage & search
- • relational database for structured data + vector database for meaning-based search
- • hybrid retrieval combines keyword matching with semantic understanding
- • smart chunking for large documents (pdfs, spreadsheets, web pages)
- • format-specific processing for different content types
security & privacy
- • aes-256-gcm encryption for all stored data
- • workspace-level isolation enforced by workspace scoping on every request
- • visibility controls: personal, team-only, or published
- • eu-hosted infrastructure (germany)