I’ve seen how often engineering teams become heavily dependent on one or two people without really realizing it until that person is suddenly unavailable. That was the main idea behind Orgledge. I wanted to build something that could make these knowledge risks visible using signals that already exist in GitHub — without needing access to the actual source code. I initially thought about just showing things like contribution concentration and bus factor, but the idea evolved into something more useful: automatic scans, risk insights, recommendations, historical comparisons and reports for CTOs and engineering leads. I’m building this as a side project and I’m still very early. For this launch, I mainly want to validate whether this is actually a problem teams care about and get feedback from people who have dealt with it themselves.

Orgledge

Spot hidden knowledge risks in your engineering team

Spot hidden knowledge risks in your engineering team