Agent Memory Database across · shared project memory — local-first · offline-ready

Agent Memory Database across Peru

Memory needs relations and vectors. PostgreSQL gives both. Types, versions, sequences, tenant isolation — queryable with psql, BI, notebooks. No proprietary export.

Semantic recall without lock-in: local Ollama or remote provider, or pure FTS. Corpus stays in your PostgreSQL, queryable forever. Start free, 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/agent-memory-database

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 Peru engineering teams choose MemHub

Across Peru, 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.

Teams operating under Law 29733 can point at a concrete architecture instead of promises.

Peru: 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.
Data residency you control — run MemHub on infrastructure inside Peru or let us host it.
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

Agent Memory Database across Peru, without the trade-offs.

Operations as usual

Replicas, backups, PITR — reuse the PostgreSQL playbook your team already runs.

Upgrade is one command

Versioned SQL migrations with checksums — not a migration essay.

Query it with anything

BI, notebooks, audits over standard SQL — no proprietary export tax.

Stop JSON, start SQL

One PostgreSQL for memory, sync cursors, audit, billing — boring, battle-tested, browsable with psql.

Semantics when you want it

pgvector HNSW indexes included — enable embeddings locally via Ollama, or stay FTS.

Tenant isolation inside the DB

Row-level policies — a bug in one project’s code can’t read another org’s rows.

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.

Can I run it managed?

Yes — any Postgres 16 with pgvector works, including Easypanel, RDS, Cloud SQL, or Neon; self-hosted and hosted modes share identical schemas.

Why PostgreSQL instead of a vector-only store?

Memory needs relations (tenants, projects, authors, versions) as much as vectors. PostgreSQL provides both, plus the operational maturity no niche store matches.

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

Agent Memory Database across the United States Agent Memory Database across Canada Agent Memory Database across the United Kingdom Agent Memory Database across Ireland Agent Memory Database across Germany Agent Memory Database across France Agent Memory Database across Spain Agent Memory Database across Portugal Agent Memory Database across Italy Agent Memory Database across the Netherlands Agent Memory Database across Belgium Agent Memory Database across Switzerland

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.

Self-Hosted AI Memory

Run the entire memory stack on your own PostgreSQL — nothing leaves.

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.

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