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

Agent Memory Database in Medellín

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
01
decision

Standardize on idempotent write endpoints

Source: architecture.md

02
pattern

Repository layer owns every database transaction

Source: pull request #214

03
bugfix

Refresh tokens rotate atomically under load

Source: auth/session.ts

Claude Code
Cursor
Windsurf

WHY IT MATTERS HERE

Why Medellín engineering teams choose MemHub

In Medellín, 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.

  • Built for Medellín: Ruta N’s innovation district.
  • 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.

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 in Medellín, without the trade-offs.

01

Operations as usual

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

02

Upgrade is one command

Versioned SQL migrations with checksums — not a migration essay.

03

Query it with anything

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

04

Stop JSON, start SQL

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

05

Semantics when you want it

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

06

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.

Without MemHubWith MemHub
Context lives in heads and DMs → onboarding takes daysStructured, searchable memory → new dev/agent productive in minutes
Every agent re-learns the repo from scratchSessions open pre-briefed with only what changed — zero re-explaining
Rules files cap out at ~2k tokensUnbounded versioned history stays one query away — never cap again
Decisions re-litigated, bugs re-introducedPinned 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.

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

EXPLORE OTHER USE CASES

THE NEXT SESSION STARTS HERE — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free