🧬 Digital Memory Server

Your life, secured locally. A fully private, Personal Digital Twin database and lifelogging engine that ensures your digital history belongs entirely to you.

Digital Memory Server is in closed preview. Join the waitlist for early access.

Overview

The Digital Memory Server is the intelligence core of the Companion ecosystem. It runs entirely on your local hardware and acts as a unified personal knowledge base, automatically aggregating data signals from your devices, browser, wearables, and integrated workflows into a single private timeline — your Personal Digital Twin.

Unlike cloud-based memory products, your data never leaves your hardware. The server exposes a local API that Companion Agents query to provide contextually aware suggestions, recall, and guidance.

Key Features

Automatic ingestion — captures data from browser extensions, desktop applet, wearables, and import tools with no manual tagging
Semantic search — full-text and vector-based search across your entire personal history
Timeline view — chronological lifelogging interface with filterable event types
Agent context API — structured endpoints for Companion Agents to query memory with temporal and contextual filters
Private by design — zero telemetry, zero cloud sync unless explicitly configured
Modular connectors — extensible data source plugins for custom integrations

Use Cases

Recall anything you’ve seen, read, or done — without relying on cloud services
Give your local AI agents rich, personal context to improve suggestions and task completion
Build a searchable personal archive of life events, documents, browser history, and media
Maintain a continuous data log from wearables (Mentra Live, Omi, Mentra) for health and memory analysis
Power the Spatial Time Machine and Photogram with structured memory data

Architecture


┌─────────────────────────────────────────────┐
│           Digital Memory Server              │
│                                             │
│  ┌─────────────┐   ┌──────────────────────┐ │
│  │  Ingestion  │   │   Storage Engine     │ │
│  │  Pipeline   │──▶│  (Vector + Relational│ │
│  └─────────────┘   │   + Object Store)    │ │
│         ▲          └──────────┬───────────┘ │
│         │                     │             │
│  ┌──────┴──────────┐   ┌──────▼──────────┐  │
│  │  Source         │   │  Query / Search  │  │
│  │  Connectors     │   │  API             │  │
│  │  (Browser, App, │   │  (REST + MCP)    │  │
│  │   Wearables)    │   └─────────────────┘  │
│  └─────────────────┘                        │
└─────────────────────────────────────────────┘
         │
         ▼
  Companion Agents  ·  Spatial Apps  ·  Photogram  ·  Earth

The server ships as a Docker container managed by Companion Hub. It exposes:

A REST API for data ingestion and retrieval
An MCP (Model Context Protocol) server for direct agent integration
A local web UI for browsing your timeline and configuring connectors

Setup

Install via Companion Hub

Open Companion Hub, navigate to the App Store, and search for Digital Memory Server. Click Install.

Configure data sources

After installation, open the Digital Memory web UI at http://digital-memory.ci.localhost. Navigate to Settings → Connectors and enable the sources you want to capture from:

Browser (requires the Browser Extension)
File system (requires the Desktop Applet)
Wearables (configure in each wearable’s settings page)
Manual import (via Import Tools)

Connect Companion Agents

In the Hub dashboard, open Agents → Context Sources and add your Digital Memory Server endpoint. Agents will automatically query it when generating responses.

(Optional) Configure retention policy

Navigate to Settings → Retention to set data retention windows, storage limits, and automatic pruning rules.

Usage

Searching Your Memory

Use the timeline search bar to query across all ingested data. Supports natural language queries (e.g. “articles I read about AI in March”) as well as exact string search.

Reviewing the Timeline

The Timeline tab shows a chronological feed of all captured events, grouped by day. Use the source filter to narrow by category (browsing, files, wearable captures, imports).

API Access


# Search memory
curl http://digital-memory.ci.localhost/api/search?q=your+query
 
# Ingest a new event
curl -X POST http://digital-memory.ci.localhost/api/events \
  -H "Content-Type: application/json" \
  -d '{"type": "note", "content": "Meeting with team", "timestamp": "2026-04-01T10:00:00Z"}'

Agent Integration (MCP)

Add the Digital Memory MCP server to your local agent configuration:


{
  "mcpServers": {
    "digital-memory": {
      "url": "http://digital-memory.ci.localhost/mcp"
    }
  }
}

Troubleshooting

Ingestion pipeline not running Check the container logs in Companion Hub under the Digital Memory app. Ensure the source connector has the correct API key or token configured.

Search returning no results Indexing runs asynchronously after ingestion. If data was just added, wait a few minutes and try again. If the problem persists, trigger a manual re-index from Settings → Maintenance → Re-index.

High disk usage Navigate to Settings → Storage to see a breakdown by data source. Reduce retention periods or exclude high-volume sources to reclaim space.

Agent not using memory Verify the MCP endpoint is reachable by running curl http://digital-memory.ci.localhost/mcp/health from within the Hub network. Check the agent’s context source configuration.