7 docs tagged with "explanation"

What PanDev Metrics actually does: IDE plugins, Git and tracker integrations, DORA metrics, cost per feature, on-prem deployment.

PanDev Metrics on-prem is a three-component stack: Spring backend, React frontend, and PostgreSQL 17 (Redis 7 is optional). Explains components, data flow, and isolation.

PanDev Metrics plugins capture activity events from the IDE, browser, CLI, and AI tools, then turn gap-based intervals into hours — never source code.

DORA, productivity, focus, AI-coding, and cost indicators in PanDev Metrics — what each one measures, how often it refreshes, and how to read it.

PanDev Metrics on-prem runs the same product as Cloud on your own infrastructure via Docker Compose or Kubernetes. Single organization per install.

PanDev Metrics is the glue between Git, Jira, CI/CD and the IDE — the only platform that measures the real cost of a feature once you grow past 10 engineers.

When PanDev Metrics is the right tool: stories by role (engineering manager, CTO, finance, HR) and by team size (10-dev startup to 200-dev enterprise).