heygrc and Greptile

Different jobs, same pull request.

Greptile reviews a change with context from across your repository, to catch system-wide bugs. That context is about how the code behaves. heygrc adds a different context, your compliance frameworks, and reads the same change for the control it touches. A change can be sound across the codebase and still move an obligation that lives outside the code.

Get early access by ISMS Copilot

Greptile

Greptile is an AI code reviewer that indexes your whole repository so its review of a pull request is aware of the rest of the codebase.

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.

Where they do not overlap

Sound code that keeps data longer than allowed.

This change raises a data retention window from 30 days to ten years. The job is correct, and it runs.

jobs/retention.ts+1 −1

// delete records older than the retention window- const RETENTION_DAYS = 30+ const RETENTION_DAYS = 3650await purgeOlderThan(RETENTION_DAYS)

heygrcGDPR Art. 5(1)(e)

The job is correct, but keeping personal data for ten years is far longer than its purpose needs, which is the storage-limitation principle in GDPR Art. 5(1)(e). heygrc is built to read a constant change like this against your frameworks and cite the control it moves.

Use them together

Keep Greptile. Add the compliance layer.

This is not a question of which tool wins. Greptile 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.

Get early access ← Where heygrc fits

Questions

heygrc and Greptile, common questions.

Is heygrc an alternative to Greptile?

Not exactly. Greptile 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 Greptile together?

Yes. They look at different kinds of risk on the same diff: Greptile 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.