Repository Intelligence for Engineering Leaders Public Beta

Brings your repository's evolution into focus

Calyntro analyses Git history, complexity metrics, and team ownership to give CTOs and Engineering Managers a clear view of Knowledge Silos, Absolute Churn, and architectural drift — at File, Module, and Team level.

Calyntro is currently in public beta. Core analyses are fully functional. We're actively refining the experience and welcome early feedback from engineering teams.
Try the beta → Explore the docs
3 scopes
File · Module · Team
Git-native
No agents, no instrumentation
Docker
Self-hosted, data stays yours
The Problem

Engineering decisions are made blind — every day

!
Knowledge walks out the door
When a key engineer leaves, their understanding of critical modules leaves with them. You only discover the gap when something breaks in production.
!
Technical debt is invisible until it hurts
High churn + rising complexity = the next incident. Without objective metrics, these files stay off the radar until they cause missed sprints or outages.
!
Teams drift off their modules
Effort scatters across the codebase. Without ownership visibility, you can't tell if a team is focused — or spread thin across systems they shouldn't be touching.
→ Calyntro translates your Git history into an always-current risk map — surfacing hotspots, ownership gaps, and complexity trends before they escalate.
Operational Excellence

Know which files are your next incident

Calyntro combines churn, age, and complexity into a single Hotspot score — so you can direct refactoring effort where it will have the most impact, not where it's loudest.

Hotspot Analysis
Activity Score + Structural Score identifies files that are both frequently changed and persistently unstable.
Absolute Churn
Lines added + deleted reveal files being heavily reworked — a leading indicator of unclear requirements or architectural problems.
Complexity Trend
Tracks Cognitive Complexity over time. A rising trend in a high-churn file is a code-red signal — catch it before it becomes a bug farm.
Development Trend
Compares activity across two time windows. See what's heating up, stabilising, or going cold across your entire file tree.
Absolute Churn · File Level · All Modules
File Path Status Abs Churn Added Deleted Revisions
src/mongo/db/pipeline/document_source_score_fusion_test.cpp ↑ 32,868 +22,066 −10,802 34
src/mongo/db/pipeline/expression_convert_test.cpp ↓ 12,605 +4,298 −8,307 10
src/mongo/db/timeseries/bucket_catalog/bucket_catalog_test.cpp ↑ 11,845 +7,811 −4,034 73
50 entries found · showing top 3 by Abs Churn · sortable by any column
Strategic Planning & Stability

Bring data to your architecture conversations

At module level, Calyntro aggregates hotspot scores, ownership distribution, and velocity trends into an architectural health view — the evidence base your roadmap decisions have been missing.

Module Hotspot Trend
Aggregated Activity + Structural scores reveal which architectural components are accumulating instability over time.
Module Change Frequency
Total commits per module. Outliers reveal "god modules" absorbing disproportionate maintenance effort.
Lines of Code (LOC)
Identify God Objects — massive files that should be split. Size + churn flags the highest-priority decomposition candidates.
Cyclomatic + Cognitive Complexity
The best predictor of bugs. Combined with high churn scores, complex files are the first candidates for your next refactoring sprint.
Knowledge Silos · Module Level · All Modules
Module Total Files Silo Files Silo Ratio Dominant Developer Risk
shell 112 16 14.3% Steve McClure low
client 180 4 2.2% Guillaume Racicot low
base 69 1 1.4% Billy Donahue low
9 entries found · Knowledge Silos = files owned overwhelmingly by a single developer — Bus Factor risk
Risk Management & Knowledge Retention

Reduce your bus factor before someone leaves

Calyntro maps exactly who owns what — not based on org charts, but on actual commit history. Spot single points of knowledge and fragmented ownership before they become crises.

Code Ownership
Primary contributor per file or module with ownership percentage. High single-owner concentration = high bus-factor risk.
Knowledge Fragmentation
Too many contributors signals diffusion of responsibility — no clear owner, higher communication overhead, a "junk drawer" module.
Module Ownership by Teams
Team-centric view: is your team focused on their assigned modules, or is effort scattered across systems they shouldn't own?
Top Team Contributors
Module-centric view: which teams are actually driving each component? Detect cross-team boundary violations early.
Top Team Contributors · Team Level · All Modules
Module Team 1 Team 2 Team 3
(unassigned) TeamF 100.0% — —
base TeamF 100.0% — —
bson TeamF 100.0% — —
Single-team dominance detected across all modules — no cross-team knowledge redundancy. Bus Factor risk at organisational level.
8 entries found · shows top 3 contributing teams per module by churn percentage
Deployment

Up and running in one afternoon

1
Deploy via Docker
Calyntro ships as a self-hosted Docker container. No SaaS vendor receives your code. Your IP stays on your infrastructure.
2
Import your Git history
Run the initial data import against your repository. Incremental updates keep the dashboard current with zero downtime — designed to fit existing CI/CD pipelines.
3
Filter, analyse, decide
Select any analysis — Hotspots, Ownership, Complexity Trends — filter by module and date range, and drill into any file with a single click. Session filters are saved automatically.

Your Git history already holds the answers

Calyntro surfaces them. Deploy in an afternoon, run your first hotspot analysis the same day.

We're looking for early adopters to shape the product. Beta access is free — all we ask for is honest feedback.
Join the beta → Read the docs
Self-hosted · your data stays yours Docker · no infrastructure overhead Git-native · no agents required Free during beta