Data· Client work · anonymized

Impact-Tracing Knowledge Graph

A Neo4j graph linking IT assets to the business services they support, so a regulated enterprise can trace the business impact of an asset failure.

roleGraph database, backend, and frontend

impact~4 months — two-person build, delivered into the existing CMDB

Neo4jFastAPIAngularag-Grid

Problem

An audit requirement: trace the business impact of an IT asset failure. The data was siloed across systems.

What I built

It was a two-person build. A founder owned discovery and export; I owned the graph database, the backend, and the frontend.

Neo4j links IT assets to the business services they support. A FastAPI backend serves graph queries to an Angular frontend with ag-Grid drill-downs and overview analytics.

Graph data was pushed into the client's existing CMDB.

  siloed source systems
       │  discovery + export (founder)
       ▼
  Neo4j: IT assets ──supports──▶ business services
       │
       ├──▶ FastAPI graph queries ──▶ Angular + ag-Grid drill-downs
       │
       └──▶ pushed into the existing CMDB

Decisions and tradeoffs

A graph over relational tables, because impact tracing is multi-hop.

Tables over a graph visualization, because a force-directed view is unreadable at that scale, and auditors drill down from overviews.

Pushing into the existing CMDB, so teams didn't have to adopt a new tool.

Results

Delivered in about four months.

next case studyPersistent Agentic Memory