Skip to main content
1

Create your account

Sign up at app.veridical.dev with Continue with GitHub. The first time, GitHub asks you to authorize Veridical. Your repositories, reviews, access, and billing stay inside the workspace you create.
2

Install Veridical on GitHub

Choose Connect GitHub. GitHub asks where to install the app and whether it may access all repositories or only selected ones. Selected repositories are the safer default. See GitHub App permissions for what the app can read and write.
3

Check your repositories

Back in Veridical, the repositories you picked are connected to your workspace. If one is missing, assign it on the Repositories page. A repository is reviewed only when it is both selected on GitHub and connected in Veridical.
4

Pick a plan

A public repository starts on Free as soon as it is connected: no card, no application, no form. A private repository needs a paid plan. See Plans and limits. On Pro and Team Pro, the first codebase scan of each repository you connect starts by itself, and you choose how often it is scanned again. See Codebase scans.
5

Open a pull request

Veridical reviews the pull request at its exact head commit. Findings appear inline, and a check run on that commit carries the review summary. See Read your first review.
Start from Veridical rather than from the app’s page on GitHub. An installation started on GitHub alone is not connected to a workspace, and gets no reviews, until you sign in to Veridical and connect it.

When Veridical reviews

  • A review starts on its own when a pull request is opened, reopened, or marked ready for review in a connected repository.
  • A draft pull request waits until it is marked ready for review.
  • Pull requests from dependency and release bots, such as Dependabot and Renovate, wait for a maintainer to ask with a command. Pull requests written by AI coding agents are reviewed like anyone else’s.
  • A pull request from a fork is reviewed only when a maintainer asks: comment /veridical review on it.
  • New commits do not start a review on their own, and they cancel a review of an earlier commit that is still queued or running. If the cancelled review was the pull request’s first automatic review, Veridical starts it again on the new head, up to 3 times per pull request. After a review has completed, use a command to review new commits.
  • Closing a pull request cancels a review that is queued or running.
  • Pull requests that were already open when you connected the repository are not reviewed on their own. Close and reopen one to start its first review.
  • Reopening starts a review only for a commit Veridical has not already reviewed or tried to review, apart from the one retry after a failure on Veridical’s side (see Commands).

Commands

Write the command as the first line of a comment on the pull request.
  • Only people with write, maintain, or admin access to the repository can use the commands. Veridical checks the commenter’s access with GitHub.
  • A review cancelled because the pull request was closed is not restarted by reopening it or by a command. Push a commit to get a new head to review.
  • If a review failed on Veridical’s side, it is not counted, and that commit can be tried once more: comment a command, or close and reopen the pull request.
  • If nothing happens within a few minutes, comment again.
  • With the merge gate on, a new commit needs a fresh review before its safe-to-merge check can pass. See After new commits.
Each review, including an additional review, counts against your plan’s allowance. See How reviews are counted. For what Veridical receives, keeps, and publishes, see Data handling.
Last modified on November 19, 2026