The human layer for AI-written software
Review the change,
not the diff.
See what a pull request does to your system before you merge it. Review changes as fast as agents produce them.
112 files, tests green, 140 bot comments. Every line is right there. Which ones matter?
The same pull request, as a system. Six components, drawn from the code itself. Hover one to follow its connections, click it to see what flows in and out.
Payments now depends on Identity. A Google sign-in outage can block card payments. That is a system decision, not a code change.
Real diagrams, one click away
Open a finished diagram.
Five public codebases, drawn by the engine from their code. Pick one and it opens in CodeBoarding: explore the system, or review a pull request as a diagram. No account needed.
See the impact. Set the direction.
From the pull request to the system.
What changed, what it affects, where to look first.
The Action posts a Mermaid change diagram on the pull request itself. See the changed components and new connections without leaving GitHub.
Architecture review · 2 components changed, 1 new dependency
| Component | Change | Files | Depends on |
|---|---|---|---|
| Identity & Sessions | Modified | 61 | Google Identity API (external) |
| Payments | Modified | 38 | Identity & Sessions (new), Data Store |
Colors indicate component changes compared to the target branch:
AddedModifiedRemoved
Open this pull request in CodeBoarding
Download the PR analysis artifacts from this workflow run.
Delegate more
Keep ownership of what merges while agents take on more of the work.
The dashboard sorts every open pull request by what it is waiting for: needs you, ready to merge, blocked, waiting on others. Your team reviews at the level where decisions live and hands the line-by-line work to the agents.
How it works
Up and running in one pull request.
Sign in and pick repositories
One at a time or a whole organisation. Read-only, and you can change it later.
Merge one pull request
We prepare the setup and open a pull request in the repository you choose. It adds two workflow files and nothing else.
Each pull request gets its diagram
Once you merge it, your GitHub Actions draw the baseline and a change diagram for every pull request.
- Runs in your GitHub Actions
- Excerpts go to the model provider you configure
- Files are read only when you open them
- How the analysis runs
Wherever you review
Browser, editor, CI. One diagram.
In your browser
Open any pull request as a diagram, click a component for what changed in it, share the link with the team.
Open a live example
In your editor
The same diagram beside your code in VS Code, Cursor and Windsurf. Copy a component as context for your agent.
Get the extension
In CI
The GitHub Action draws every pull request on top of the baseline and posts the architecture change as a comment.
See the ActionWhat engineering teams say
“As a manager of a team of 8 developers, it's often difficult to keep track of changes to our system. CodeBoarding has made it much easier to keep an accurate understanding of the system that helps me make relevant decisions and stay up to date in technical discussions.”Engineering ManagerPalo Alto Networks
Pricing
Free to start. Pay when the diagram needs depth.
Free
Metered analyses, diagrams three levels deep, every repository you choose. No card.
Try for freeEnterprise
Custom environments, integrations and priority support for your organisation.
Book a demoPro is a monthly subscription. Cancel any time.
Your codebase is the next diagram
Review the change, not the diff.
Start free with the repositories you choose, or talk to us about your team.