use cases

Find the shape of your problem

The same binary solves quite different problems depending on who is running it. Pick the situation that looks like yours and start from the configuration that fits it.

🌱

Open Source Maintainers

A free reviewer for a project with no budget, running on GitHub's free minutes, that helps first-time contributors instead of scolding them — and never gives a drive-by comment the power to make the bot act.

For maintainers
🚀

Startups

Four engineers, no reviewer to spare, and dependencies quietly rotting. Automate the review nobody has time for and the updates nobody wants.

For small teams
🏢

Platform & Enterprise Teams

Standards enforced as check runs across every repository, on your own infrastructure, with no vendor holding your source.

For platform teams
🧰

Agencies & Consultancies

Twenty client repositories on eight stacks. One config template, one workflow, and a dependency-health report the client can read.

For agencies
🏗️

Monorepos

Every manifest at every depth, discovered by walking the tree. No workspaces setting, because there is nothing to configure.

At scale
🛡️

Security & Compliance

Licence allowlists, OSV advisories, end-of-life base images and workflow supply-chain audits — enforced as blocking checks, with an auditable trail and nothing leaving your perimeter.

For security teams
🔄

Migrating off Renovate or Dependabot

buddy setup reads your existing config, converts what maps, and reports what does not. Nothing changes silently.

How migration works
🤖

Working with AI Coding Agents

When most of the diff was written by an agent, review is the bottleneck. buddy review --format agent closes the loop before the PR exists.

Close the loop

Not sure which one you are

Answer one question: what is the thing you keep not getting to?

If it is…Start here
Nobody reviews the PRs properlyAI code review
Dependencies are six months behindDependency updates
Standards exist but nobody enforces themMerge gates
The build breaks and sits red for a dayCI repair
A vendor cannot have our sourceYour CI, your keys
We cannot justify another per-seat toolLocal review — it runs with no key at all

Or just try it

bun add -g @buddysh/buddy
buddy review --light

No account, no key, no repository access. It reads your working tree and tells you what it finds.