heygrc
heygrc and Aikido

Different jobs, same pull request.

Aikido focuses on security, scanning code and dependencies. heygrc reads the same change for the compliance control it touches, a different category of risk. A change can be a routine networking tweak and still expose an internal system where it should not be reachable.

Aikido

Aikido is a developer security platform. It scans code and pull requests for security issues across several scanner types.

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

A networking change that exposes an internal database.

This change moves a database into a public subnet to simplify networking. The infrastructure applies cleanly.

infra/network.tf+1 −1
resource "aws_db_instance" "main" {-  publicly_accessible = false+  publicly_accessible = true}
heygrcDORA Art. 9

The change applies and the database still works. But making it publicly reachable removes the network segmentation that keeps critical systems protected, which goes to the protection measures in DORA Art. 9. heygrc is built to read an infrastructure change like this against your frameworks and cite the control it touches.

Use them together

Keep Aikido. Add the compliance layer.

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

Questions

heygrc and Aikido, common questions.

Is heygrc an alternative to Aikido?

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

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