Open source · no sign-up · runs in your browser

See how any GitHub repo works.

Paste a link and get an animated, narrated architecture tour in seconds. Every box and arrow links to real code, so nothing is made up.

Try:
  • 0 dependencies
  • 11 languages
  • MIT licensed
  • 100% in your browser
Animation of a gitvisualise tour of tj/commander.js: the diagram lights up one import at a time while the narration on the right explains each step

Or choose from a GitHub account

Private repo, or hit GitHub's rate limit? Add a token

The token is only ever sent to api.github.com from your browser. Nothing is uploaded to any other server. Use a fine-grained token with read-only Contents access.

What you get

More than a diagram

Compare two revisions

See what changed between two tags or branches: added, removed and changed components, with a narrated tour of the difference.

Request tracing

Follow a fetch call from the frontend to the server route that handles it. Linked only on an exact method and path match.

Monorepos

One component per workspace package, or open a single folder such as owner/repo:apps/web.

Search, group, export

Find components with /, group into swimlanes, and export SVG, PNG, Mermaid or PlantUML.

Narrated tours

Captions and your browser’s own voice, with playback controls and a shareable link to any step.

Private by design

Analysis runs in your browser and the tour plays in a sandboxed frame. Nothing is uploaded and no keys are needed, unless you choose the optional AI narration with your own key.

Import graphs for JavaScript / TypeScriptPythonGoJavaKotlinRustC#RubyPHPC / C++Dart more on the roadmap →

How it works

  1. 1

    Reads the repo

    Your browser fetches the file tree and source files straight from GitHub. No server of ours ever sees them.

  2. 2

    Finds the structure

    It resolves real imports, entry points and dependencies, then checks every claim against the actual files.

  3. 3

    Plays the tour

    Watch the flow light up step by step with captions and voice narration, and click any part to see its code.

If the repo already publishes its own tour (docs/architecture/), you get that one, curated by its authors.

Bring it to your own repo

The website gives you an automatic picture. Add the skill or the action to publish a curated tour with narration written from your actual code.

🤖 Claude Code skill

Ask Claude Code to “generate an interactive architecture for this project.” It reads your code, writes the narration, and validates every claim.

git clone https://github.com/Kaushik2210/gitVisualise gitvisualise
node gitvisualise/skills/repo-architecture/scripts/gitvisualise.mjs install-skill

⌨️ Command line

One command, zero dependencies, Node 18+. Works on local folders and GitHub URLs.

node gitvisualise/skills/repo-architecture/scripts/gitvisualise.mjs all .

⚙️ GitHub Action

Regenerate on every push and publish to GitHub Pages. Curated edits are preserved.

- uses: actions/checkout@v4
- uses: Kaushik2210/gitVisualise@main
  with:
    out: docs/architecture

Read the docs Help build it

Build it with us

gitvisualise is open source and young. There is a public roadmap, and every task is a scoped issue with pointers to the exact files. Pick one, or tell us which repo it draws badly.

Find a good first issue Read the roadmap Join the discussion

Narrate this tour with AI

Optional. A language model rewrites the plain narration of each step, using your own API key. Nothing happens until you press Start.

Experimental. This has been tested against a stand-in provider, not yet against the live API. If it fails, nothing is changed.

What is sent to the provider

For each tour step: its title, the names, kinds and one-line summaries of the components it highlights, how they connect, and the current plain narration. No source code and no file contents. Names and summaries can contain file and folder names.

Show exactly what step 1 would send
What comes back is checked

A rewritten step is used only if it is short plain prose that names nothing outside this tour. Anything else keeps the automatic narration, and the tour must still pass validation. Rewritten steps are labelled AI-written.