About CodeVitals

Where It Started

Axel Hunter was running a dev agency called Dev, in when the same question kept coming up from clients: “Is my team actually productive?” The honest answer was: “I don’t really know.”

Every time a client asked, the process was brutal. Pull up GitHub. Read through weeks of pull requests. Count commits. Try to form a picture from fragments of activity spread across multiple repos. Write a report. Repeat every month. It was unsustainable — and it still didn’t answer the question properly.

CodeVitals was built to automate that entire process. Connect to GitHub once, and get a clear health score for any engineering team — without reading a single line of code.

Our Mission

Make engineering team health visible to the people who need it most — founders, managers, and agency owners who don’t have a technical background but are responsible for engineering outcomes.

Right now, the only way to understand how a dev team is doing is to read code, dig through GitHub, or rely on what developers tell you. That gives technical people an advantage and leaves everyone else flying blind. CodeVitals closes that gap.

How We Think About It

CodeVitals is like WHOOP for dev teams. Just as WHOOP tracks your body’s vital signs and tells you whether you’re recovered and ready to perform, CodeVitals tracks your engineering team’s vital signs and tells you whether the team is healthy and moving well.

We measure three things: Output (how much your team ships), Quality (how well code is reviewed), and Process (how smoothly work flows through the team). Together they form an Overall Health Score — a single number from 0 to 100 that gives you a starting point for any conversation about engineering performance.

CodeVitals does not judge individual developers. It does not create leaderboards or rank people against each other. It is a diagnostic tool — built to surface problems early so managers can act before those problems become missed deadlines or budget overruns.