We take over systems that others built and left
When the original developer has gone, we audit the code, keep it running and improve it in safe steps. We modernise the parts that need it and leave stable parts alone.
What is included
- Code and infrastructure audit
- We review the code, dependencies, database and servers, then rank the risks.
- Access and documentation recovery
- We collect credentials, repositories and server access and document what we find.
- Stabilisation
- We fix critical bugs, patch security issues and add backups and monitoring.
- Runtime upgrades
- We move old PHP, database and operating system versions to supported releases.
- Refactoring
- We restructure the code that causes the most bugs or slows down changes.
- Replacement planning
- Where a rebuild is justified, we plan it module by module while the old system keeps running.
How it works
Audit. We get access and review the code, data and hosting.
What you receiveAn audit report with risks ranked by severity.
Stabilise. We fix urgent problems and put backups, version control and monitoring in place.
What you receiveA system that is backed up, monitored and under version control.
Modernise. We upgrade and refactor in small releases, each tested before deployment.
What you receiveRegular releases with a changelog.
Maintain. We take ongoing responsibility for the system under a support agreement.
What you receiveA named contact and agreed response times.
Right for you if
Nobody on your team fully understands a system you depend on.
Your application runs on an unsupported PHP or server version.
A full rewrite feels too risky but you can't leave things as they are.
Questions
Do you need the original developer's cooperation?
It helps, but we have worked without it. We need access to the servers and, ideally, the source code.
Will you recommend rewriting everything?
Only when the audit shows it costs less over time than repairing. Most systems improve faster through targeted changes.
How long does the audit take?
Usually 1 to 2 weeks, depending on the size of the system.
Can you move the system to our hosting at the same time?
Yes. We often combine stabilisation with a move to infrastructure we operate.