Review every pull request with a panel of specialist agents

SHIP reviews each pull request with several reviewer agents, such as one for security and one for your conventions. A Builder fixes whatever blocks the merge.

For: Teams that already pay for AI code review.
Instead of: Review comments your engineers still fix by hand.

Runs today: Open a pull request and hand it to SHIP with ship delegate pr. Add --prompt-file to give that mission's Reviewer extra instructions, such as a security pass.

Join the early-access list Read the CLI guide

Answer 4 questions. SHIP emails you when it opens to you.

The Reviewer's result on a GitHub pull request, ending with the SHIP agent card that names the harness, model and run — The Reviewer's result on a pull request SHIP built. A review by several reviewers on every pull request is in early access.

How it works

Open a pull request and get one review

Step 1

Install SHIP on your repositories

Install the GitHub App and pick the reviewers for every pull request: correctness, security, your conventions, or one you write yourself.

Step 2

Read one combined review

Each reviewer checks the diff in its own sandbox, on its own model. SHIP merges their findings into one review, with the issues that block the merge first.

Step 3

Let a Builder fix what blocks

A Builder pushes a fix to the branch for each finding that blocks the merge. Your CI and the Tester run again before the pull request is ready.

Capabilities

Pick who reviews each pull request

Run the reviewer on a different model from the author

Give each reviewer its own harness and model, separate from the Builder's, so a different provider checks the code another one wrote.

Write a reviewer in your own words

Write a reviewer's instructions as a prompt file in your repository. Choose whether they add to your review conventions or replace them, for one pull request or for all of them.

Test the change on a preview too

The Tester runs the change on a preview and checks its acceptance criteria, so a review comes with evidence that the change works.

Use your own models and keys

Every reviewer runs on the credentials you connect, and your provider bills inference at your own rates.

See what each review cost

Every review reports its cost per reviewer, priced on the model that actually answered.

Comparison

Compare SHIP with CodeRabbit and Greptile

What each product's own pages say. Last reviewed October 1, 2026. Check the vendor's page before you buy.
CodeRabbit	Bills per developer seat, $24, $48 or $72 a month on annual billing, for developers who create pull requests. Pricing Reviews pull requests with multiple AI models. Pull request review Delivers a commit or a follow-up pull request from Autofix and Finishing Touches when someone asks for one. Finishing Touches Connects to your own model provider when you self-host it on Enterprise, for 500 seats or more. Self-hosted
Greptile	Bills per seat. Pro is $30 per seat a month and includes 50 credits per seat. Pricing Builds a graph index of your codebase and runs a swarm of agents on each pull request. Homepage Sends a suggested fix to your own coding agent, which applies it for you to review. Fix with your Agent
SHIP	In early access Runs each reviewer on the harness and model you choose, on your own keys. Tests the change on a preview, and fixes each finding that blocks the merge on the branch before your CI runs again. Generally available Bills per mission: one credit covers one mission of up to 3 agent-hours, and your own provider bills model usage. Key facts

FAQ

Frequently asked questions

Is multi-agent code review available today?

Partly: a review by several reviewers on every pull request is in early access. Today, run ship delegate pr on an open pull request, and SHIP reviews it, tests it and gives it back ready to merge. Add --prompt-file to give that mission's Reviewer extra instructions, such as a security pass.

Add instructions for one pull request

Does it review pull requests people wrote?

Yes. SHIP reviews pull requests written by people and by agents against the same conventions. Today you hand one over with ship delegate pr after you open it.

When is CodeRabbit or Greptile the better fit?

CodeRabbit or Greptile fits a team that wants AI review on every pull request today, as their own pages describe. Their fixes arrive when someone asks for them, or the team's own coding agent applies them. SHIP fits when a finding that blocks the merge should come back fixed on the branch, through your CI and a preview test.

Get several reviewers on your next pull request

Join early access and pick the reviewers for your repositories.

Join the early-access list

Answer 4 questions. SHIP emails you when it opens to you.