Only the lines you changed
The old debt in the same file is still measured by ArchScan, but it never turns into review noise on your merge request.
- New violation: commented
- Existing debt: no comment
A senior architect on every pull request.
ArchPilot kicks in the moment a pull/merge request opens, reads the changed code against your architecture rules and leaves the fix as an inline review comment.
Screens from a running installation
The journey of a merge request
Six steps between your CI and the AppArch panel, both inside your network. The repository is never uploaded; only the findings travel.
- CI and Git
A merge request opens
A new MR, or a new push to one, starts your pipeline.
- CI and Git
The analyser job starts
It fetches the rule set from the panel, with project and workspace settings already applied.
- CI and Git
Only changed files are read
In review mode the analyser resolves the changed files first and reads only those.
- AppArch panel
Findings go to the panel
Rule, file, line and message travel to the panel; the repository itself is never uploaded.
- AppArch panel
New, repeated or fixed
The panel compares with the previous run: new findings get a comment, repeated ones are not posted again, fixed ones are resolved.
- CI and Git
Comments and a summary land
Inline comments on the exact lines, and an AppArch section in the MR description with the totals.
Optional gate: choose a fail-on severity in the panel and the job exits with code 4 once a finding reaches it, after the results are posted, so the pipeline turns red.
Anatomy of a comment
Every comment answers the same five questions, and looks the same on all four Git providers.
-
Rule and severity
Which rule, and how serious. Severity drives the score and the optional gate.
-
The exact line
The comment sits on the line that breaks the rule, never on an annotation above it.
-
Why it matters
The reasoning, so fixing it is a decision rather than a guess.
-
Suggestion
What to change, as the analyser suggests it.
-
Rule details
A link to the rule's own documentation page.
A finding's life on a merge request
One comment per finding, from the first push to the last. A finding closes one at a time: fixed, or closed by a person.
- FoundThe push that introduces it: one inline comment.
- Still thereLater pushes: the comment stays, no duplicate is posted.
- FixedThe line no longer breaks the rule: the comment is resolved.Closed by handA person closes it: it counts as dismissed, never as fixed.
Four Git providers, one behaviour
Comments post from the default integration user, or a workspace-dedicated bot account.
GitHub GitLab Bitbucket Azure DevOps
What's under the hood
ArchPilot isn't a linter - it behaves like an architect who fits your team's flow without the noise.
Inline review comments
The finding lands on the exact line - explaining what's wrong, why, and the suggested fix, just like a human reviewer. You can reply in the thread to discuss.
Diff-scoped analysis
Only the code changed in that PR/MR is reviewed. Legacy debt never becomes noise - the team focuses only on the risk they're introducing now.
Deduped & auto-resolved
Comments are marker-keyed: the same finding is never re-posted on each push, and fixed violations auto-resolve. The PR stays clean and readable.
Dedicated bot account + comment language
Comments post from the default integration user, or a workspace-dedicated bot account. You choose the comment language per workspace (EN/TR).
On-demand manual reviews
Trigger a review on a specific MR straight from the panel. ArchPilot verifies access first ("can I read it?"), then runs the review in your own CI pipeline.
Developer sync & scoring
Git members and MR authors sync automatically; service/bot accounts are auto-flagged (and editable). Each developer gets an ArchPilot-based score.
Per-project rule overrides
Enable, disable or tune rules per project or workspace. Rules you switch off in the panel never reach the bot - no false positives.
Runs in your own CI
The analysis runs in your own CI, on your own infrastructure - your source never leaves it; only findings are sent to the panel.
See it in the product
All screenshots
Get your first review today
Connect Git, switch the rules on, and let ArchPilot speak up on the next PR.