Self-Hosted AI Memory in · shared project memory — local-first · offline-ready

Self-Hosted AI Memory in San Diego

Stop shipping code context to a black box. MemHub is self-hosted AI memory on your PostgreSQL 16 + pgvector — Docker or Easypanel, you run the migrations, you own the data.

Self-hosting should be production-ready, not a tarball. MemHub ships RLS, restricted roles, audit trails and pg_dump backups — compliant from day one, no external API.

Start free — get briefed in 2 min

Free for 1 project · No card · Self-host or we host · No external API

acme/self-hosted-ai-memory

synchronized

context/main

memories 41

pinned 6

contributors 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new

decision

Standardize on idempotent write endpoints

Source: architecture.md

pattern

Repository layer owns every database transaction

Source: pull request #214

bugfix

Refresh tokens rotate atomically under load

Source: auth/session.ts

Claude Code

Cursor

Windsurf

WHY IT MATTERS HERE

Why San Diego engineering teams choose MemHub

In San Diego, software teams ship faster when their tools share one memory instead of three silos. Distributed squads stay aligned because every session opens with the same briefing.

MemHub runs hosted or fully self-hosted, so the storage boundary follows your compliance requirements rather than dictating them.

San Diego: connect Claude Code, Cursor, Windsurf, Cline, Codex CLI, or Antigravity to one shared memory. It also plugs into any CLI that speaks MCP or reads a JSON config.
Local-first writes keep sessions productive through outages and travel.
One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.

Start free — 2 min1 project free · no card required Guided demo20 min · see your repo remembered Self-host it myselfDocker + pgvector · you own the data

UNIVERSAL COMPATIBILITY

Plugs into any CLI or development tool you use.

If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.

Claude Code
Cursor
Windsurf
Cline
Codex CLI (GPT)
GitHub Copilot
Google Antigravity
Gemini CLI
Aider
OpenCode
CI bots via REST

WHAT YOU GET

Self-Hosted AI Memory in San Diego, without the trade-offs.

Stay inside your boundary

One Docker Compose / Easypanel file — database never phones home, data never leaves.

Production posture day one

RLS policies, NOBYPASSRLS roles, transaction-local tenants — in the migrations, not a todo.

Answer the auditor fast

Append-only audit table with actor/reason/metadata — demos that bore the DPO (in a good way).

AI without the API bill

Start with FTS; flip on local Ollama for vectors — no external embedding vendor needed.

Backups you already run

Plain PostgreSQL — pg_dump, replicas, PITR fit your existing continuity plan.

Move without rewriting

Hosted and self-hosted speak identical MCP/REST — switch is config, not code.

The honest comparison.

No feature-matrix gymnastics — just what changes the week you adopt MemHub.

Start free — 2 min Talk to the team

Without MemHub	With MemHub
Context lives in heads and DMs → onboarding takes days	Structured, searchable memory → new dev/agent productive in minutes
Every agent re-learns the repo from scratch	Sessions open pre-briefed with only what changed — zero re-explaining
Rules files cap out at ~2k tokens	Unbounded versioned history stays one query away — never cap again
Decisions re-litigated, bugs re-introduced	Pinned invariants prevent regressions — agents respect past calls

Keep your stack. Add shared memory.

One command for Claude Code, Cursor, Codex, Windsurf, Cline or any MCP client. No new editor. Setup in 2 minutes, works offline.

Start free — 2 min Talk to the team

repository terminal

$ npm install --global @simplexlat/memhub

$ memhub login

✓ project resolved · context ready · memory synchronized

Questions, answered straight.

What do I need to self-host?

A host with Docker (or Easypanel) and a PostgreSQL 16 database with the pgvector extension. Migrations and seeds are one command each.

Is the hosted option still private?

Hosted memory is isolated per organization with row-level security, encrypted transport, and hashed credentials — but self-hosting remains the strongest guarantee because no third party operates the storage.

What happens when our connection drops?

Nothing interrupts the work. Writes commit to the local SQLite outbox and synchronize automatically when the shared service is reachable again.

Can we try it without sending data anywhere?

Yes — the local engine works fully offline, and the self-hosted stack keeps even the shared layer on your own PostgreSQL.

How much does it cost?

A Community tier is free, and the Team plan adds multi-project contexts, seats, and higher synchronization limits. Self-hosting is unlimited.

MORE LOCATIONS

Self-Hosted AI Memory in California Self-Hosted AI Memory in Texas Self-Hosted AI Memory in New York State Self-Hosted AI Memory in Florida Self-Hosted AI Memory in Washington State Self-Hosted AI Memory in Massachusetts Self-Hosted AI Memory in Colorado Self-Hosted AI Memory in Illinois Self-Hosted AI Memory in Georgia Self-Hosted AI Memory in Arizona Self-Hosted AI Memory in North Carolina Self-Hosted AI Memory in Utah

EXPLORE OTHER USE CASES

AI Agent Memory

Give every AI coding agent a persistent, team-wide memory.

MCP Memory Server

A hosted MCP memory server your whole team connects to in one command.

Claude Code Memory

Claude Code memory that survives sessions and reaches the whole team.

Cursor Memory

Carry Cursor context across sessions, machines, and teammates.

Codex CLI Memory

Persistent context for Codex CLI — personal today, shared tomorrow.

Cross-Agent Memory

One memory behind Claude Code, Cursor, Codex CLI, and Antigravity.

Developer Knowledge Base

A living knowledge base that writes itself while your team codes.

Coding Agent Context

Context engineering for coding agents — brief, don’t dump.

Engineering Decision Log

An ADR habit your team will actually keep — logged by the agents doing the work.

Agent Memory Database

A real database behind agent memory — PostgreSQL, pgvector, row-level security.

Windsurf Memory

Persistent Windsurf context shared with every other agent on the team.

Cline Memory

Give Cline a memory that survives tasks, machines, and teammates.

Copilot Team Memory

What Copilot’s custom instructions can’t hold, MemHub remembers.

Antigravity & Gemini Memory

Persistent context for Google Antigravity, Gemini CLI, and the agents around them.

THE NEXT SESSION STARTS HERE — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free