Unified Agent Memory: Server Service Map

Companion note for unified-agent-memory-fabric.

server Service Map

The server server runs far more than just the memory fabric. Here is the full landscape and how the agent infrastructure fits within it.

graph TB
    subgraph "Agent Memory Fabric"
        CDB[CouchDB]
        LS[LiveSync Daemon]
        FS[Vault Filesystem]
        GB[gbrain MCP]
        M0[mem0 API]
        M0D[mem0 Dashboard]
        HMC[hermes-mcp Gateway]
    end

    subgraph "Authentication"
        AK[authentik SSO]
        AKP[authentik Postgres]
        AKR[authentik Redis]
    end

    subgraph "Supabase Stack"
        SDB[(Supabase PG 15)]
        SK[Kong API Gateway]
        SA[GoTrue Auth]
        SR[PostgREST REST]
        SRL[Realtime]
        SML[Meta]
        SEF[Edge Functions]
        SSP[Storage]
        SIM[imgproxy]
        SLF[Logflare]
        SVD[Vector]
        SUI[Studio]
        SPL[PgBouncer Pooler]
    end

    subgraph "Services"
        N8N[n8n Automation]
        CHD[Change Detection]
        MFS[Meilisearch Search]
        MFU[Meilisearch UI]
        PLP[Paperclip + PG 17]
        PLL[Pillow API]
        CVX[ConvertX]
        SPDF[Stirling PDF]
        SXNG[SearXNG Meta Search]
        UM[Umami Analytics]
        UMD[Umami DB]
        MINIO[S3 Storage]
        IMP[imgproxy]
        DOZ[Dozzle Logs]
        UPK[Uptime Kuma]
        CFS[Coolify + Sentinel]
        LND[Landing Page]
        PNL[panel.goku.codes]
        IMA[img.goku.codes]
    end

    subgraph "Agent Hosting"
        GHR[GitHub Actions Runner]
        HERM[hermes-gateway-poke]
        TS[ Tailscale]
    end

    subgraph "CLI Tools"
        GH[gh CLI]
        GIT[git]
        GBR[gbrain CLI]
    end

    AK -.-> AKP
    AK -.-> AKR

    SDB --- SK
    SK --- SA
    SK --- SR
    SK --- SRL
    SK --- SML
    SK --- SEF
    SK --- SSP
    SK --- SIM
    SDB --- SPL
    SLF -.-> SDB
    SVD -.-> SDB

    CDB --> LS
    LS --> FS
    FS --> GB
    HMC --> GB
    HMC --> M0
    HMC --> FS
    M0 --> SDB
    M0D --> M0

    GHR ---|actions| GH
    GIT ---|pull/push| FS
    GBR ---|sync --full| FS
    GBR ---|query| GB

Service	What It Does	Connects To
CouchDB	Document DB, livesync changes feed	nginx (public), livesync-daemon, Obsidian clients
nginx	SSL reverse proxy	CouchDB (public endpoint)
livesync-daemon	Headless livesync peer, bidirectional filesystem bridge	CouchDB, vault filesystem
vault-write (filesystem)	The actual vault directory, git repo, gbrain source	git, gbrain, cloud agents, livesync-daemon
gbrain MCP	Semantic search + knowledge graph over vault	gbrain CLI, local MCP service, and hermes-mcp proxy with local CLI fallback
mem0 API	Episodic memory store for agents	hermes-mcp, Supabase PG, mem0-dashboard
mem0-dashboard	Web UI for browsing memories	mem0 API
hermes-mcp	Optional unified SSE MCP gateway, wraps gbrain + mem0 + vault	server service is active; vault, mem0, and gbrain smoke tests pass
hermes-gateway-poke	Hermes gateway daemon for messaging platform integration	Chat platforms
Supabase PG	Shared Postgres 15 with pgvector, used by gbrain, mem0, supabase services	gbrain, mem0, supabase-kong
Supabase Stack	Auth, REST, realtime, storage, edge functions, analytics	Web apps, mobile backends
authentik	SSO / OAuth2 provider for internal services	Protected web UIs
n8n	Workflow automation (Zapier-like)	HTTP APIs, webhooks
Meilisearch	Full-text search engine (separate from gbrain)	Web UIs
Paperclip	AI agent memory/state storage	Own PG 17 database
Pillow API	Image processing API	HTTP clients
ConvertX	File format conversion UI	HTTP clients
Change Detection	Website change monitoring	HTTP, browser
SearXNG	Private meta search engine	HTTP clients
Stirling PDF	PDF manipulation tools	HTTP clients
MinIO	S3-compatible object storage	HTTP clients, backup targets
Umami	Website analytics	Web UIs, own PG
Dozzle	Real-time Docker log viewer	Browser
Uptime Kuma	Uptime monitoring	All public endpoints
Coolify	PaaS / app deployment manager	Docker, deployed apps
GitHub Actions Runner	Self-hosted runner for CI/CD	github.com
img.goku.codes	FastAPI image app	HTTP clients
panel.goku.codes	Next.js panel app	Browser
Tailscale	Mesh VPN, all servers on same tailnet	All nodes

How It All Connects

The agent memory fabric (couchdb, livesync, gbrain, mem0, hermes-mcp) is a focused subset that shares the Supabase PG with the broader supabase stack. The vault filesystem is the integration point:

• CLI tools (git, gh, gbrain) read/write the vault filesystem directly
• LiveSync daemon bridges the filesystem to CouchDB for real-time replication
• gbrain indexes the filesystem for semantic search
• hermes-mcp wraps the filesystem, gbrain, and mem0 into MCP tools for clients that benefit from a single SSE endpoint
• All other services (paperclip, n8n, meilisearch, etc.) run independently and are unrelated to the memory fabric

The key insight: the vault filesystem is the shared ground truth for durable agent knowledge. CouchDB replicates it live. Git snapshots it for history. gbrain indexes it for search. CLI tools work on it directly. hermes-mcp exposes vault, mem0, and gbrain for clients that want MCP. All durable paths converge on that one directory.