Cross-service change impact
See the impact of a change before you merge
Project status
This project is no longer active. Over a few months I explored this idea, talked to engineers, and tried to validate it through direct sales. The conclusion was clear: while the problem exists, it’s not a priority for teams right now. Leaving this page up as a reference.
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
Context
This concept was explored as part of an early-stage validation process. The focus was on understanding how teams handle cross-service changes and whether proactive impact detection is something they would adopt.
If this problem becomes relevant for your team in the future, feel free to reach out.