Techdebt — Debt Register, Interest & Refactor Priority

Techdebt — Debt Register, Interest & Refactor Priority — a premium, 100% offline digital tool by Aceplore. Runs entirely in your browser: no accounts, no subscriptions, your data never leaves your device.

A private, offline register of the code you have not fixed and what it costs every month — payback in months, the horizon that decides it, and the debt that actually hurts because the code keeps changing. 34 tools in one, and it never hides which horizon produced the answer.

34 built-in tools in one app. A register carrying principal, interest, impact, frequency, effort and risk; principal totalled and by area, INTEREST in hours a month — the number that makes the case — and interest in money at your rate, with the hours kept visible because the hours are what was estimated; PAYBACK as principal over interest, a payback ranking, a HORIZON view giving the cost of doing nothing over 6, 12 and 24 months against the cost of fixing now, and a break-even month per item — 40 hours against 3 a month repays in 13.333333 months, so over a 12-month horizon fixing is 4 hours WORSE and over any longer one it is better, and Techdebt shows the horizon rather than presenting one as the answer; a weighted priority score with the formula and weights editable and printed, a ranking that states the MARGIN between neighbours, and an effort against impact quadrant; areas with files touched and change rate, a HOTSPOTS view combining debt with CHURN — because 40 hours in code nobody touches costs nothing — incidents per year against the debt recorded there, and a risk view separating items whose argument is risk from items whose argument is cost; dependencies with a valid fixing ORDER by topological sort and cycles REPORTED rather than followed; sprint capacity, allocation with overflow flagged, a schedule and a burndown of principal; an ACCEPTED view holding debt you decided to keep with its reason and review date, a review-due list and a stale list; plus CSV exports, a JSON backup and a Method page.

Interest. The running cost of not fixing — the number that makes the case.

Score. 8 × 5 ÷ 13 = 3.076923, with the weights editable and printed.

What's included:

• Techdebt.html
• Quick-Start-Guide.html
• How-To-Use-Guide.html
• README.txt
• LICENSE.txt

Includes a personalized welcome wizard, an interactive guided tour, a ⌘K command palette, light/dark themes with 8 accents, and one-click JSON backup & restore.

Techdebt is a planning, costing and record-keeping tool for software and infrastructure work. Every figure it reports is computed by a stated formula from the numbers YOU enter, and every figure carries its UNIT, because a millisecond, a byte, a request, a vCPU-hour and a user-minute are different quantities and confusing them is the classic failure in this field. Byte and month conventions are settings and are printed beside the figures they produced — 1 KB = 1,000 bytes and 1 KiB = 1,024 bytes are both correct and they disagree. Where something is consumed against an allowance, the consumed amount, the remaining amount floored at zero and the overage are reported separately, because a negative remaining renders as headroom and that is how an outage gets missed. Where a figure rests on an assumption — a hit ratio, a growth rate, a base event rate, an hourly price — it is labelled an assumption at the point of use and is yours to change. It runs entirely in your browser with no network access of any kind: it cannot reach a server, a registry or a cloud account, and it reports only what you recorded. It does not predict an outcome and is not a guarantee of uptime, of a deploy, of a bill, of compliance or of security posture, and nothing in it is legal advice.