Do you give an amount or a score for our debt?

No. We show findings with proof, with a traffic light per topic. An amount is something we would have to make up.

Is a complex function the same as debt?

Not always. Complexity is a pointer. It becomes a problem when such a file also changes often and has few tests. That's why we look at that combination.

How is this different from a code quality review?

It is the same measurement, for the question of a team that is falling behind: where do I start? See also the page on code quality and architecture.

Do you pay the debt off?

No. We fix nothing. You build and decide what to fix.

Does AI make it worse?

We don't say that, and we don't cite figures we can't support. Code arrives faster, so the measurement has to run with every new version.

Measure technical debt in your code

Measure technical debt: where is it in your code?

Technical debt is work you put off and pay back later, in slower changes and more bugs. We use fixed tools on your repository and your git history to measure where that debt sits. You see where cleaning up pays off most, without an invented figure.

Updated 18 October 2026

What you can measure of technical debt

The debt itself can't be measured, its traces can. A file that is complex, changes often and has few tests is expensive to touch. Those are the places where it chafes first.

What we measure

With fixed tools, without AI, on your repository:

The most complex functions and files
Hotspots: files that are complex and also change most often
Size per language, and how much test code there is against the code
Runtimes and frameworks that no longer get updates, and whether there are lockfiles
From the git history: how old, how active, and whether the work sits with one person

Then an inspection reads the architecture

An AI model reads the code, read-only, and notes claims about how it is built. Every claim must point to a file and a line, or it doesn't go in your view. We are accountable for the check, not for the cleanup.

What we don't do

We don't convert debt into an amount or a number of days of work. That would be a figure we can't support. You get the findings with their proof and the place where they sit.

We clean up nothing. You decide what to tackle first.

The pilot is by invitation. Sign up, we check whether your application fits and email you. You connect your repository with read access only, the first check starts by itself, you see what is checked and what is proven, and then we ask what it is worth to you. Have a question first? Ask it in the message below.

Our team

Reads every sign-up and every question

Our team reads what you send and answers by email. A conversation only happens if you ask for one: with the people who do the work, not a salesperson.