NuHQ
The dashboard I use to run everything else — health, deployments and priorities across every project, where every number has to say where it came from.
Please note: A tool I built for my own use.
- My role
- Designer and developer. Internal tool.
- Built for
- Internal tooling
- Current status
- Internal tool, in active use. Not a product and not for sale.
- Built with
- Next.js · TypeScript · Supabase · GitHub API · Vercel API · Anthropic Claude
The story
What problem existed, and what we built.
The problem
Running a dozen systems at once means the honest answer to 'how is everything doing' is usually a guess. Worse, most dashboards will happily show you an estimate styled exactly like a measurement.
What I built
A command center that pulls live data from the code and hosting platforms, and labels every single number with its provenance — measured, synced, estimated, or entered by hand.
What it had to achieve
- Know the real state of every project without opening twelve tabs
- Never show an estimate dressed up as a measurement
- Degrade visibly when a data source is down
The owner & staff experience
One screen showing what is healthy, what needs attention, and what to do next — with every figure carrying a badge saying how it was obtained.
What the business can do
- Portfolio health across every project
- Live deployment and commit activity
- A per-project view with timeline and metrics
- An AI assistant that ranks what to work on next, clearly marked as advisory
- Visible 'not connected' and 'stale' states instead of invented numbers
How it works
The system, explained without the jargon.
If a technical term is needed below, it's explained right where it appears.
Every number declares its provenance
Measured, synced, AI-estimated and manually entered are four visually distinct things. A dashboard that blurs them is worse than no dashboard, because it is confidently wrong.
Missing data looks missing
If a token is absent or an API is down, the interface says so. It does not fall back to a plausible-looking number.
Design decisions
The choices that shaped it — and why.
Honesty over completeness
A visibly empty panel is more useful than a filled one you cannot trust. This principle is the whole reason the tool exists.
How it was built
Development process
- 1Built the live control plane against real code and hosting data
- 2Added the per-project view and provenance system
- 3Added a local collector for facts the cloud APIs cannot see
- 4Added the advisory AI planning layer
Where it stands
Status & outcome
Current status
Internal tool, in active use. Not a product and not for sale.
Outcome
It is how this portfolio audit was assembled — the project inventory behind this website came out of it.
Related projects
You might also want to see
ClaimGuard
Claims recovery platform · My own venture
A platform that helps freight carriers recover money they are owed — reading their paperwork, building the claim, and tracking it to payment.
Read the case study
Operion
Multi-tenant operations platform · My own venture
The platform behind J Kiss and Supercharged, generalized so more than one company can run on the same codebase without seeing each other's data.
Read the case studyWant something like this for your business?
Tell me how your days go and what you'd like to stop doing by hand. I'll tell you honestly what would help.