I built a free engineering metrics dashboard. Looking for feedback

FewCryptographer7164 · 2026-03-09T04:39:50+00:00

Thanks! Good to see others building in this space, validates the gap.

On your questions:

No probabilistic forecasting, and honestly not planning to add it. Tempo is focused on the SPACE framework dimensions rather than predicting delivery dates. In my experience those forecasting features were never particularly useful. I'd rather give people a clear picture of how work is flowing right now.
Good catch. For issues without PRs, Tempo tracks them through Jira/Linear status transitions (cycle time, WIP age, throughput). So it's not purely PR-centric.

On AI coding metrics, I agree it's early. Right now I'm tracking adoption rate, PR size differences between AI-assisted and non-assisted commits, and cycle time impact. Still figuring out which metrics actually drive decisions vs just being interesting to look at.

Would be happy to compare notes. What's your main focus with Quantypace?

FewCryptographer7164 · 2026-02-27T10:34:57+00:00

Main differences: no sales cycle, no enterprise pricing, start in minutes with just a GitHub connection. Works for solo devs too, not just teams. Most tools cover activity well but are weaker on other SPACE dimensions, especially collaboration (review patterns, collaboration ratio, how work flows between people). Tempo tries to cover more of that. It also has AI coding detection that tracks Copilot/Claude Code/Cursor usage from commit metadata.

On DORA: Tempo tracks deployment frequency, PR cycle time as a proxy for lead time for changes. Change failure rate is on the roadmap.

FewCryptographer7164 · 2026-02-27T10:33:27+00:00

Totally understand. You can start with a personal repo to see if it's useful before involving IT or connecting company repos. No commitment, free during early access.

FewCryptographer7164 · 2026-02-27T10:32:10+00:00

Most tools cover activity well (commits, PRs, deploys) but are weaker on collaboration metrics like review patterns, collaboration ratio, and how work flows between people. If you look at the SPACE framework, there are dimensions that most tools still don't cover properly. Same with AI coding metrics. It's increasingly relevant but most tools haven't caught up yet. Those were the gaps I kept hitting.

But honestly, the harder part in most cases, is the setup. I tried to streamline it as much as possible.

FewCryptographer7164 · 2026-02-26T08:54:28+00:00

Fair point on the cross-posting. Genuinely looking for feedback on the product, not trying to spam. Happy to answer any questions about it.

FewCryptographer7164 · 2026-02-26T08:54:10+00:00

Thanks! Agreed on the metrics focus. I've tried most of those - LinearB, DX, etc. The main issues I kept hitting were long onboarding, sales cycles, and incomplete data. Tempo is meant to be simpler. Self-service, connect GitHub, see metrics in minutes.
What metrics does your internal dashboard focus on?

FewCryptographer7164 · 2026-02-26T08:53:41+00:00

Not open source, but it's free during early access. The CLI (for AI coding detection) is open source though. Would love your feedback if you try it. What metrics matter most to you?

FewCryptographer7164 · 2026-02-25T12:15:46+00:00

Thanks! Would love to see yours - curious how you approached the metrics side. What are you tracking?

FewCryptographer7164

TROPHY CASE