01 / Overview
Spot what needs attention.
See waiting reviews, inactive PRs and recent activity together. Start the day with context, not a repository hunt.
A clearer view of review delays
Find pull requests awaiting their first human review. Know what needs attention, take action on GitHub, and understand review delays over time.
Get started free Explore with fictional dataCurrently free to use · Personal and organization accounts
Fictional repositories and PRs. No GitHub data connected.
*Creation time is the fallback when readiness is unknown. Ages are fixed sample values, measured in elapsed calendar time.
A clearer review rhythm
From today’s waiting work to the patterns behind it. Three views, one shared context.
Explore with fictional data Interactive example only. No GitHub account is connected. Coverage and freshness are unavailable.
sample-studio · 2 fictional repositories
Interactive example only. No GitHub account is connected. Coverage and freshness are unavailable.
Fictional eight-day activity example. Dates use your local timezone; the final day is partial.
01 / Overview
See waiting reviews, inactive PRs and recent activity together. Start the day with context, not a repository hunt.
02 / Pull requests
Find the oldest waits across your authorized tracked repositories. Open the PR on GitHub to review or follow up.
03 / Review trends
Compare first-review and open-to-merge times over time, with medians, p75 and sample counts. Trace metrics to the underlying PRs.
The live queue includes open, non-draft PRs with no submitted human review from someone other than the author. Approvals, changes requested and submitted comment reviews count, even if later dismissed. Bots, self-reviews, conversation comments and review requests do not.
This queue measures the wait for a first review; it does not identify PRs needing another review.
The workflow
GitHub users connect selected repositories, import PRs and reviews, and open their live queue. This preview uses fictional sample data.
Start with GitHub. Complete your profile and confirm a contact email before repository setup.
Grant the GitHub App repository access, then explicitly enable tracking. Organization setup needs a verified administrator; members need an explicit owner or viewer grant.
Review imported PRs and reviews, check coverage, then follow PR links back to GitHub. Import progress and freshness remain visible.
Clear about access
Know what ReviewBeacon reads, who can see it and how to remove it.
The GitHub App uses read access to repository metadata, contents, issues and pull requests, organization members, and your email addresses. Choose selected or all repositories on GitHub; ReviewBeacon tracks only those you explicitly enable.
We use GitHub identity, repository and access information, PR titles and links, author and reviewer identities, activity dates, review states and synchronization status to show review queues and delays. Repository records do not retain source code, commit diffs or comment and review text. Notifications received from GitHub can contain private repository information.
New users need a verified contact email to set up repositories. We use a verified GitHub email when available, or ask you to verify an address. We retain your contact details and verification status to manage your account and send verification and welcome messages. Verification messages go only to your address; the operator receives a blind copy of your welcome message, which contains no private repository content. Mail to hello@reviewbeacon.dev is forwarded to the operator's inbox.
Organization data is shared with explicitly authorized members using their last verified GitHub access. When you return, ReviewBeacon can show currently stored repository data while it checks GitHub again in the background. If access changes only on GitHub, viewing can continue until a later check detects the change; failed or delayed checks do not impose a fixed time limit on this access. Removing a member in ReviewBeacon or signing out blocks subsequent access checks immediately; content already shown cannot be recalled. These actions do not delete shared organization data.
We use hosting, database, email and monitoring service providers to run ReviewBeacon. Primary storage is in Germany, and encrypted recovery copies are stored in the EU. Providers and their subprocessors may also process data elsewhere, including the United States. Email services process recipients and message content. Monitoring records help detect service problems and can include account or repository identifiers; they exclude repository titles, review text, credentials and contact details. Processing is not limited to Switzerland or the EU.
GitHub notification content expires within 30 days. Repository records remain while an account participates. Account deletion, uninstall and confirmed repository removal block access and schedule affected repository data for deletion within seven days; cleanup can be delayed. Suspension blocks access without deleting history. Signing in or refreshing GitHub access does not cancel deletion or restore removed local membership.
We keep encrypted recovery copies on a seven-day retention schedule. Copies can remain after live data is deleted. Service-provider logs and underlying backup copies follow their own retention policies, and legal retention obligations can apply.
Request repository-data deletion in Account settings, or manage repository selection and uninstall on GitHub. Signing out does not delete data. Repository-data deletion does not delete your sign-in identity, and a member's identity-deletion request does not necessarily delete shared organization records.
Privacy noticeClearer reviews. Free to use.
ReviewBeacon is currently free to use. Sign in with GitHub, confirm a contact email, and choose the repositories you want to track. Personal and organization GitHub accounts are supported. Organization access requires a verified administrator or an explicit owner or viewer grant.
Returning users can sign in with GitHub to manage selected repositories or return to their queue.
Returning user? Sign in with GitHub
GitHub sign-in verifies your identity. Repository access is checked separately, and tracking starts only when an authorized owner chooses Track and import.