Developer Knowledge Base across · shared project memory

Developer Knowledge Base across Finland

Architecture decision records, runbooks, onboarding notes: most die in a Confluence graveyard. MemHub keeps engineering knowledge next to the workflow, versioned per project, searchable in natural language.

Onboarding a senior hire takes weeks mostly because context lives in people’s heads. A MemHub-backed knowledge base hands newcomers the repo’s real history — decisions with their reasons, fixes with their root causes.

Create your shared memory

Free Community tier. Self-hosted or hosted. No external embedding API required.

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

LOCAL FIT

Why Finland engineering teams choose MemHub

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

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

Finland: 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 Finland 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 freeFree workspace in 2 minutes Guided demo20 min with the founding team Self-host it myselfDocker + PostgreSQL on your infra

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

Structured and typed

Decisions, patterns, bugfixes, and references are stored as distinct record types, not free-form pages.

Natural-language retrieval

Full-text and optional semantic search find the right precedent in seconds.

Provenance-first

Authorship and source links make every claim checkable — no mystery folklore.

Human portal included

Managers and staff engineers browse the same corpus from the web dashboard without touching a terminal.

Exportable ownership

Self-host the stack and your knowledge base lives entirely on infrastructure you control.

Capture in the flow

Entries come from the tools engineers already use — terminals, editors, PR reviews — not a separate CMS.

The honest comparison.

No feature-matrix gymnastics — just what changes the week you adopt MemHub.

Start free Talk to the team

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.

Start free 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

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

Stop rebuilding context.
Start building the product.

Create workspace