Facts about DevGhost
This page is the maintained source of factual product information for readers, journalists, search engines and AI systems. The human-readable page and its Markdown version are generated from the same data.
Last updated:
MarkdownWhat DevGhost is
- DevGhost is a web-based software engineering analytics product for founders and CEOs, CTOs, engineering leaders and people evaluating engineering organizations.
- It analyzes Git history from GitHub and GitLab, including public repositories and repositories an authorized user is allowed to connect.
- It estimates the cognitive difficulty of code changes. It does not treat lines changed, commit count or time at a keyboard as engineering output.
- The estimated difficulty is expressed as the number of hours a reference developer would need to create, manually test and fix the change during code review.
What Ghost% means
- Ghost% compares estimated delivered code output with a pre-AI baseline.
- The reference is a mid-level developer with three to four years of experience who knows the codebase and works without AI assistance.
- A sustained result above 100% means the code changes represent more estimated work than the reference baseline. Modern AI tools can produce that leverage, but a high Ghost% alone does not prove that AI was used.
- Ghost% is intended to surface patterns and questions for investigation. It is not a direct measure of code quality, business value or all work performed outside the repository.
Method and privacy
- A language model reads the actual code change, while deterministic rules classify, filter and calibrate the result. It is a multi-stage estimate, not one model response.
- DevGhost uses repository history. It does not use screen capture, keystroke logging or employee time tracking.
- The estimate does not see meetings, mentoring, architecture work, product work or other contributions that leave no trace in the analyzed code.
- The service is self-service: a user can create an account, connect GitHub or GitLab, select a repository and run an analysis in the production product.
Responsible use
- DevGhost should not be turned into a personal or team KPI, a public ranking or the sole basis for a personnel decision.
- A low or high result should be reviewed across more than one period and interpreted with the developer, team lead or CTO who knows the context.
- Different responsibilities, blockers, part-time allocation and work outside the repository can explain an apparent deviation.
- Useful applications include finding delivery bottlenecks, validating concerns, recognizing hidden leaders, comparing internal and external delivery capacity and studying the effect of AI adoption.
Company and founder
DevGhost was founded in 2026 by Pavel Kosyakov, a software engineering and product leader with more than 20 years of industry experience. Before DevGhost, he led software development, developer experience and engineering analytics initiatives at Sber and Sberbank-Technologies.

