Taking over, fixing and carrying forward business-critical, legacy or orphaned software — from the interface through the database and integrations to the servers and operations.
Many companies run a system they built themselves and could not work without: route planning, inventory, invoicing, customer records. Whoever wrote it has left, the documentation is thin, and everyone is afraid that one fix will break something else. First I get to know the system and write down how it works. Then I fix it step by step, at a fixed price, and every step ends with working software you can take over. The code and the documentation stay yours.
“The person who wrote it is gone.”
“It works, but we don’t know why.”
“Our IT runs it, but can’t change it.”
Logging is required, MFA is required, passwords must leave the config files — and nobody is there to build it.
The framework or the database is out of support, and in an audit that is now a finding.
A report runs for hours and nobody knows where it gets stuck.
A mobile app, an integration or an AI feature is needed — and nobody dares to open up what exists.
In an orphaned system it is rarely only the code that is orphaned: the servers, the database, the deployment and the backups are too. So I go through it layer by layer, from the interface to operations — and where needed, I change every one of them.
The system stays where it runs today — or moves where it needs to be.
According to the Hungarian supervisory authority, the policies are in place; the practical implementation is where the work remains — above all in access management and business continuity. Both are decided where someone has to change the system. And an orphaned system is a continuity risk in itself: if nobody can touch it, nobody can restore it.
Source: SZTFH (Hungarian Supervisory Authority for Regulated Activities), response to a freedom-of-information request, SZTFH-JOG/569-2/2026 (16 October 2026). The organisation count is an estimate: 2,132 audits completed on time multiplied by the published shares.
What is there, how it is built and deployed, who has access, what the risks are and what comes first — with a fixed price per item. If something is not worth fixing in code because a compensating control is cheaper, I say so.
Versioned releases with a rollback plan. Every step ends with working software you can take over — and you decide on every item.
Operations, modernisation, new features (mobile, integration, AI on your own infrastructure) — or a documented handover to your own team.
On the systems of around 20 banks, where legacy systems cannot stop, may only run on supported platforms, and every change leaves a trace.
From the mobile app through the database and servers to operations — in one pair of hands.
Read ↗306 s → 0.4 sone business-critical reportLegacy, undocumented database logic, made fast without replacing it.
Read ↗Case studies are anonymised. Named references are available on request during a technical discussion.
You have the audit report or the pen test results, and nobody to touch the findings that live in code? I assess them, fix them at a fixed price per item, and give you evidence for the next audit.
How it worksI am Lajos Tokodi. I am the one who works on your system: no handovers, no project manager, and no part of it left orphaned. I am one person — I take on one project at a time, and I have a written answer for what happens if I become unavailable.
Show me the system. I will tell you whether it is worth touching — and if it isn’t, I will tell you that too.
Book a 30-minute callThe succession plan and the supplier compliance pack are available on requesthello@tokodisoftware.com