Harten Technologies

Understand the software your organisation depends on

Harten helps organisations understand complex applications and plan changes to them. We combine application analysis with business and technical review, so teams can check what their software does before committing to a replacement, migration or major change.

Why modernisation is still difficult, even with AI

A business rule can span several components

A calculation may depend on a database constraint, a background job and information from another service. Replacing it means understanding those relationships, not just translating the code. As applications grow, there is more source to examine and potentially more behaviour to reconcile across boundaries.

An explanation can be accurate and still incomplete

AI helps teams examine and explain code. But a clear account of the main workflow can still omit an exception or miss how two components interact. Teams need a way to investigate those gaps before using the account to define a replacement.

Read the independent evidence

Planning the work: the U.S. Government Accountability Office’s July 2025 review identifies three key elements of a legacy-modernisation plan: milestones, a description of the work and what will happen to the existing system. Read GAO-25-107795.

Checking AI’s use of long inputs: NoLiMa, an ICML 2025 research paper, found that the tested models became less reliable at finding information through associations as input length increased. It is a long-context benchmark, not a test of Harten or a measurement of omissions in software. Read the NoLiMa paper.

These sources inform the explanation of the problem; they are not endorsements of Harten. Harten’s own application findings can be inspected in the public case studies below.

How Harten approaches the work

From source code to the material needed to plan the change.

Wayfinder is Harten’s software intelligence platform. We use AI within a staged analysis and review process, retaining the evidence needed to revisit findings rather than relying only on a final summary.

Account for the source

We establish the source version and organise the analysis into defined work units. We retain the findings and processing records, so the intended workload and its results can be checked.

Connect and revisit the findings

We assemble findings across the application into documentation and related views, retaining intermediate findings and evidence links. We revisit the source to investigate selected gaps and contradictions, and record what remains unresolved.

Review what needs to be preserved

Your specialists help confirm business intent and supply knowledge the source cannot establish. We carry the findings into a recovered specification and proposed modernisation plan, with requirements, questions and verification work for your team to review.

Processing every planned input is not proof that every business rule has been found. The retained evidence gives Harten and your specialists something to inspect, challenge and correct before accepting requirements or committing to delivery.

See how Wayfinder works

Where to start

You need to understand an application

Find the implemented business rules, dependencies and information flows before deciding what to change. Explore application discovery

Your team needs usable documentation

Give people taking over support or development a current account of the system, rather than asking them to piece it together from old documents. Explore application documentation

You need to plan modernisation

Examine the options, dependencies and verification work before agreeing the scope and sequence of delivery. Explore modernisation planning

For the combined recovery and assessment engagement, see the scope, timetable and pricing.

Read the work before commissioning it

DEFRA PRSD-IWS

Browse the documentation, specification and proposed modernisation plan produced from 423,897 lines of publicly available application source. This is independent Harten analysis, not a DEFRA commission. Open the full case study

AWS CardDemo

Examine selected COBOL findings about payment handling, concurrent updates and rejected batch transactions, together with the questions they raise for a replacement. Read the CardDemo findings

Browse application examples · Read Harten’s papers on software change

About Harten

Harten Technologies Ltd is an independent UK software-intelligence and advisory business. Its work connects the application an organisation has today with the operational needs, business decisions and engineering work involved in changing it.

Harten was founded by Lavan Nallainathan, formerly a Director at Microsoft. His experience spans application modernisation, Azure, developer productivity and platform engineering across public-sector, financial-services and retail organisations.

Lavan’s professional background · Working with delivery partners

Discuss your application

Tell us what the application supports, what you need to decide and what is making the next step difficult. Harten will explain whether the work fits and what access and review would be needed.

Speak with Harten

Do not send credentials, production data or source code through public email. We agree the appropriate access and information-handling arrangements first.