We look after a system we didn't build, whatever it's written in
PHP 5, AngularJS, old .NET, Java, WordPress with plugins from years ago. We start with an audit of the code and access, then care for the system like our own.
How we take over someone else's system
The system keeps running, and you know exactly what we're taking on.
- 1Code auditWe read the code, check library versions and the places that break most easily.
- 2AccessWe list servers, databases, repos and accounts, and help recover any missing access.
- 3Test environmentWe set up a copy of the system where changes are checked before release.
- 4CareWe take on reports, small changes and security updates on the package terms.
Signs you need someone who knows old tech
Nobody wants to touch it
The author is gone
No documentation
Replacing it costs too much
Technologies we maintain
Including versions their makers no longer support.
PHP
JavaScript
.NET
Java
CMS
Databases
How we check the results
After the takeover we track errors, audit risks closed and security updates.
- 1Audit risks closed
- 2Production errors
- 3Libraries with known holes
- 4Documented parts of the system
The documentation grows with every month of care.
Common questions
Will you talk us into a rewrite?
Not if it doesn't pay off. We say plainly what's worth changing and what can keep running.
What if we don't have the source code?
We check the server, as the code is often there. If it isn't, we tell you what can be done without it.
Can an old system be made secure?
Usually the risk can be reduced: updates, protection against attacks, backups. When that isn't enough, we suggest modernising step by step.
How long does a takeover take?
It depends on the size of the system and the access. The first step is a short audit, after which we know more.
Describe your system
Tell us what the system is built with, who built it and what's causing trouble today. We reply within one business day.