Add retry policy to payout processor
MRMarco pushed changes after your review
Take another lookWaiting 2h
Built for GitHub + Slack
Keep every pull
request moving.
Review Relay knows whose turn it is, detects when the handoff changes, and sends the right reminder without creating notification noise.
State-aware remindersQuiet hoursTwo nudges per day maximum
Review queue
Waiting for action
Improve keyboard navigation for menus
SLReview requested from Sofia
Review requestedWaiting 5h
Cache image metadata off the main thread
CUReview requested from Daniel
Quiet hoursResumes 9:00
How it works
Review follow-up, without the follow-up work.
Connect your tools, choose a calm reminder policy, and let Review Relay coordinate each handoff.
GH
+SL
Connect GitHub and Slack
Select repositories and verify the identities that Review Relay may notify.
9:0015:00
Set a calm reminder policy
Choose one or two daily windows, quiet hours, and the repositories covered.
Review→Changes→Re-review
Let the relay track the handoff
It follows review requests, changes, replies, approvals, drafts, merges, and closes.
Purpose-built
Smarter than a scheduled reminder.
Every message is based on the current PR state, so the bot knows who can move the work forward.
Core behavior
State-aware handoffs
Review Relay distinguishes an initial review from another look after the author pushes changes or replies.
Review requestedSofia → Review PR
thenAuthor activity detectedSofia → Take another look
◎
Low-noise by default
Daily caps, quiet hours, cooldowns, snoozes, and idempotent delivery prevent reminder fatigue.
↯
Checks before every message
PR state and repository access are reconciled before delivery so stale reminders are suppressed.
⌘
Reviewer control
Reviewers can snooze or mute a PR. Authors can pause, resume, inspect, or remove subscriptions.
◇
Built for enterprise boundaries
GitHub App access, selected repositories, signed webhooks, and verified identities preserve trust.
MVP dashboard
See what is waiting, and why.
A focused view of active PRs, the current handoff, recent reminders, and configuration. Deeper analytics come later.
Active PRs12Across 4 repositories
Waiting for first review5Oldest: 7 hours
Waiting for re-review2Author activity detected
Reminders today8Within team limits
| Pull request | Current handoff | Status | Next reminder |
|---|---|---|---|
| Add retry policyacme/payments #1842 | Marco → Sofia | Re-review | Today, 3:00 PM |
| Keyboard navigationacme/web-kit #931 | Author → Daniel | First review | Today, 3:00 PM |
| Cache image metadataacme/mobile #624 | Author → Sofia | Quiet hours | Tomorrow, 9:00 AM |
Simple pricing
Start free. Pay when the team depends on it.
Pricing follows the developers receiving value—not the number of notifications sent.
Free
$0
For open source and small teams proving the workflow.
- Up to 3 active developers
- Up to 5 repositories
- 1 reminder per reviewer daily
- 7-day activity history
Recommended
Team
$3 / active developer / month
Choose the number of developers your team needs. No fixed monthly minimum during the pilot.
- Unlimited repositories, subject to fair use
- Up to 2 reminders per reviewer daily
- Custom schedules and user timezones
- State-aware re-review nudges
- 90-day activity history
Prices are shown in USD for easy comparison. Final amount and currency are shown at checkout. An active developer is a unique GitHub user who authors, reviews, comments on, or is explicitly subscribed to a Review Relay-managed pull request during the billing period. Bots are excluded.
Private pilot
Stop chasing reviews.
Keep shipping.
Join a small group of engineering teams shaping Review Relay’s first release.