Solutions / Custom software

Legacy rewrite and rescue

A system nobody dares touch, taken over, made testable, and shipping again.

How we deliver it

• We read the code and find out what it actually does before changing anything.
• We add tests and an automated deploy, so changes stop being risky.
• We fix, rewrite or replace it piece by piece, without downtime.

How it works

A system nobody dares touch is rarely beyond saving, and rarely worth rewriting from scratch. We find out what it actually does before changing anything, make it safe to change, and only then decide how much to replace. What we find decides the plan.

Safe to change before anything changes

The first changes add nothing visible. Tests pin down what the system does today, including the odd behaviour people now rely on, and automated deploys make releasing routine. From there, each piece is replaced while the rest keeps running.

What decides it

Who still knows it

If the person who built it is still around, a few hours with them saves weeks. If not, the code and the production data are the documentation.

What must never go down

The parts the business cannot do without are replaced last, behind the same interface, with a way back.

Repair or rewrite

A rewrite is chosen only when the existing code cannot be made safe to change, never because a new stack is more appealing.

The data

Old systems keep years of records in shapes nobody remembers designing. Moving them is planned as its own piece of work, and checked against the original.

Releasing safely

Every replacement ships through tests and an automated pipeline. That is CI/CD, set up first.

Hand over or run

Your choice, per solution. We hand it over with documentation your team can work from, or we keep it running: upgrades, monitoring and incidents, with one of us on call 24/7.

Proof

Two earlier attempts to fix a slow search platform did not ship. Two of us replaced its data layer in six months, with no downtime at cutover.