01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Self-Hosted AI Memory in · shared project memory
Self-Hosted AI Memory in Querétaro
Self-hosting an AI memory layer should mean more than downloading a tarball. MemHub brings row-level security, restricted runtime roles, audit trails, and backup-friendly schemas — production posture from day one.
Data residency questions have simple answers when the answer is “your datacenter.” Run MemHub in-region, keep embeddings optional and local via Ollama, and put a defensible architecture in front of your DPO.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/self-hosted-ai-memory
synchronizedcontext/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
What changed since your last pull
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
LOCAL FIT
Why Querétaro engineering teams choose MemHub
In Querétaro, software teams ship faster when their tools share one memory instead of three silos. Mixed toolchains stop fragmenting knowledge across vendor-specific stores.
Every entry carries authorship and version history, which keeps both humans and auditors comfortable.
- Built for Querétaro: aerospace and IT services parks.
- 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
Self-Hosted AI Memory in Querétaro, without the trade-offs.
01
Same protocol, anywhere
Hosted and self-hosted speak identical MCP and REST interfaces, so moving between them is configuration, not code.
02
Your infrastructure
Single Docker Compose file or Easypanel template; the database never phones home.
03
Defense in depth
RLS policies, transaction-local tenant context, and NOBYPASSRLS application roles built into migrations.
04
Auditable by default
Administrative actions append to an audit table with actor, reason, and metadata.
05
Optional embeddings
Start with pure full-text search; enable Ollama locally if you want vectors without external APIs.
06
Standard backups
Everything important is plain PostgreSQL — pg_dump fits your existing continuity plan.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Status quo | With MemHub |
|---|---|
| Context lives in heads and DMs | Memory is structured, shared, and searchable |
| Every agent re-learns the repo | Sessions open pre-briefed with only what changed |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away |
Connect the tools already in your repository.
One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.
repository terminal
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
Questions, answered straight.
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 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.
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 Mexico CitySelf-Hosted AI Memory in GuadalajaraSelf-Hosted AI Memory in MonterreySelf-Hosted AI Memory in PueblaSelf-Hosted AI Memory in TijuanaSelf-Hosted AI Memory in MéridaSelf-Hosted AI Memory in San FranciscoSelf-Hosted AI Memory in New York CitySelf-Hosted AI Memory in AustinSelf-Hosted AI Memory in SeattleSelf-Hosted AI Memory in BostonSelf-Hosted AI Memory in Chicago
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