Institutional memory for engineering teams

The decision log for engineering teams

Ravnik links every decision your team makes to the commit that shipped it — so “why did we do this” always has an answer.

Sample decisions

Built with Ravnik

Ravnik’s own decision log, kept in Ravnik

250+Decisions logged building Ravnik itself
liveDecision → commit traceability
ClaudeMCP connector
enforcedPer-organization isolation
cut & diffedVersioned decision log
feather viewProvenance graph

How it works

Three steps, no new habits

01

Connect Claude

Add Ravnik's MCP connector to Claude. No separate app to install, no new login for your AI tool.

02

Log decisions

Decisions get written down as the work happens — what was decided and why — instead of reconstructed from memory later.

03

Trace to commits

Every decision in Ravnik's own log links forward to the commit that shipped it — the sample above mirrors how that actually looks.

Docs & guides

Read the guides

Four short guides: set up, connect Claude, decide what to log, and keep the log useful.

Pricing

Draft pricing

Checkout isn’t live yet — creating an account starts you on Free. Prices may change before paid plans go live, and we’ll say so here when they do. No lock-in, cancel anytime.

Free$01 memberReal, not a crippled trial — stays usable indefinitely.
Starter$13/mo5 members
Pro$21/mo10 members
Business$49/mo20 membersPlus about $4.50 per additional seat beyond 20 — no cliff at any headcount.

Start the log

Two minutes now, so nobody has to ask “why did we do this” in six months.