repo → signal

Read any codebase like a live signal

Paste a GitHub URL. Get an architecture diagram, schema guess, API flow, folder map, and a learning roadmap — decoded from the repo's structure in one pass.

try
what you get
output

Five reads on one paste

Every analysis returns the same five sections, rendered as real diagrams — not a wall of prose.

01

Architecture diagram

A Mermaid graph of the real components and how they wire together — inferred from the file tree and entry points.

02

Database schema guess

Entities and relations read from migrations, models, and ORM files. Or a clear “no database here”.

03

API & runtime flow

The main request, job, or CLI path through the system, end to end.

04

Folder explanations

What each top-level directory is actually for — no more guessing at /lib vs /core.

05

Learning roadmap

An ordered path: what to read first, second, third to ramp on the codebase.

pipeline

From URL to map in one pass

  1. 1

    Paste a repo

    Any public GitHub URL — or just owner/repo. No sign-in, no install.

  2. 2

    We read the signal

    The GitHub API hands over the file tree, README, manifests, schema files, and entry points — metadata, not a full clone, so it scales to huge repos.

  3. 3

    A model decodes it

    One pass through a language model turns that structure into five readable sections, with diagrams rendered live in the browser.