Connect Git provider
Connect your Git provider using OAuth.
See where knowledge is at risk.
Orgledge analyzes your Git activity to uncover concentrated engineering knowledge, explain the risk, and recommend what to do next.
No source code access required.
orgledge / engineering knowledge riskToday
Overall Risk68/100
↓ 12%Top Risks
payments-apiKnowledge risk89 ↑
authenticationReview concentration74 ↓
customer-serviceKnowledge risk61 →
Contribution spread18%
Bus factor1
Repositories26
Compared scan-12%
Connect your Git provider
Analyze contribution, review, and ownership metadata to identify where critical knowledge is concentrated.
GitHubAvailable
GitLabPlannedThe overlooked risk
The risk is not the person. The risk is the dependency.
Critical knowledge lives with one person
A key system depends heavily on one engineer, making the team vulnerable when that person is unavailable or moves on.
Important changes depend on the same reviewers
Only one or two engineers regularly review critical changes, creating hidden dependencies around important parts of the codebase.
Knowledge becomes isolated across the team
Engineers naturally become experts in specific systems, while valuable context and experience remain trapped within individual areas.
Key contributors can become inactive
When an experienced contributor stops working on a system, the resulting knowledge gap may remain invisible until the team needs that expertise.
Knowledge risk changes as your team changes
New hires, departures, team moves, and changing responsibilities can quietly increase knowledge concentration across your repositories.
You don't know whether the risk is improving
Teams can invest in pairing, documentation, and cross-training without having a clear way to measure whether knowledge has actually become more distributed.
Orgledge identifies knowledge concentration and organizational dependencies, not employee performance.
How does Orgledge work
From Git activity to actionable insights.
Select repositories
Choose the repositories you want Orgledge to monitor and analyze.
Repeats with every scan03 04 05
Analyze engineering signals
Orgledge analyzes contribution, review, ownership, and activity patterns to identify knowledge concentration and dependencies.
Understand the risk
The Risk Engine calculates knowledge-risk metrics. AI explains the findings and suggests practical ways to reduce the risk.
Measure improvement
Compare new scans with previous results to see where knowledge risk is improving, increasing, or remaining concentrated.
From risk to action
See the risk. Understand why. Know what to do next.
ORGLEDGE / Engineering Knowledge RiskPrevious scan ↓ 12%
payments-api
Knowledge Risk89
Contribution Spread18%
Review Concentration91%
Bus Factor1
Why is payments-api high risk?
82% of measured contribution comes from one contributor.
The next contributor accounts for only 9%.
Review activity is similarly concentrated.
What to do next
- Establish a second active reviewer
- Increase contribution from additional developers
- Improve repository documentation
Continuous monitoring and reporting
Stay informed without checking manually.
Orgledge automatically scans your repositories, compares results with previous scans, and generates reports you can keep, share, or send to leadership.
Automated scans
- Weekly scanMar 28 · 09:00
- Analysis completed26 repositories · 184 contributors
- Changes detected3 improved · 1 increased · 1 new
- Report generatedEngineering Risk Report · PDF
Engineering Knowledge Risk Report
Overall Risk68 ↓ 8
Executive summary
Knowledge risk decreased across 3 repositories. 3 risks improved, 1 new risk detected.
Top risks
payments-api89 → 72 ↓ 17
authentication74 → 68 ↓ 6
customer-service72 → 76 ↑ 4
Key signals
Contribution concentration82% → 64%
Review concentration91% → 78%
Bus factor1 → 2
Recommended focus
Continue distributing contribution in payments-api. Establish a second active reviewer.
Daily or weekly scans · Historical results · Automatic comparisons · PDF reports · Email delivery
Built for CTOs, Heads of Engineering, Engineering Managers, and Technical Leads.
Early access
Be one of the first teams to try Orgledge.
Join the early-access waitlist and discover hidden engineering knowledge risks in your engineering teams.
Frequently asked questions
Simple answers for
busy teams.
What is Orgledge?
Orgledge is an Organizational Knowledge Intelligence platform that helps engineering teams discover where knowledge and contribution are concentrated, understand the associated risk, and track whether it improves over time.
Does Orgledge read our source code?
No. Orgledge works without reading source-code contents. It focuses on GitHub metadata, repository information, README information, and contribution and activity signals.
What data does Orgledge analyze?
Repositories, contributors, commits, pull requests, reviews, contribution history, activity timestamps, changed-file metadata, and README or documentation signals.
How does Orgledge calculate risk?
The deterministic Risk Engine calculates Knowledge Risk Factor, Bus Factor, Contribution Spread, Review Concentration, and Inactivity Risk. AI interprets those signals and recommends practical actions.
Does Orgledge judge individual developers?
No. Orgledge identifies organizational dependencies and knowledge concentration. GitHub activity is treated as a signal, not proof of expertise.
Can we scan automatically and generate reports?
Yes. Orgledge supports daily, weekly, and manual scans, plus automated PDF reports and email delivery.
Who is Orgledge for?
CTOs, Heads of Engineering, Engineering Managers, and Technical Leads responsible for engineering knowledge risk and organizational dependency.
What does Bus Factor mean in Orgledge?
Bus Factor is a signal describing how many active contributors appear necessary to cover meaningful repository activity. It is not a literal prediction or proof that only one person understands a repository.
GuideWhat is bus factor? Definition, calculation and how to improve itHow much access does Orgledge need to our GitHub org?
Orgledge requests read-only OAuth access to the repositories you choose. It never requests write, admin, or destructive permissions.
Can we revoke access at any time?
Yes. You can disconnect Orgledge from your Git provider at any time, which immediately stops all further scans.
Do you support private repositories?
Yes. Orgledge analyzes both public and private repositories you explicitly select after connecting your Git provider.
How long does the first scan take?
Most first scans complete within a few minutes per repository, depending on repository size and activity history.
How much does Orgledge cost?
Pricing is not final yet. Join the waitlist for early-access terms and updates before general availability.
Is our data deleted if we delete our account?
Yes. Deleting your account permanently removes your connected repositories, scan history, and stored metadata from Orgledge.
Will Orgledge support other Git vendors or sources in future?
Yes. GitHub is available today. GitLab, and further Git vendors and sources are planned as Orgledge grows.