For teams shipping with coding agents

Most AI-generated PRs don't need you.Some absolutely do.

Prism triages the pull requests your team is asked to review and flags the ones touching code worth a human look — so reviewers skim the rest and spend their time where it counts.

Try the live demo
highAuth, migrations, CI config
lowTests, docs, generated files

Risk badges come with the PR Risk plan.

Risk comes from what a PR changes

Prism looks at paths, test-to-prod line ratio, and diffs. This is done in-memory on our servers, and is never written to our database. It is stored in your browser's local storage, and never sent to our servers.

Safe to skim

Tests, docs, fixtures, mocks, snapshots, and generated output. A PR made only of these is marked Low, so a thousand-line agent diff stops competing for your attention.

  • src/**/*.test.ts
  • docs/getting-started.md
  • __snapshots__/page.snap
  • __mocks__/stripe.ts
  • api.generated.ts

Worth reading closely

Auth, secrets, supply-chain manifests, destructive schema changes, and untested control-flow. One high signal marks the whole PR High.

  • src/lib/auth/session.ts
  • src/lib/permissions.ts
  • .env.production
  • package.json
  • db/migrations/003_drop.sql

A queue you can actually clear

Enough context on every row to decide without opening a tab, and one click out to the place you already review.

One queue

Every teammate gets their own queue: the GitHub PRs you're involved in, grouped by what needs your review, what's yours, what's still a draft, and what just merged.

Decide from the row

Every row carries risk, CI status, merge readiness, and diff size. Dismiss what you've handled and search the rest — your queue stays a queue.

Review where you already work

Prism doesn't rebuild code review. Click a PR and land on GitHub with the comments, checks, and history your team already uses.

Prism never stores your code

Analyzed, never stored

Prism reads what a pull request changes to score it in memory. Your code and risk verdicts aren't stored in our database. They are cached in your browser.

Only your permissions

Your GitHub sign-in shows only pull requests you could already open yourself. Risk scoring uses that same connection.

Revoke anytime

Unlink GitHub and the inbox stops loading. There's no copy of your code to delete.

👋 Hi, I'm Andrew. I built Prism because agents started opening more pull requests than I could honestly read. It's early days, and I read and reply to every piece of feedback personally. Let me know what's broken, missing, or confusing at andrew@prismstudio.dev.

Pricing

Questions

What's free, and what costs money?

The inbox is free, for as many people and repos as you like. Risk badges are the PR Risk plan at $10 per seat per month, with a 14 day trial. Billing belongs to the workspace — yours alone or your team's — and a workspace admin manages it.

How do I get risk badges?

Link GitHub so the inbox can load, then upgrade the workspace to the PR Risk plan. When you open the inbox, Prism scores pull requests for that commit — reading changed files from GitHub in memory, not writing the verdict to our servers. The badge is cached in your browser for that commit.

How does Prism decide what's risky?

A small set of signals: sensitive paths (auth, secrets, IAM, supply-chain manifests), destructive schema diffs, and a CRAP-style approximation — branch density in added production lines versus the ratio of test lines changed. One high signal marks the whole PR High. A PR made only of tests, docs, and generated files is Low. No model, no guessing at whether your code is any good — so you can always check the call yourself.

What do you store?

Never your code or diffs. Risk scoring reads which files changed, and sometimes the diff. We don't write PR identity, verdicts, or matched paths to our database. If you dismiss a pull request from your inbox, we store an opaque token tied to that PR, not the repo or PR number. These rows are deleted after 60 days. The inbox list and risk badges live in your browser, refreshed from GitHub as you use the app.

Will Prism comment on or change my pull requests?

No. Every call Prism makes to GitHub is a read. It never comments, reviews, labels, merges, or pushes, and opening a row just sends you to the pull request on GitHub.

Does it work with private repos?

Yes, and that's the normal case. Your inbox is whatever your own GitHub account can see, private repos included — Prism can't surface a pull request you couldn't open yourself. On the PR Risk plan, badges cover those same pull requests.

Can I get risk badges on my personal repos?

Yes. Personal, other-org, and OSS pull requests in your inbox are scored the same way. Every account gets its own workspace at signup, so paying as a team of one is simply one seat.

Stop reading every PR the same way

Link GitHub and see which pull requests actually need you.