Different jobs, same pull request.
Graphite's reviewer is built for fast, stacked review of bugs, security, and style. heygrc rides alongside it and asks the compliance question, the control a change touches in your frameworks. A change can be clean code and still weaken how sensitive data is protected at rest.
Graphite
Graphite is a code review and merge platform with an AI reviewer that flags bugs, security, and style issues on stacked pull requests.
heygrc
heygrc reviews each pull request against the compliance frameworks your company must meet (ISO 27001, SOC 2, GDPR, and more) and cites the specific control a change touches. It is built for compliance, not code quality.
Clean code that stores a token in plaintext.
This change writes an access token to a plain column instead of through the encrypted-vault helper. The code is simpler, and it still works.
await db.tokens.insert({- token: await vault.encrypt(accessToken),+ token: accessToken, provider,})Persisting the access token in plaintext drops the cryptographic protection the prior line provided, and use of cryptography is ISO 27001 A.8.24. heygrc is built to read a change like this against your frameworks and cite the control it touches.
Keep Graphite. Add the compliance layer.
This is not a question of which tool wins. Graphite catches the bugs and quality problems heygrc never looks for, and heygrc catches the compliance issues a code review is not built to see. Running both means a pull request is checked for whether the code is good and for whether the change is compliant, two different kinds of risk, on the same diff.
heygrc does not replace your code review, and it does not certify you. It reviews changes against your frameworks and cites the control, so the compliance question is answered where the change is made. heygrc is in early access.
heygrc and Graphite, common questions.
Is heygrc an alternative to Graphite?
Not exactly. Graphite reviews your code; heygrc reviews each change for compliance against the frameworks your company must meet (ISO 27001, SOC 2, GDPR, and more) and cites the specific control it touches. They answer different questions about the same pull request, so heygrc is designed to run alongside it, not replace it.
Can I use heygrc and Graphite together?
Yes. They look at different kinds of risk on the same diff: Graphite on the code, heygrc on the compliance control a change touches. heygrc does not replace your code review.
What does heygrc check on a pull request?
heygrc reviews each pull request against the frameworks your company selected and cites the specific control a change touches, so the compliance question is answered in code review. heygrc does not certify you and is in early access.
How heygrc fits with other tools.
See also: AI code review tools in 2026.