Architecture Metrics — How We Calculate
The Risk Score is a weighted sum (added×5 + removed×10 + changed×3), capped at 100. Drift count is the number of projects with at least one drift report.
This guide details how each metric on the Architecture page is computed.
Risk Score (0–100)
The Risk Score is a weighted sum of resource changes detected between consecutive C4 model scans:
risk = min(100, added×5 + removed×10 + changed×3)
| Change type | Weight | Rationale |
|---|---|---|
| Removed | ×10 | Highest impact — resources deleted from Azure |
| Added | ×5 | Medium impact — new resources not in the approved model |
| Changed | ×3 | Lower impact — existing resources with modified type or name |
- 0–29: Green — low risk
- 30–69: Amber — moderate risk, review recommended
- 70–100: Red — high risk, immediate attention
The value shown is the max across all projects in your organisation.
Projects with drift
Number of projects that have at least one drift report. Each project is compared independently: its current live Azure state vs the last stored C4 model snapshot.
Risk level
Risk level is derived from the max risk score shown on the executive cards:
- Low: 0–29
- Moderate: 30–69
- High: 70–100
Risk distribution
Projects are grouped into high, moderate, and low risk buckets so teams can prioritize remediation across the portfolio.
Resources changed
Total count of Azure resources that were added, removed, or modified since the last C4 model scan. Summed across all projects with drift.
Last Drift
Timestamp of the most recent drift report generated across all projects. Indicates when drift was last detected.
Top risk project
Top risk project is the project with the highest risk score in the selected comparison mode and links directly to that project drift report.
Data source
Drift is computed by the scanner worker after each successful scan. It compares the newly saved C4 model to the previous snapshot for the same project and level, then writes a drift report to the database.