The language behind a very large share of the working web, including a good deal of the estate we are asked to modernise rather than replace.
Existing PHP applications, and migrations off them. Modern PHP with typed properties and a real dependency manager is a considerably better language than its reputation, and a working system is worth more than an elegant rewrite.
We do not propose it for new work. Where a rebuild genuinely is the right call, we will say what it costs and what it risks first — most requests for a rewrite are really requests for a boundary and a test suite.
Strangler-pattern migrations, mainly: put the new system in front, move one route at a time, and keep the old application serving everything that has not moved yet, so there is never a weekend where everything changes at once.
Where this appears on the site
We work in PHP, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.
