The software your business runs on is old, and nobody will touch it. We will.
Old PHP, an end-of-life server, a framework nobody updates, a developer who's long gone. We'll tell you honestly whether to keep it, fix it or replace it, then look after it so it stops being a worry.
The signs it needs looking at
- It runs on a version of PHP that no longer gets security fixes
- The server's operating system is out of support
- It's built on a framework that's stopped moving, like CodeIgniter 3
- The person who built it has gone, and there are no notes
- Everyone's scared to change it, so changes don't happen
- Something breaks now and then, and nobody can say why
Keep it, fix it, or replace it
Most old systems need fixing, not replacing. A rebuild is the most expensive advice anyone can give you, and very often the wrong one.
It does the job and nothing's exposed. Keep it patched, backed up and watched, and leave it alone otherwise.
The usual answer. Move it onto supported PHP and a supported server, fix a specific list of things, and write down how it works. See what an upgrade to PHP 8 involves.
Only when the data model can't support what the business now needs. We'll show you why rather than ask you to take it on trust.
A review, a fixed price, then we look after it
- A System Review. We read it and tell you the good, the bad and the ugly in plain English. £250 + VAT, five working days. What it covers.
- Make it safe. Every fix in the report has its own fixed price, so you choose what gets done and in what order.
- We look after it. Updates, tested backups and someone who hears about problems first, on a monthly plan from £355 + VAT.
The day the fix isn't coming
When a critical PHP flaw was published in October 2026, the official fix only covered the newest versions. We put a stop-gap on every server we look after before the fix was out, then rebuilt every site it didn't cover on supported PHP the same night. That's what looking after old software is for. How we did it.
The four things people ask
Working and safe are different things. Once a PHP version stops getting security fixes, every flaw found afterwards stays open for good. It's fine until the day a serious one is published and there's no fix for your version. More on the actual risk.
Yes. It's most of what we do. We read the code rather than relying on documentation, and part of what you get back is a plain-English description of what your system actually does.
Usually not, and we have no incentive to: the review costs the same whatever we find. Most old systems need a list of fixes and a supported home, not a replacement.
A System Review is £250 + VAT for one system, and every fix it recommends comes with its own fixed price. Looking after it afterwards is a monthly plan from £355 + VAT.
Old software, looked after
Tell us what you have and we'll tell you where you stand.
What the system does, roughly how old it is, and who looks after it now (if anyone). If you don't know what it runs on, that's a normal answer here.
What we will cover:
- What it runs on, and whether that still gets security fixes
- Whether to keep it, fix it or replace it
- What it would take, at a fixed price
Rather talk now? Book a call or ring 01474 639 089.
We reply within one working day.
