The multi-repo alternative for teams that have many data sources

Mintlify is a great docs platform if you want to run a public docs platform. Dosu is for teams that want their internal docs and context to stay current without thinking about it and can run on all the tools and repos they already use.

No migration. No new platform. No extra tab.

Dosu manages your docs where they already live — Notion, Confluence, Coda, GitHub, GitLab, and more. No lift-and-shift to a new platform, no parallel source of truth, no retraining your team on where to look.

# eng-help

M
MiguelTuesday at 4:43 PM
@Dosu what GCP service backs our code retrieval tools?
DosuAPPTuesday at 4:43 PM

Cloud Filestore (NFS) — a 2.5 TB BASIC_SSD instance mounted at /mnt/filestore. It stores LanceDB vector databases that power code search and retrieval. The internal-api mounts it read-write for indexing, and the search-api mounts it read-only for queries [1].

The search-api Cloud Run service sits in front of it, handling vector and full-text search requests from agents over a direct VPC network interface for low-latency access.

111
D
DonnieToday at 10:27 AM
@Dosu can u update our docs with this?
DosuAPPToday at 10:27 AM

Updated! I've added the Cloud Filestore / LanceDB architecture details to the infrastructure docs. Let me know if anything needs adjusting.

Code Retrieval Infrastructure

Notion

Synced

Engineering / Infrastructure / Code Retrieval Infrastructure

Code Retrieval Infrastructure

Last edited 4 min ago

GCPSearchProduction

Our code search and retrieval pipeline is backed by Cloud Filestore (NFS) — a 2.5 TB BASIC_SSD instance mounted at /mnt/filestore. It stores LanceDB vector databases that power all vector and full-text search across the codebase.

Source: This page was reconciled from a thread in #eng-help started by Miguel on Tuesday at 4:43 PM.

Filestore configuration
PropertyValue
Instance typeBASIC_SSD
Capacity2.5 TB
Mount path/mnt/filestore
ProtocolNFS
Network accessDirect VPC (low latency)

How Dosu compares vs. Mintlify

Capability comparison between Mintlify and Dosu
ContentMintlifyDosu
No migration — docs stay in Notion, Confluence, Coda, GitHub, and GitLabMintlify does not do this.new platformDosu does this.
Internal engineering knowledge, not just customer-facing docsMintlify does not do this.Dosu does this.
Doc maintenance preconfigured — no prompt engineering requiredMintlify does not do this.Dosu does this.
One knowledge base spanning every repoMintlify does not do this.single repoDosu does this.
Knowledge captured from code repos, docs, and team communication toolsMintlify does not do this.author-writtenDosu does this.
Reconciled on every pull request, so pages never drift from the codeMintlify does not do this.manualDosu does this.

Docs for your engineers, not just your customers

Mintlify optimizes your customer-facing docs. Dosu does that — and also captures the internal knowledge that keeps your team running: architecture decisions, incident context, prior PRs, system reasoning. Great external docs matter; so do great docs for the engineers building the thing.

GitHub
Confluence
GitLab
Notion
Dosu
Jira
Slack
Coda
Microsoft Teams

Collective memory with an infinite bus factor

Every coding agent is a new engineer you onboard from scratch for every task. Dosu gives your team — and every agent on it — a shared, persistent memory of how your systems work.

Michael Torres

Staff Engineer

Sarah Chen

Senior Engineer

Jun Park

QA Engineer

Dosu
CODING AGENTS
ClaudeCursorCodexGeminiWindsurf

You built something
worth documenting

Let Dosu handle the part you've been putting off.