DryDock

Assess your codebase health and how it uses AI

Many technology leaders know their codebase is slowing delivery or holding back modernisation. Yet, they can’t identify which technical issues are causing problems and what needs attention first.

With DryDock, Crosstide’s codebase assessment platform, our engineering team can quickly analyse one or more repositories. You receive a repeatable view of technical health and AI usage, with clear priorities for action.

Complete the form, then choose a time to discuss which DryDock assessment fits your priorities.

DryDock_Assessment_Hero (1)

Complete the form below, then choose a time to book your introductory DryDock discovery call.

DryDock: How it works

DryDock combines repository analysis with review and guidance from Crosstide’s engineering team. The assessment gives technical and business leaders a clearer view of the current position and what to do next.

The process gathers evidence across the repositories and supporting material agreed for the assessment. This creates a consistent view across systems, rather than a collection of separate opinions.

Crosstide then works through the results with technical and business leaders, explains what is driving each priority and helps determine the most appropriate next steps.

Book a Discovery Call

What DryDock delivers

DryDock combines repository analysis with review and guidance from Crosstide’s engineering team. The assessment gives technical and business leaders a clearer view of the current position and what to do next.

01

Crosstide icons_website_Aquamarine__Health and life_icon

__Health and life_icon

A trackable health score

Each repository receives a health score from 0–100 and A–G grades. The same version of the code receives the same score, while analysis of historical versions shows how its health has changed.

02

__Data as a revenue-driver_icon

Technical Assessment

Reviews engineering, infrastructure, documentation, delivery, resilience and AI maturity. This includes code quality, security, testing, dependencies, architecture, ownership and DORA delivery metrics.

03

Crosstide icons_website_Aquamarine__Speed to market_icon

__Faster speed to market_icon

AI Usage Assessment

Maps models, providers, agents and tool calls across the codebase. It also examines token and cost usage, evals, guardrails, sensitive-data exposure and observability.

04

Crosstide icons_website_Aquamarine__Impact at scale_icon

__Impact at scale_icon

Evidence to investigate

Findings are linked to the relevant file and line. DryDock can also use supporting context from documentation, Confluence exports and ticketing systems.

05

Crosstide icons_website_Aquamarine__Increase the velocity and quality of software teams_icon

__Increase the velocity and quality of software teams_icon

Remediation priorities

Recommendations are grouped as P1: act now, P2: plan soon and P3: improve. Estimated effort helps leaders decide what to fund, what to plan and what can wait.

06

Crosstide icons_website_Aquamarine__Tech allowance_icon

__Tech allowance_icon-1

Exec briefings & reports

You receive an executive briefing, technical report and prioritised roadmap. Detailed guidance helps your engineering team, delivery partner or chosen coding agent carry out the work.

01

A trackable health score

Each repository receives a health score from 0–100 and A–G grades. The same version of the code receives the same score, while analysis of historical versions shows how its health has changed.

02

Technical Assessment

Reviews engineering, infrastructure, documentation, delivery, resilience and AI maturity. This includes code quality, security, testing, dependencies, architecture, ownership and DORA delivery metrics.

03

AI Usage Assessment

Maps models, providers, agents and tool calls across the codebase. It also examines token and cost usage, evals, guardrails, sensitive-data exposure and observability.

04

Evidence to investigate

Findings are linked to the relevant file and line. DryDock can also use supporting context from documentation, Confluence exports and ticketing systems.

05

Remediation priorities

Recommendations are grouped as P1: act now, P2: plan soon and P3: improve. Estimated effort helps leaders decide what to fund, what to plan and what can wait.

06

Exec briefings & reports

You receive an executive briefing, technical report and prioritised roadmap. Detailed guidance helps your engineering team, delivery partner or chosen coding agent carry out the work.

Frequently asked questions

01

How is DryDock different from an off-the-shelf analysis tool?

Off-the-shelf tools commonly focus on one part of the technology stack and leave your team to interpret the results. DryDock examines technical health, delivery, resilience and AI usage. Crosstide’s engineering team then reviews the findings, identifies the important issues and recommends what to do next.

02

Does DryDock make changes to our code?

The assessment is read-only. Where appropriate, you can add a human-gated fix workflow. Proposed changes are presented as reviewable diffs and must be approved before a pull request is opened. DryDock does not write directly to your repository.

03

Do we need to fix everything DryDock finds?

No. DryDock separates issues that need immediate attention from improvements that can be planned or left until later. This helps prevent a long list of findings from becoming an impractical programme of work.

04

Which DryDock assessment do we need?

The Technical Assessment examines the overall condition of the codebase and delivery environment. The AI Usage Assessment provides a detailed view of how AI is being used, including models, agents, costs and controls. The discovery call will help determine the appropriate scope.

05

Who carries out the work after the assessment?

You choose. The recommendations can be implemented by your engineering team, an existing delivery partner or Crosstide. The reports and implementation guidance are designed to support whichever route you select.