Developer Knowledge Base in · shared project memory — local-first · offline-ready

Developer Knowledge Base in Manila

ADRs and runbooks die in Confluence. MemHub keeps engineering knowledge next to the workflow, versioned per project, searchable in natural language — and agents read it, so it stays fresh.

Onboard seniors in days, not weeks. MemHub hands newcomers real history — decisions with reasons, fixes with root causes — provenance included. Try with one project free.

Start free — get briefed in 2 min

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

acme/developer-knowledge-base

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

In Manila, software teams ship faster when their tools share one memory instead of three silos. New engineers ramp in days because precedent is searchable, not oral history.

Because writes land locally first and synchronize later, flaky connections never block the work.

Manila: 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

Developer Knowledge Base in Manila, without the trade-offs.

Not another wiki page

Decisions, patterns, bugfixes typed as records — not free-form blobs you’ll never find.

Find the precedent in seconds

Full-text + optional semantic search — junior or senior, answer in one query.

Every claim checkable

Authorship and source links on every memory — no anonymous folklore, no trust-me docs.

Managers can read it too

Human web portal — leadership browses same corpus without opening a terminal.

You own the corpus

Self-host on your PostgreSQL — exportable, ownable, lives on infra you control.

Docs that write themselves

Knowledge captured where work happens — terminals, PRs, agents — not in a separate CMS you avoid.

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 we import existing docs?

Memories accept arbitrary source references, and the sync API accepts programmatic writes — most teams seed it from ADRs and postmortems with a small script.

Is this just another wiki?

It is the opposite: instead of asking engineers to write documents, it preserves the knowledge they already produce as they work, structured for both human and machine retrieval.

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

Developer Knowledge Base in San Francisco Developer Knowledge Base in New York City Developer Knowledge Base in Austin Developer Knowledge Base in Seattle Developer Knowledge Base in Boston Developer Knowledge Base in Chicago Developer Knowledge Base in Denver Developer Knowledge Base in Los Angeles Developer Knowledge Base in Atlanta Developer Knowledge Base in Miami Developer Knowledge Base in Dallas Developer Knowledge Base in San Diego

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.

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.

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