Use Case

The engineering wiki your team already has.

Your RFCs, runbooks, and architecture docs are in Drive. Shelfdrive makes them navigable.

Continue with Google →

Free to start · No credit card required

/Engineering
  /RFCs
  /Architecture
    /System Design
    /Data Models
  /Runbooks
  /Oncall
  /Postmortems
  /Onboarding

The problem with engineering docs in Drive

Engineering docs pile up in Drive — a design doc here, a runbook there, a postmortem in someone's personal folder. Without shared structure, no one can tell which architecture doc is current, and search returns five drafts of the same RFC. The knowledge exists; it just can't be found when it matters.

Features

What Shelfdrive gives engineering teams

Folder tree

RFCs, runbooks, and specs in a nested tree your whole team can navigate.

Cmd+K search

Full-text search across every doc, without leaving the keyboard.

Native editing

Write in Google Docs. No new editor.

Shareable links

Send a Shelfdrive URL — recipients land inside the wiki, not back in Drive.

What belongs in an engineering wiki

Keep the wiki to documents that stay true for months. RFCs capture why the system looks the way it does. Architecture and data-model docs describe how it fits together. Runbooks and oncall procedures keep production recoverable; postmortems turn incidents into lessons; onboarding guides get new engineers shipping fast. Transient discussion stays in your issue tracker — the wiki is the durable layer. See how Shelfdrive works or compare pricing.

/Engineering
  /RFCs
  /Architecture
    /System Design
    /Data Models
  /Runbooks
  /Oncall
  /Postmortems
  /Onboarding
FAQ

Common questions.

The one your team actually keeps current. If your RFCs and runbooks already live in Google Docs, Shelfdrive fits best — folder-tree navigation and Cmd+K search on top of Drive, with no migration and no second source of truth.
Yes, for most teams. Confluence's value is structure and search, not its editor. Shelfdrive gives Drive that — nested folder tree, full-text search — while you keep writing in Google Docs. You skip the import, the per-seat bill, and the duplicate-content problem.
A top-level Engineering folder split by type: RFCs, Architecture, Runbooks, Oncall, Postmortems, Onboarding. Keep folders shallow and predictable. Shelfdrive renders that as the wiki tree — the way you file is the way teammates browse.
Durable knowledge — RFCs, design decisions, architecture and data-model docs, runbooks, oncall procedures, postmortems, onboarding. Keep transient chatter in your issue tracker. The wiki is for documents that stay true for months.

The engineering wiki, minus the migration.

Make the Drive your team already uses navigable. Ready in 30 seconds.

Continue with Google →