AI codebase analysis — preview

Understand any codebase in minutes

Connect your GitHub repository and get an AI-powered map of its architecture, important files, documentation, and codebase Q&A.

Free for up to 3 repositories · No credit card required

acme/ecommerce-platform — analysis
live

Cloning repository

acme/ecommerce-platform · main

Indexing 214 files

TypeScript · 48,210 lines

Mapping architecture

5 modules detected

Architecture detected

Frontend ↓ API Routes ↓ Database

How it works

From repo to mental model in four steps

Stop reading READMEs and chasing imports. Get the map that experienced engineers build in their heads.

01

Connect a repository

Link a GitHub repository with a single click. We only request read access — we never push or modify your code.

02

We map the codebase

Our engine indexes the repository and builds an architecture map: modules, important files, data flows, and dependencies.

03

Get onboarding docs

Receive generated documentation covering setup, architecture, and the flows every new engineer asks about.

04

Ask anything

Chat with the codebase. Ask where things live, how flows work, or why a decision was made — grounded in your actual code.

Features

Everything needed to ramp up fast

Built for engineers who would rather read code than a wiki that's already out of date.

Live

Architecture map

A visual diagram of services, modules, and their relationships — extracted directly from your code, not written by hand.

Live

Important files

We rank the files new engineers should read first, so onboarding starts with signal instead of a wall of directories.

Live

Auto-generated docs

Setup guides, architecture overviews, and flow walkthroughs generated from the repository itself.

Preview

Codebase Q&A

Ask questions in plain English and get answers with file and line references you can verify.

Live

Flow explorer

Follow a request from entry point to database query. Understand checkout, auth, and sync flows end to end.

Live

Secure by design

Read-only access, encrypted at rest, and scoped permissions. Your code is never used to train models.

Live

Language support

TypeScript, JavaScript, Python, Java, Go, and more. New languages are added every month.

Next phase

Change summaries

A digest of what changed since the last analysis, so the map stays fresh as your codebase evolves.

Example architecture

What a map looks like

A real analysis of a Next.js + Stripe storefront. Every box is traceable back to code in the repository.

Frontend

Product Catalog

Next.js · React 19

Cart & Checkout

Next.js · React 19

API Routes

/api/* · route handlers

Authentication

NextAuth v5 · JWT sessions

Database

PostgreSQL · Prisma ORM

Payment Service

Stripe

Webhook handler

Codebase Q&A

Ask your codebase anything

Answers grounded in the repository you connected — with file references you can jump to and verify yourself.

Try asking

  • • How are background jobs retried?
  • • Which service owns the user profile?
  • • What does /v1/orders/:id do end to end?

Ask about any repository…

Where does the checkout flow start?

Checkout starts in app/(shop)/checkout/page.tsx. It submits to POST /api/checkout, validates inventory, creates a Stripe payment intent, and confirms via the Stripe webhook.

app/(shop)/checkout/page.tsxapp/api/checkout/route.tsapp/api/webhooks/stripe/route.ts

How is authentication wired up?

Authentication uses NextAuth v5 with JWT sessions. The session is exposed to server components through lib/auth.ts. The checkout page calls requireUser() to redirect unauthenticated visitors.

lib/auth.tsapp/api/auth/[...nextauth]/route.ts

Why is inventory decremented transactionally?

To keep stock consistent when checkout races with other purchases. Prisma runs the update and order insert inside a transaction with row-level locking.

lib/cart/inventory.ts

FAQ

Frequently asked questions

Everything you might wonder before connecting your first repository.

What do I need to connect a repository?

Just a GitHub account with a repository you want to understand. We use read-only access — we never push commits, open PRs, or modify your code in any way.

How long does an analysis take?

Most repositories are analyzed in under five minutes. Small repos finish in under a minute; very large monorepos can take a bit longer. You'll see live progress in the dashboard.

Is my code used to train AI models?

No. Your code is encrypted at rest and only used to answer questions about your own repository. We never train or benefit from your source code.

Which languages are supported?

We currently support TypeScript, JavaScript, Python, Java, Go, Rust, and C#. Ruby and PHP support are in progress.

Does the analysis stay up to date when the code changes?

Yes — re-analyze on demand or on a schedule. Change summaries highlight what's different since the last analysis.

Can my whole team use one organization's repositories?

Starter is per-person. Team plans add a shared workspace with pooled limits, which arrives in a later phase.

Stop reading READMEs. Start understanding.

Connect a repository and get the architecture map, docs, and answers your whole team can rely on — in minutes.

Free for up to 3 repositories · No credit card required