documentation

Install ReviewGate in your own infrastructure

The bot ships as a single Docker image, connects to your self-hosted GitLab over a webhook and leaves its comments right in the merge request. The code never leaves your network: with a self-hosted platform the only thing that goes out is the request to the model you chose.

The second hosting vendor is GitHub: the same reviews and the same .reviewgate/config.yml for pull requests on github.com. The bot works with either vendor, or with both at once.

The pages below are a reference — they answer «what does this key do». When the question sounds like a task instead — «put the review on a hook», «review without the cloud», «the bot said nothing» — start from the recipes: each one is a task walked end to end, ending with a real run and its price.

where to startIf this is your first install, follow the quickstart: it takes you from an empty .env to the bot's first comment on a test pull request.

01QuickstartFrom nothing to a first review on a real pull request.02Install with an AI agentHand the installation to an AI agent: it brings up the containers, the webhook and the config from a playbook.03CLI, hook and MCPReview in the editor before the pull request: the binary, the pre-push hook, the MCP tools for your agent.04CLI referenceThe whole reviewgate surface: commands, flags, report fields, error codes, the home config.05Review server for the teamHow to give the team review in the editor without handing out the model key. Written for whoever decides.06Installationdocker compose, the health check, the full environment reference.07Connecting GitLabThe bot token, the webhook, and which events get reviewed.08Connecting GitHubA GitHub App or a token, the permissions, the webhook and events, and how the gate differs.09Review configuration.reviewgate/config.yml: team rules, your own review guideline, presets, the severity gate.10Models and your own keyBring your own key, choosing a model, running one locally.11LicenseThe product is free and needs no key; what the status line in the summary means and how previously issued keys behave.12Logs and monitoringThe job tag in the logs, the structured JSON format, shipping to Graylog / ELK / Loki.13TroubleshootingThe diagnose.sh script, and why a review did not appear.