This page provides technical information on the internals of Reviewpad.
Reviewpad is a web code review tool for Git projects. It provides a seamless integration with code hosts such as Bitbucket, GitHub and GitLab (including their self-hosted versions) with a modern interface for code reviews that combines the best of code visualisation methods and static code analysis technology.
Table of Contents
Key Design Features
Reviewpad has the following key design features:
- On-premise deployments. You can setup Reviewpad in a single developer environment, in a server for dozens of developers to use or even scale it with a kubernetes cluster for hundreds of developers. You can monitor all Reviewpad's requests for maximum security.
- Zero configuration required. You don't need to configure your team members or configure review settings - Reviewpad mirrors the permission system from the code hosts so that users only have access to the same information as they would have there. The same is applied to actions - you can't merge a pull request on Reviewpad unless you can do it on the code host.
- Easy adoption curve. Reviewpad integrates seamless with code hosts. That means that in a team of 10 developers, you don't need all 10 developers to use Reviewpad in their review process at first. Because all the actions in Reviewpad are propagated back and forth between code hosts, a subset of the team can safely use it for reviews without breaking the existing review process.
It has been designed to ease security concerns that are connected with any tool that handles sensitive and propriety information such as code, comments and personal information. If you have any security concerns or require further information contact our security team.
General Security Information
Reviewpad is distributed through Docker images so that it can be self-hosted easily. This can be either a developer machine or a server in the organisation. A running instance of Reviewpad does not communicate with Reviewpad.com servers or any non-disclosed third-party to send any information. Reviewpad instances do not communicate between them - for trials of Reviewpad Cloud, we provide access to an instance that is running in an isolated environment from other users so that there is no possibility of information leaks between environments.
For further investigation you can inspect the Docker images from the free plan on dockerhub.
Reviewpad is an abstraction layer on top of existing code hosts that use git such as Bitbucket, GitHub and GitLab.
Reviewpad integrates with a code host so that communication is performed bidirectionally. That is, an action on Reviewpad (e.g. submission of a user review) is sent to the code host using their REST or GraphQL API. An action on the code host is propagated back to Reviewpad through Webhooks.
Communication between code hosts and Reviewpad requires extra configuration and typically done in the Team plan. However, we provide special refresh actions that actively probe the code host through their APIs to keep your instance of Reviewpad up-to-date with actions in the code host that were not yet processed by Reviewpad.
Reviewpad is composed of two main components:
- Front-end service: Web react application that implements the review interface. This is the main service that users interact with in their browser. In terms of network, the front-end service only communicates with the back-end service.
- Back-end service: Microservices application that exposes a REST API.
The following diagram presents an overview of Reviewpad's architecture.
Other components necessary for Reviewpad to work are:
- PostgreSQL database that stores permanent information.
- Docker volume that Reviewpad uses to store git projects.
For more information on how to deploy Reviewpad to your team check visit
If you have any security concerns or require further information contact our security team.