Skip to main content

Blast Radius

Know what breaks before you change it.

​
The Problem

In microservices and multi-repo environments, no one person holds the full picture. A schema change in one service silently breaks three others. Staff engineers spend weeks tracing cross-system dependencies by hand.

​
What It Does

Connects multiple repositories into a unified context graph:
  • Traces change propagation across service boundaries
  • Answers: “what else breaks if I change this interface?”
  • Surfaces hidden coupling before it becomes a production incident

​
Try It

Example - API contract change:
Full cross-repo scan:

​
Expected Output

  • Context graph - unified dependency map across services
  • Change impact report - downstream consumers affected
  • nablr-reports/context_graph.json - machine-readable graph for CI integration

​
Who This Is For

  • Platform teams at organizations with microservices sprawl
  • Staff engineers executing system-wide changes
  • Engineering organizations preparing for major refactors or infrastructure migrations
Point nablr at each service repo in sequence using discovery before running the impact assessment. The richer the context graph, the more accurate the impact trace.