Peer Reviews for Pros

All the tools you need in one place. For manual and agentic work.

mac·windows·linux·github · gitlab · bitbucket
async function refreshSession(token: string) { const session = await store.find(token); if (!session) throw new SessionNotFound(); try { return await store.refresh(session); } catch (err) { console.log(err); throw err; logger.error({ err, ctx: 'session.refresh' }); throw err; }
Rules · 47 active
log-and-rethrow31×
no service-to-service db22×
named exports for utils18×
Result<T,E> in /core11×
Source · #842 #1019 #1183
Built by engineers from
StripeGitHubVercelDatadogShopifyFigma
Why Gremium

A reviewer that already knows your codebase.

Generic AI review missed the point. Gremium reviews against your repo's history — the patterns your team has already enforced thousands of times in real PRs.

Voice

Reviews in your team's voice

Catches the things your senior engineers would catch, because it learned from the things they already caught. Every rule links to the past PRs that taught it.

Onboarding

Junior onboarding, built in

New engineers get the team's tribal knowledge applied to their PR in minutes, not after three rounds of review. The senior on call gets their afternoon back.

Signal

Less noise, higher signal

Rules are evidenced by repeated enforcement in your history. One-off opinions don't become rules. Mute any rule once and it stays muted across the team.

How it works

Your team has already written the rules.

Point Gremium at a repo. It ingests the review record — what got flagged, what got fixed, what got merged without comment — and builds a rules layer specific to your codebase.

Rules come from patterns repeated across your history, weighted by how consistently they were enforced in review. You see every rule before it goes live.

The rule shown opposite was extracted from three real PRs and is enforced by four reviewers on your team.

error_handling/log_and_rethrow.zed31× enforced
// extracted from #842 · #1019 · #1183- catch (e) { console.log(e); throw e; }+ catch (err) { logger.error({ err, ctx }); throw err; }// applied 31× in past reviews · 4 reviewers
Objections

Honest answers, ahead of time.

How is this different from CodeRabbit, Greptile, and the others?

They review against general best practices and a model's prior training. Gremium reviews against your repo's history — the specific rules your team has already enforced thousands of times in past PRs. If your team rejects a pattern, Gremium will too. If your team's fine with it, Gremium won't waste a comment.

Will it just add noise to our PRs?

Gremium only flags patterns it has strong evidence for in your history — rules that appear repeatedly in past reviews, fixes, or rejected PRs. One-off opinions don't become rules. You can mute any rule with a single click; it won't come back. The goal is fewer comments than your current AI reviewer, not more.

Is our code and PR data safe?

Your code is sent over TLS to the LLMs Gremium uses for review and is never used to train any model — ours or the providers'. PR history used for rule extraction is processed in an isolated workspace tied to your account. For teams that need stricter guarantees, the Enterprise Server runs Gremium fully inside your VPC — your code, your PR history, and the model calls all stay on your infrastructure.

Won't it just learn the bad habits in our old PRs?

Gremium weights rules by how consistently they were enforced in review — not by how often a pattern appears in code. Antipatterns that slipped through don't become rules; patterns your reviewers fixed do. You also see every rule before it goes live and can remove any you disagree with.

Pricing

Free where it counts. Paid where it's serious.

Desktop

Free, forever

For individuals and small teams

  • Mac, Windows, Linux
  • Unlimited personal & team repos
  • Full PR-history rule extraction
  • Reviews on every new PR
Download
Enterprise Server

Self-hosted

Runs entirely inside your VPC

  • SSO, audit logs, RBAC
  • Bring your own LLM provider
  • Code never leaves your infra
  • Onboarding with the founders
Talk to sales
// guarantee

If Gremium doesn't surface rules your team would actually enforce within the first review cycle, uninstall and we'll personally walk through the rule set with you to figure out why.

Download

Get Gremium for your machine.

macOS
  • Loading latest release…

Blocked on first launch? Open System Settings → Privacy & Security and click Open Anyway.

Windows
  • Loading latest release…

Blocked on first launch? Click More info, then Run anyway.

Linux
  • Loading latest release…

On RHEL 9 or an older distro? Use the Flatpak: the .rpm needs WebKitGTK 4.1 and the AppImage glibc 2.35+.

All releases on GitHub →

Stop re-explaining the same five rules in every PR.

Download Gremium, point it at a repo, and watch it read what your team has already taught itself.