Understand any GitHub repository, with every answer cited to the exact line^[1]

[1]AuthService.authenticate() · AuthService.java · lines 19–33 · @3f9c2e1

DevIQ reads your code at one commit. Ask how something works, open the lines behind every claim, and follow the architecture and request flows until the whole codebase makes sense.

Open your repositories See how it works

Public and private repositories
Read-only GitHub access
Every answer linked to source

Solo developers

Pick up an unfamiliar codebase or your own code from six months ago.

Students

Learn how real projects are structured, one file and one flow at a time.

Freelancers

Get productive on a client's repository before the first call is over.

Features

Ask, verify, explore, visualize, learn

One workspace per repository. The overview, diagrams and source are free to browse; only answers written by the AI use your daily allowance.

Answers you can verify

Ask in plain language. Every statement links to the exact file, symbol and lines at the indexed commit — never invented by the model.

Source at the exact commit

Open any citation to read the code with the cited range highlighted, a symbol outline, and a link to the same lines on GitHub.

Architecture, drawn from code

Controllers, services, repositories, data models and external systems, connected by calls DevIQ resolved — zoom, pan, go full screen.

Real request flows

“Show me the login flow” or “Trace POST /api/orders” becomes a step-by-step diagram. Click any step to land on its code.

A reading order to learn it

README, entry points, APIs, core services, data — in the order that makes sense, with the key functions of every file.

Dependencies and data model

See what any function depends on and what uses it, every endpoint with its services, and every entity with its tables.

How it works

From clone-and-grep to a guided tour

Connect GitHub
Sign in with GitHub and pick a public or private repository. DevIQ only reads.
Index one commit
Files are parsed into functions, classes, endpoints and entities, pinned to the commit they came from.
Start from the overview
What the project does, its stack, key modules and a reading order — before you ask anything.
Ask and verify
Answers cite exact lines. Open them, explain a symbol, or turn the answer into a flow diagram.

Grounded answers

The model cites; DevIQ decides what a citation is

Hybrid search finds code by meaning, keywords and exact symbols or routes
The model may only refer to the sources it was given — unknown references are removed
Line numbers and commit hashes always come from the index, never from the model
No relevant code found? You get a plain answer saying so, and no AI use is counted

Visual understanding

Diagrams built from resolved calls, not guesses

Java calls followed through field types; JS, TS and Python by unambiguous names
Frontend fetch calls linked to the backend endpoints they hit
Every box and step opens its code; dependencies in both directions
Drawing diagrams never uses your AI allowance

Learning

A new codebase, in the right order

Reading order from the repository's actual structure: README → entry → API → services → data
Key functions of each file, picked by how much the rest of the code uses them
Optional study guide: one AI interaction, stored for that commit
Progress you can tick off as you go

Security and cost

Built to be trusted with your code

Your token stays on the server

GitHub tokens are encrypted at rest and never sent to the browser or written to logs.

Access checked on every request

Your repositories are visible only to you, and DevIQ re-checks GitHub access before serving code.

Read-only by design

DevIQ reads code to index it. It never pushes, comments or opens pull requests.

FAQ

Questions, answered

Open a repository you have never seen. Understand it today.

Connect GitHub, pick a repository, and start from its overview.

Open your repositories

Understand any GitHub repository, with every answer cited to the exact line[1]

Ask, verify, explore, visualize, learn

Answers you can verify

Source at the exact commit

Architecture, drawn from code

Real request flows

A reading order to learn it

Dependencies and data model

From clone-and-grep to a guided tour

Connect GitHub

Index one commit

Start from the overview

Ask and verify

The model cites; DevIQ decides what a citation is

Diagrams built from resolved calls, not guesses

A new codebase, in the right order

Built to be trusted with your code

Your token stays on the server

Access checked on every request

Read-only by design

Questions, answered

Which languages does DevIQ understand?

Can the AI make up file names or line numbers?

What counts as an AI interaction?

What happens when my repository changes?

Does it work with private repositories?

Open a repository you have never seen. Understand it today.

Understand any GitHub repository, with every answer cited to the exact line^[1]