REPOBRIEF // ANALYSIS ENGINE

Understand any
codebase in minutes,
not weeks.

Paste a GitHub repo. We map the architecture with Mermaid, extract the tech stack, and write a plain-English brief — so you can ship on day one instead of day thirty.

try:

~/nextjs-starter · architecture.mmd

00/19

analyzing

Next.js 15 · TypeScript · Prisma · 47 files

JavaScriptTypeScriptPythonGoRustRubyJavaC++SvelteReactVueDjangoRailsNext.jsFastAPIElixirKotlinJavaScriptTypeScriptPythonGoRustRubyJavaC++SvelteReactVueDjangoRailsNext.jsFastAPIElixirKotlin

// 01 — HOW IT WORKS

04 STEPS≈ 90s

THE FLOW

From clone-URL to clarity in under two minutes.

Paste a URL

Any public GitHub repo. Or sign in with GitHub to browse your private ones — read-only, revoke anytime.

We walk the tree

We parse the file graph, manifests, and imports — mapping modules, services, and their relationships.

AI explains the why

Claude reads key files and writes a brief: what this app does, how it's structured, and where to start.

Ship on day one

Open the brief in your editor, share it with your team, or export the Mermaid diagram to your docs.

// 02 — FEATURES

06 MODULES

WHAT YOU GET

Six tools that turn a repo into a full onboarding doc.

MODULE 01

Live architecture map

Auto-generated Mermaid diagrams show how modules and services actually connect — rendered, not guessed.

MODULE 02

Tech stack, dated

Every framework, library, database, and runtime — with versions, license flags, and freshness indicators.

MODULE 03

Plain-English brief

An AI-written overview: what the repo does, how data flows, which files matter, and how to run it locally.

MODULE 04

File heatmap

See which files are the beating heart of the codebase — by commit density, imports, and coupling.

MODULE 05

Dependency graph

Go beyond package.json. We trace real imports to surface what each module actually depends on.

MODULE 06

Export everything

Markdown, JSON, raw Mermaid, or a shareable link. Drop the brief straight into your team docs.

// 03 — LIVE DEMO

INTERACTIVE

TRY IT WITHOUT SIGNING IN

Pick a repo. Watch it unpack.

TECH STACK 4 groups

FRAMEWORK

Next.js15.2.0

React19.0.1

LANGUAGE

TypeScript5.4.5

Node.js20.x

TOOLING

Turbopack2.0

SWC1.7

pnpm9.x

TESTING

Jest29.7

Playwright1.45

ARCHITECTURE auto-generated

~/nextjs-starter · architecture.mmd

00/19

ready

Next.js 15 · TypeScript · Prisma · 47 files

AI BRIEF claude 4.5

Next.js is the React framework for production. The repo is a monorepo with the core framework under packages/next/, containing the router, bundler integration, and server runtime. It exposes hooks into Turbopack for development and ships with hybrid rendering: SSG, SSR, and RSC on the same tree. Start reading at packages/next/src/server/.

METRICS

Files analyzed4,218

Primary languageTypeScript (87%)

First commitOct 2016

Contributors3,400+

// 04 — OUTPUT

MARKDOWN · MERMAID

WHAT YOU EXPORT

One command. Two files. A full onboarding.

architecture.mmdMERMAID · 42 LINES

graph TD
  A[app/] --> B[api/]
  A --> C[components/]
  A --> D[lib/]

  B --> E[routes/]
  B --> F[middleware/]
  C --> G[ui/]
  C --> H[forms/]
  D --> I[db.ts]
  D --> J[auth.ts]

  I --> K[(PostgreSQL)]
  J --> L[(Clerk)]

  %% generated by repobrief v0.4
  %% commit: a7f3d2e · 2026-04-18

brief.mdMARKDOWN · 184 LINES

# acme-dashboard

A multi-tenant admin panel built on Next.js 15 with
server components, Prisma, and Clerk for auth.

## tl;dr

- Renders on Node.js runtime, not edge
- Data layer: Prisma → PostgreSQL (AWS RDS)
- Auth: Clerk (see lib/auth.ts)
- Billing: Stripe Subscriptions

## where to start

Read app/(dashboard)/layout.tsx first —
it wires auth, tenant context, and nav. All feature
routes live under app/(dashboard)/[org]/.

## how to run

pnpm install
pnpm db:push
pnpm dev

// 05 — PRICING

3 TIERS

PAY FOR WHAT YOU SHIP

Free to try. Honest to scale.

HOBBY

^$0/ forever

For curious developers exploring open-source codebases.

10 public repo analyses / month
Architecture diagram (Mermaid)
AI brief (short form)
Markdown export

Start free →

PRO · POPULAR

^$18/ month

For engineers onboarding to new jobs, contractors, and reviewers.

Unlimited public + private repos
Full brief + dependency graph
File heatmap + code owners
JSON / Mermaid / PDF export
Priority analysis queue

Start 14-day trial →

TEAM

Custom

For engineering teams onboarding together or auditing inherited code.

Everything in Pro
Shared workspace + comments
SAML / SSO
On-prem deploy option
Dedicated support

Book a call →

// 06 — FAQ

06 ITEMS

QUESTIONS

Things people ask before signing up.

No. We analyze in-memory and persist only the generated artifacts — the diagram, the tech stack, and the brief. Your source is fetched via the GitHub API at analysis time and never written to disk.

We request read-only repo access. You can revoke it from GitHub's settings at any time. For public repos, no OAuth is needed — just paste the URL.

JavaScript, TypeScript, Python, Go, Rust, Ruby, Java, Kotlin, Swift, PHP, Elixir, C#, and C++ — plus their major frameworks. If your repo has a manifest file, we probably understand it.

Yes, on the Team plan. We ship a Docker image and Kubernetes Helm chart. You bring your own LLM key (Claude or a compatible model) and we run entirely in your network.

The brief is guided by deterministic analysis — we parse manifests, imports, and config files first, then pass findings to the model to phrase. It won't hallucinate a database you're not using.

Yes. The Pro plan includes 5,000 API calls / month. The Team plan is uncapped.

Stop reading
codebases. Start
shipping in them.

Connect your GitHub and turn your next unfamiliar repo into a brief in 90 seconds. Free to try.

◉Connect GitHub → Analyze a repo

Understand anycodebase in minutes,not weeks.