UpCore

1. General information

UpCore is intended for companies with large IT departments and software engineering teams. The system analyzes code without manual developer reports and builds management metrics for specialists, projects, stacks and the whole organization.

2. Functional characteristics

2.1 Source code analysis

• connection of repositories and loading of change history;
• filtering of noise: generated code, copy-paste, renames and syntax-only changes;
• identification of actual changes in lines, expressions, functions and modules;
• calculation of cyclomatic, cognitive, logical and technology complexity;
• support for language, framework, legacy and new-technology specifics.

2.2 Efficiency assessment

• calculation of code effort in hours and money;
• comparison of expected effort with event, timesheet or worklog data;
• more than 50 factors: project stage, team composition, task complexity, contribution, result quality, bugs, reviews and architecture value;
• detection of anomalies, productivity decline, burnout and schedule risks;
• tracking dynamics after process and AI-tool adoption.

2.3 Grading and development

• determination of real developer grade;
• comparison with project, stack, company and market averages;
• detection of over-skill and under-skill for project tasks;
• individual development plan preparation;
• reports for performance review, onboarding, rotation and staffing decisions.

2.4 Project and vendor management

• project ranking by efficiency, code quality and risks;
• schedule forecasting based on actual team efficiency;
• audit of external teams and real delivery scope;
• financial result assessment by project and specialist;
• matching developers to projects by technology profile and proven competencies.

2.5 AI assistant

• natural-language search across system data;
• explanation of inefficiency causes;
• highlighting anomalies and assessment factors;
• preparation of 1:1, review and management recommendations;
• analysis of AI tool usage efficiency and prompt history.

3. Architecture and integrations

UpCore includes a web interface, server API, code analysis module, calculation model, data storage, integration module and AI assistant. Components can be deployed in an isolated customer environment.

Integrations

• Git repositories: GitLab, GitHub, Bitbucket and compatible Git servers;
• task managers and worklogs: Jira, YouTrack, Redmine and API integrations;
• SSO and accounts: LDAP, SAML, OpenID Connect;
• corporate reporting: BI dashboards, CSV/JSON exports and API;
• LLM modules: on-prem model or external provider by agreement.

Security

• offline installation is supported;
• access is role-based;
• source code can be analyzed inside the customer perimeter without external transfer;
• user and system events are logged;
• backups and retention follow customer policy.

4. Installation

4.1 Environment requirements

4.2 Customer-perimeter installation

1. Agree deployment architecture, integrations and security requirements.
2. Prepare servers, domain name, TLS certificate, accounts and database access.
3. Receive UpCore distribution package and license key.
4. Deploy containers via Docker Compose or Kubernetes manifests.
5. Configure services, database, SSO, Git integrations and access rights.
6. Run database migrations and service health checks.
7. Connect pilot repositories and start initial analysis.
8. Check reports, user roles and event logs.

4.3 SaaS connection

In SaaS mode, the customer receives access to a protected UpCore web environment. By agreement, code analysis can run through an agent inside customer infrastructure, with only aggregated metrics sent to the cloud environment.

5. Operation

This section describes daily operation after installation or SaaS connection. It is intended for system administrators, engineering managers and customer-side support owners.

5.1 User roles

• Administrator manages settings, users, integrations and access rights.
• IT manager reviews company metrics, projects, risks and financial results.
• Project manager analyzes team, schedule, effort and result quality.
• Team lead uses reports for reviews, 1:1s, development and task distribution.
• HR reviews grades, onboarding dynamics, development plans and people risks.
• Developer sees personal metrics, feedback and development plan.

5.2 Main scenarios

1. Connect project, repository and working-hours source.
2. Run initial code history analysis.
3. Check dashboards for efficiency, grades, risks and financial result.
4. Configure regular analysis of merge requests, tasks and releases.
5. Use reports to manage projects, develop specialists and control vendors.

5.3 Operation schedule

5.4 First login

1. Sign in via issued account or SSO.
2. Check company details, timezone, working calendar and base currency.
3. Create groups: organization, projects, teams and roles.
4. Add users or import them from the corporate identity system.
5. Check access to logs, integrations and monitoring.

5.5 Project connection

1. Create project card and specify stack, team, analysis period and responsible manager.
2. Connect Git repository via token, SSH key or service account.
3. Connect tasks and working-hours source.
4. Map UpCore users to commit, merge request and task authors.
5. Configure exclusions for service branches, generated files, external libraries and test repositories.
6. Save settings and run initial analysis.

5.6 Analysis control

• Status is displayed in the processing queue and project card.
• Initial analysis loads repository history and links it with tasks.
• Repeated analysis is incremental.
• Unavailable sources move the job to waiting or error status with a reason.
• The administrator can restart calculation, change schedule or disable a source.

5.7 Reports

• Developer report: efficiency, contribution, resulting code quality, dynamics and team comparison.
• Project report: rating, losses, complexity, size, duration, growth and schedule risks.
• Code report: contribution, architecture complexity, review quality and bug level.
• Reports support planning, performance review, vendor control and task redistribution.

5.8 Access management

• Rights are assigned by role and visibility scope.
• Developers see personal metrics and recommendations.
• Project managers see their project and team data.
• Administrators manage integrations, users, system settings and logs.
• When an employee leaves, the account is blocked and history remains for reporting.

5.9 Backup and restore

• Database, configuration, integration keys and system settings are backed up.
• Recommended mode: daily backup, at least 30 days retention, quarterly restore test.
• Restore is performed from the latest valid backup with integration and report checks.

5.10 Typical cases

5.11-5.16 Additional procedures

• Regular synchronization: configure schedule, history depth, error notifications and test run.
• Version update: backup, test environment update, migration, production window and rollback plan.
• Monitoring: web UI, API, queues, database and event log.
• Incidents: critical, high, medium and low priority with support escalation.
• User termination: logout, account blocking, access review and data handling by policy.
• Go-live checklist: roles, repositories, tasks, user mapping, analysis, reports, backups and support process.

6. Lifecycle and support

• Product development is performed by OOO Dexmobile.
• New versions are released when improvements and fixes are ready.
• Implementation and training support is provided during the first two months of the pilot.
• Issues are registered by email or in an agreed Service Desk system.
• Critical issues are handled with priority; response times are fixed in the support agreement.
• Documentation is updated when functions, installation requirements or operation rules change.

7. Rights holder