Glyph Hold dashboard preview showing memories, encrypted secrets, API keys, and audit events
Beta now, moving quickly

Glyph Hold

A self-hosted memory and secrets service for AI agents. Keep durable context, encrypted credentials, API keys, and audit history under your control.

No hosted AI
No LLM calls, embeddings, vector DBs, or paid APIs inside Glyph Hold.
Agent ready
HTTP API, API keys, MCP connector, and deterministic SQLite FTS5 search.

Glyph Hold gives agents a shared place to remember the things that should survive the current chat: project context, procedures, preferences, decisions, and secrets that should only be revealed when explicitly requested.

Follow the beta on GitHub

Why It Exists

Memory that stays local, searchable, and inspectable.

Agents are useful when they remember stable context. Glyph Hold keeps that memory separate from the model, visible in a dashboard, and reachable through a simple API.

Durable memories

Store notes, decisions, procedures, project facts, people, preferences, and temporary context with categories, tags, confidence, and revision history.

Encrypted secrets

Store operational secrets encrypted at rest and reveal values only through explicit reveal endpoints. Secret values stay out of memory prefetch.

Agent access

Create scoped API keys from the dashboard, then connect agents over HTTP or through the standalone Glyph Hold MCP server.

Simple self-hosting

Run it with Docker on port 5995. Data lives in SQLite, search uses SQLite FTS5, and the dashboard handles first-run setup.

Current Status

Beta software, usable today, improving fast.

Glyph Hold is already suitable for local agent memory experiments and practical self-hosted use. It is still beta, so keep backups of the mounted data directory and encryption key before upgrading.

Docker image Web dashboard API keys Memory revisions Secret reveal controls MCP connector

Install

Run Glyph Hold with Docker.

Start locally, create the first dashboard account, then generate an API key for your agent.

One-line start

GLYPHHOLD_KEY="$(openssl rand -hex 32)" && docker run -d --name glyphhold --restart unless-stopped -p 5995:5995 -v glyphhold-data:/data -e GLYPHHOLD_DB_PATH=/data/glyphhold.sqlite -e GLYPHHOLD_ENCRYPTION_KEY="$GLYPHHOLD_KEY" ghcr.io/dosk3n/glyphhold:0.2.0-beta && printf 'Save this Glyph Hold encryption key: %s\n' "$GLYPHHOLD_KEY"

Docker Compose

services:
  glyphhold:
    image: ghcr.io/dosk3n/glyphhold:0.2.0-beta
    container_name: glyphhold
    ports:
      - "5995:5995"
    volumes:
      - ./data:/data
    environment:
      GLYPHHOLD_DB_PATH: /data/glyphhold.sqlite
      GLYPHHOLD_ENCRYPTION_KEY: change-this-to-a-long-random-value
    restart: unless-stopped
  1. Open http://localhost:5995.
  2. Create the first dashboard username and password.
  3. Create an agent API key from the dashboard.
  4. Connect your agent directly over HTTP or through MCP.

MCP Connector

Use Glyph Hold from Codex and other MCP clients.

The standalone MCP repo connects to Glyph Hold through the public HTTP API. It can search memories, prefetch context, create and update memory, restore revisions, manage secret metadata, and reveal secret values only when explicitly requested.

Roadmap

What is coming next.

Now

Beta releases, Docker setup, dashboard, memories, secrets, API keys, MCP.

Next

More polish, stronger recovery flows, clearer docs, and broader agent examples.

Then

A stable v1 for people who want dependable self-hosted memory for agents.