Your own Git server
For self-hosted and air-gapped Git
Connect your own GitLab instance by its URL. AppArch runs entirely inside your network, even fully air-gapped, and the analysis runs in your own CI.
Auth: Instance URL + OAuth application or access token
Screens from a running installation
How it connects
- 01
Register your instance
Add your GitLab URL and a credential: an OAuth application or a personal access token.
- 02
Connect repos
Select the projects to review.
- 03
Run on-prem
Analysis runs in your own CI and infrastructure.
What you get
On-prem & air-gapped
Fully operational with no internet access.
Self-managed GitLab
Any GitLab instance the installation can reach, by its own URL.
Data stays in your network
Source code never leaves your infrastructure.
One release line
The same product and the same images as every other installation.
How it works inside AppArch
Your AppArch server talks to the Git platform; the analysis runs in your CI. Here is every call in both directions.
What it reads
- Repositories, branches and members; members every 10 minutes for Developer Sync
- Merge requests, approvals and review threads; MR facts every 15 minutes for MR Insights
- Branch protection and merge settings, for Git Health
- Single files and the file tree, for Compliance; nothing is cloned
- The vulnerability report every 4 hours (GitLab Ultimate), into ArchSecurity
What it writes
- Inline comments on the lines the change added
- An AppArch section in the MR description, or one summary comment if that edit fails
- Resolves its own thread once the finding is gone
- Optional auto-approve or auto-reject; it refuses to approve if new commits arrived after the review
- Starts merge request and branch pipelines for on-demand runs, and can write CI variables
- Auto-reject withdraws the approval and leaves a note, since GitLab has no rejection
What it never does
- No commit statuses or check runs: the pipeline result is your CI job's own exit code
- Never clones or uploads the repository to the panel
- Never registers webhooks itself; paste the URL if you want one
- Self-managed GitLab is the only self-hosted Git server supported today
The same as GitLab, but every API and OAuth call is built from your instance's own URL, so traffic stays inside your network.
When things happen
- 5 sComments are posted
- 10 sNew findings are matched to their threads
- 5 minMerge request state and approvals are re-read
- 10 minMembers are synced
- 15 minMR facts for MR Insights
A webhook makes the merge request state change immediate instead of waiting for the next poll.
See it in the product
All screenshots
Connect Your own Git server
Connect in minutes - your first review lands on the next change.