SiloBreaker
Bus-factor and ownership-risk analysis for codebases: quantify who owns what before it becomes a delivery risk.
Problem
Repos often have a small set of people who own critical paths. When they leave or are unavailable, delivery and continuity suffer—but teams rarely quantify this until after an incident. “Bus factor” and ownership concentration are hard to measure without cloning, parsing, and aggregating history.
Solution
SiloBreaker runs an event-driven pipeline: FastAPI gateway accepts a repo target, Redis brokers the job, and a worker clones the repo, analyzes commit and file ownership, and computes bus factor and concentration metrics. Results surface so engineering and platform leads can act on risk before it bites.
Why it matters
Ownership risk is a business risk: key-person dependency slows delivery and increases attrition impact. A concrete, repeatable signal (e.g. “this repo has bus factor 2”) supports staffing, succession, and refactoring decisions. Fits dev tools, platform teams, and M&A due diligence.
Tech choices
- FastAPI — Async gateway; natural fit for “enqueue analysis” and “get result” without blocking.
- Redis — Job queue and broker; decouples gateway from heavy clone/analysis; easy to scale workers.
- Worker process — Isolates git clone and file/commit parsing so the API stays responsive; can run on a separate host or container.
- Docker — Repeatable runs for gateway + Redis + worker; same stack in dev and CI.