[integrations]
Eight SCMs. One review platform.
SCMs are where review lands. Task Context is how linked bug and enhancement details stay attached while the same review and evidence model runs across the estate.
GH
GitHub
Native PR comments and status checks with the same full review engine used across the rest of the platform.
Native review comments and status checks
GHE
GitHub Enterprise
Enterprise-managed GitHub with the same review depth, governance, and evidence model.
Enterprise-ready app install and deployment support
GL
GitLab
Cloud and self-managed merge-request review with the same full engine and compliance model.
Inline merge request comments and policy enforcement
BBC
Bitbucket Cloud
Pull-request review for Atlassian cloud estates without sacrificing review depth or evidence quality.
Workspace token support and comment posting
BBDC
Bitbucket Data Center
Self-hosted Atlassian review coverage for teams that do not want to migrate just to adopt AI review.
Server-side webhook validation and anchored PR comments
ADO
Azure DevOps
Pull-request review for Microsoft-centric engineering estates with strong review quality and scoped enforcement.
Azure-native pull request workflow support
GER
FlagshipGerrit
Atomic review publishing for governed engineering teams that cannot pretend Gerrit is GitHub.
Single-call review submission model
P4
Perforce
Bring strong AI review to Helix Swarm and Perforce estates that still carry critical software delivery.
Helix Swarm review compatibility
[surface proof]
Breadth only matters if the behavior is real.
If a page says the product posts native comments, validates webhooks, or emits review status in a given SCM, the page has to show that behavior.
[task context]
Intent can come from outside the SCM.
Jira, GitHub Issues, Linear, Monday.com, and Jira Data Center can feed linked task context while review still renders natively in the code host.