> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anyshift.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pull request blast radius

> Map a proposed code change against live production dependencies before merge.

Tests can tell you whether code passes. They do not know which live workloads, services, datastores, and monitors depend on what the pull request changes.

<iframe width="100%" height="420" src="https://www.youtube-nocookie.com/embed/Fn7zGzLXnb0?rel=0" title="Map pull request blast radius with the Anyshift Graph API" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

## Bring production context into review

* Map the proposed change against the live production graph
* Surface every workload and service in the blast zone
* Name the monitors at risk before merge
* Give CI and coding agents the same read-only context

Engineers catch hidden dependencies during review instead of during rollback.

<Card title="Watch every Graph API demo" icon="circle-play" href="/pages/product/graph-api/overview">
  Open the complete video showcase.
</Card>