legacy takeover
Legacy support: we take over the system nobody on staff understands
The last person who understood it has left, and it still runs payroll. Engineers with 25+ years in production take it over in days, go on call, patch and fix it, and write down how it works.
Within 48 hours: a takeover plan, a fixed price and the day our engineers go on call.
Undocumented code, unpatched servers and one retired contractor who still picks up the phone.
- systemnobody left who knows it
- incidentsnights · weekends
- security patchesbehind
- documentationnone
On call within days of getting access
A senior engineer on call, patches applied, bugs fixed, runbooks and a map of the whole system.
- on-callsenior engineers
- patchescurrent
- map + runbookswritten
- migration pathpriced
How the takeover goes
- 01days 1–3
Access and shadowing
Access to code, servers and job schedules, and time with whoever keeps it alive today. We watch the system through a normal run, including the overnight batch.
- 02days 2–6
Map the system
The platform reads the whole codebase and builds the map: modules, jobs, interfaces, the database and what depends on what. Engineers check the map against what the system does in production.
- 03days 5–10
Go on call
Our senior engineers take the pager with runbooks written for the failures this system actually has. Security patches and the bug backlog are ranked by risk and fixed in that order.
- 04days 10–30
Run it, price the exit
Steady support at a fixed price, plus a priced plan to move to Go, Rust or TypeScript whenever you choose. The map and the runbooks are yours and hold everything we learned.
What the platform does, what our engineers do
Reading and mapping the codebase
Platform
COBOL, RPG, VB6, Delphi, PowerBuilder, old PHP and the scripts around them, in one pass.
Finding what depends on what
Platform
Jobs, files, tables and interfaces, so a fix in one place leaves the rest standing.
Being on call
Engineer
A senior engineer takes the page and fixes the fault, with response times written into the contract.
Security patches
Both
The platform finds outdated dependencies and exposed code. An engineer patches them and tests on a replay of your traffic.
Bug fixes
Both
Traced through the call graph by the platform, then fixed by an engineer who records the cause in the runbook.
Runbooks and documentation
Engineer
Written from real incidents, so whoever is on call next starts from what already happened.
Every fix goes into the runbook, and every page of the runbook belongs to you.
Who keeps your system running
Our engineers have been writing and running production code for more than 25 years, much of it on the stacks you are trying to keep alive: COBOL batch, AS/400, VB6, Delphi, ColdFusion, PHP from before frameworks. That makes them the best people to take your system over. The platform reads the code in one pass, and our engineers know what it means.
The fixed price, the response times and the takeover date are all in the contract. Every map, runbook and fix is yours from the first day.
Questions from the people who inherited it
Our last expert has already left. Is it too late?
The platform reads the code whether or not anyone remembers writing it, and our engineers work out the rest from the running system. If your current staff are still around, they help in the first days. If they are gone, we manage without them. Get a quote today and we start with access.
How fast can you take over?
Our engineers are on call within days of getting access, with the map and the first runbooks ready by day 6. If something is on fire right now, say so in the request and we start there. Get a quote and pick the date.
Do you support COBOL and the AS/400?
Yes, along with VB6, Delphi, PowerBuilder, ColdFusion, Classic ASP, old PHP and Perl. Any language, any database, any operating system still running in your building. Name your stack in the request and an engineer who knows it replies within 48 hours.
Will you push us into a migration?
The migration plan is priced and on the table from the first days, and the decision is yours. Support runs at its own fixed price for as long as you need it. When you are ready, the team that already knows your system does the rewrite in 30 days. Start with support today.
How do you handle access and security?
Access is scoped to what the work needs and logged, with an NDA signed first. Where the system cannot be reached from outside, we work on site and air-gapped on our own hardware. Put your access rules in the request and the plan will fit them.
Hand over the pager
Right now one person, or nobody, stands between that system and an outage. Share what it runs on and what it does today. Within 48 hours you have a takeover plan, a fixed price and the date our engineers go on call.
An engineer reads it and replies. NDA signed before any access.