Does it work with GitLab Self-Managed or Dedicated?

Revix supports GitLab.com today. Self-Managed and Dedicated instances are not supported yet. If you run your own instance, get in touch and tell us, because that demand is what decides the order we build in.

What access does Revix need on GitLab?

Revix asks for the api and read_user scopes on GitLab's own consent screen. To connect a group you need the Maintainer or Owner role on it, because GitLab only lets those roles create project webhooks and Revix adds one to each project you choose. Your personal namespace needs no extra role.

Do I need to create a bot account?

No. Revix uses the GitLab authorization of the person who connected the group, so there is no extra seat to pay for and no personal access token to rotate. Its comments and summaries post under that account.

How long does a review take?

Most merge requests get a summary in around a minute or less, with inline comments shortly after.

How long does the initial repository analysis take?

It depends on the size of the codebase. Revix uses intelligent analysis instead of reading everything, so a standard repository is ready in around 3 minutes.

revix.

AI code review for GitLab

Native GitLab.com support. Connect a group and Revix reviews every merge request against the standards already in your repo.

Try it yourself

What a Revix review looks like on GitLab

Revix reviews GitLab merge requests the way a senior engineer would. It applies your team's own standards, comments on the diff with intent, and writes a summary into the merge request description.

Rules derived from your own repository

Revix reads your repository, learns your conventions, and derives review rules from how your team already writes code. Every GitLab review is checked against those rules, so feedback matches what your seniors would flag.

Revix rules dashboard listing rules derived from a codebase, grouped by impact

Comments written like a senior engineer

Each comment lands as a discussion on the exact line of the diff. It states the issue, the fix, and the rule behind it. When you push a fix in a later commit, Revix resolves its own discussion.

A Revix review comment on a GitLab merge request diff explaining an issue and linking the rule it applied

Merge request summaries in the description

Revix writes a summary of what the merge request changes into its description, above your own text, and refreshes it on every push. Reviewers get the full picture before they read a single line.

A Revix summary written into the description of a GitLab merge request

Get Revix reviewing your GitLab projects

01.Sign in with GitLab
Create your Revix account with a single click using your GitLab.com account. No new password, no manual access tokens.
02.Pick the group Revix should review
Choose a GitLab group or your personal namespace. Connecting a group needs the Maintainer or Owner role, because Revix adds a webhook to each project you connect.
03.Add the projects you want reviewed
Pick the GitLab projects you want under review. Nothing runs on projects you do not select.
04.Open a merge request
Revix reviews every new merge request automatically. No changes to .gitlab-ci.yml, no config file, no extra commands in your workflow.

Questions GitLab teams ask

No. Revix listens to merge request webhooks on the projects you connect, so reviews run outside your pipelines and never consume compute minutes. Tools that ship as a CI job or a CLI step do run inside your pipeline budget.

Bring senior-level reviews to your GitLab workflow

Start a 14-day free trial. No credit card required.

Start free trial