Skip to main content
MergeWatch runs in your AWS account. Your code never leaves your infrastructure. There is no per-seat pricing — you pay your own Bedrock bill. The project is AGPL v3 open source, and reviews run through a multi-agent parallel pipeline rather than a single-pass model.
  • Self-hosted: No. Everything runs in your AWS account. MergeWatch has zero access to your code.
  • SaaS + BYOC: MergeWatch processes the diff in-memory to call your Bedrock endpoint. Nothing is persisted.
  • SaaS + MergeWatch Bedrock: Same as BYOC, but MergeWatch pays the Bedrock bill. The diff is processed in-memory and not stored.
You deploy MergeWatch’s Lambda stack into your own AWS account using SAM. All Bedrock calls happen from your account. You see the costs in your AWS bill.
No. Amazon Bedrock is a managed API service — AWS hosts the models. You authorize and pay for inference calls via IAM.
The review fails gracefully. A “Review failed” comment is posted on the PR, and the review is marked as “Failed” in the dashboard. You can retrigger it with @mergewatch review.
Yes. Bedrock supports Llama 3.1 70B, Mistral Large, and others. Set the model in .mergewatch.yml or in the dashboard settings.
  • BYOC: You use the mergewatch.ai SaaS for orchestration but connect your own Bedrock account via an IAM cross-account role.
  • Self-hosted: You deploy the entire stack (Lambdas, DynamoDB, API Gateway) in your AWS account. Nothing touches MergeWatch infrastructure.
AGPL ensures improvements to the core stay open source. Companies can use it freely for internal purposes. A commercial license is available for those who need it.
  • Self-hosted: No billing from MergeWatch. You pay AWS costs only.
  • SaaS: Each PR that triggers a review counts. Skipped PRs do not count.
Reviews stop until the next billing cycle. Existing reviews remain accessible.
Yes. The GitHub App requests contents: read permission to access diffs.
GitHub Enterprise Cloud: yes. GitHub Enterprise Server: not yet (planned).
Install the GitHub App on each org separately. Each installation appears in the dashboard.