Cross-service change impact
See the impact of a change before you merge
Blast Radius analyzes API, schema and contract changes across repositories and highlights which services may be affected, directly inside your pull request.
The reality of growing systems
- • Multiple services evolve independently
- • Contracts change across repositories and teams
- • Dependencies are not always obvious
- • Small changes can cause delayed breakage
What Blast Radius does
- • Parses proposed changes in pull requests
- • Detects API and schema modifications
- • Surfaces potentially affected services and repositories
- • Flags risky changes before merge
How it works
- • Connect to your GitHub or GitLab repositories
- • Analyze diffs in pull requests
- • Map changes to related code across services
- • Post impact summary as a PR comment
Deployment options
- • GitHub and GitLab compatible
- • Self-hosted inside your infrastructure
- • Read-only repository access
Who this is for
- • Teams working with multiple backend services
- • Engineering leads managing legacy systems
- • Projects with cross-repository dependencies
Current stage
Blast Radius is in early development. I am working with a small number of engineering teams to build the first production-ready pilot based on real repositories and real change scenarios.
Talk through your system (30 min)