RepoFold

Your codebase,
explained.
Always current.

RepoFold turns every repository into a cited, searchable workspace and keeps it updated with every commit. Open source at its core: run it in our cloud, or fully offline on your own machine.

See a live example
Private repositoriesLine-level sourcesIncremental updatesOpen source
RepoFold - Your codebase, explained. Always current. | Product Hunt
ReadySynced 2m ago
8f2c1ad
Architecture

Architecture

Orbit is an event-driven service that converts repository changes into a continuously updated knowledge layer.

System overview

Orbit receives repository events, maps changed symbols and publishes one consistent documentation revision. Each generated statement remains connected to its source.

Runtime topology

ServiceResponsibilityState
webWorkspace and APIStateless
workerAnalysis and generationQueued
databasePages and revisionsPersistent

Request lifecycle

A signed webhook records the target commit and queues an incremental job. Files with an unchanged blob SHA are skipped before any model call.

Source-grounded by default

Only changed files and affected pages are regenerated, keeping every sync fast and reviewable.

Updated today, 10:42 UTC·commit 8f2c1ad·

One workspace.
Four ways to understand.

One minute.
Whole picture.

From connecting a repository to a cited wiki, agent answers over MCP, and documentation that updates itself as your code changes. Watch it happen.

Built to be checked.

Generated documentation should never be a black box. RepoFold keeps the source, the commit, and the change history attached.

Every claim keeps its source.

Move from generated explanation to the exact implementation in one step. Citations stay pinned to the commit that produced the page.

worker/pipeline.ts8f2c1ad
42const changed = files.filter(hasNewBlob);43await regenerate(affectedPages(changed));44await revision.publish(commit);
1Used in ArchitectureLines 42–44

Only changed code moves.

Unchanged files and unaffected pages are reused.

Knowledge is versioned.

Every documentation revision follows a commit.

We keep the wiki, not your code.

Read-only access, scoped to the repositories you pick. Source streams through the indexer and is deleted the moment the job finishes. Even the snippets you open later are fetched live from GitHub, never from us.

Security and AI processing details
Open source

Code that is not allowed to leave the building?

Some codebases can never touch a cloud service, and some teams simply do not want to trust one. For them, RepoFold is open source: the same cited-wiki pipeline, running entirely on your own machine with local models through Ollama. No account, no telemetry, not a single network call beyond your own hardware.

The hosted product runs this pipeline on frontier models with automatic sync, search, Ask, and MCP. That is where it performs at its best. The local edition is for when policy or trust decides the code stays home.

View on GitHub

Your agent
reads it too.

Connect Claude Code, Codex, or Cursor over MCP. Instead of scanning the whole codebase, your agent asks the wiki and gets a short answer with exact file and line references, pinned to a commit.

claude ~/projects/xploredMCP · repofold
>where is the login flow implemented?
⏺ask_wiki("Neilbenji/xplored", "where is the login flow…")
Mobile: mobile/src/context/AuthContext.tsx:9-23 holds the AuthProvider; token refresh lives in mobile/src/services/api.ts:215-279. Backend: routes in backend/src/routes/auth.ts, JWT middleware in backend/src/middleware/auth.ts.
1 tool call · answered from the wiki @ c62bea6 · $0.00

One endpoint, every agent.

Anything that speaks MCP: add the server URL, paste an API key from your account, done.

Answers, not exploration.

ask_wiki answers server-side from the generated knowledge layer, so your agent spends a few hundred tokens instead of reading half the repository.

Grounded and current.

Every response names the commit it describes and cites file:line ranges your agent opens locally.

Start small.
Scale when it matters.

Every plan starts with source-linked documentation. Choose the workspace that fits the way your team builds.

Free

For understanding one codebase.

$0forever
  • One repository
  • Cited wiki and search
  • Changelog and history
  • Coding-agent access (MCP)
  • One manual refresh a week

Pro

For developers who ship daily.

$12per month, first 14 days free
  • Five repositories
  • Ask with line-level citations
  • Agent Q&A over MCP (ask_wiki)
  • Automatic daily sync
  • Repos up to 2,500 files

Team

For teams keeping knowledge current.

$49per month
  • Fifteen repositories
  • Team members, unlimited readers
  • Repos up to 10,000 files
  • Priority support

Company

For larger engineering organizations.

Custombuilt around your team
  • Everything in Team
  • Custom repository volume
  • SSO and invoicing
  • Security review support

Questions,
answered.

The short version of everything people ask before connecting a repository. For the security specifics, see the security page.

What is RepoFold?

RepoFold generates a documentation wiki from a GitHub repository. Every claim in the wiki cites the exact file and lines of code it describes, citations are validated against the parsed source, and the wiki updates itself as the code changes. It also answers questions from coding agents over MCP.

How do I know the generated documentation is correct?

Every sentence carries a citation into the source, and citations are checked by machine, not trusted from the model: the file must exist in the indexed commit and the line range must match a real function, class, or type extracted by a parser. Citations that fail validation are demoted or dropped before a page is published, and each citation in the wiki is a link that opens the actual code, so you can verify any statement in one click.

How citation validation works
Does RepoFold keep a copy of my source code?

No. RepoFold connects through a read-only GitHub App scoped to only the repositories you pick. The source streams through the indexer and is deleted the moment the job finishes; RepoFold stores the generated wiki, not your code. Even the code snippets you open while reading are fetched live from GitHub.

Security and AI processing details
Can I use RepoFold if my code is not allowed to leave the building?

Yes. RepoFold is open source: the same cited-wiki pipeline runs entirely on your own machine with local models through Ollama. No account, no telemetry, and no network calls beyond your own hardware, so the code never leaves your environment.

RepoFold on GitHub
How does the wiki stay up to date?

RepoFold re-syncs with your repository and regenerates only what a change actually affects. Unchanged pages are skipped by comparing input hashes, code that merely moved gets its citations re-anchored without a model call, and unchanged sections are reused byte-for-byte. Every documentation revision is pinned to the commit that produced it.

Can my coding agent use the wiki?

Yes. RepoFold exposes an MCP server that works with Claude Code, Codex, Cursor, and anything else that speaks MCP. Instead of reading half the repository, your agent calls ask_wiki and gets a short answer with exact file and line references, pinned to a commit.

What does RepoFold cost?

The Free plan covers one repository with the full cited wiki, search, and MCP access. Pro is $12 per month for five repositories with automatic daily sync and Ask; Team is $49 per month. The open-source local edition is free forever.

Which repositories does it work with?

Public and private GitHub repositories. You can see real generated wikis for well-known open-source projects in the showcase before connecting anything.

Browse the showcase

Stop documenting
yesterday's code.

Connect GitHub and give your team one place to understand what exists now.

By signing in you agree to the Terms and Privacy Policy.