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

Developer Knowledge Base across Romania

Stop letting your wiki rot. MemHub is a living developer knowledge base that writes itself while you code — decisions captured where they happen, retrieved where needed.

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.

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

Across Romania, 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 GDPR can point at a concrete architecture instead of promises.

  • Romania: 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 Romania 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.

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 across Romania, without the trade-offs.

01

Docs that write themselves

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

02

Not another wiki page

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

03

Find the precedent in seconds

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

04

Every claim checkable

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

05

Managers can read it too

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

06

You own the corpus

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

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.

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.

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.

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