Server-rendered pages, no build step, no API layer, and navigation that feels like an app. Here is how the combination actually behaves in production — including the parts that needed real work.
A critical PHP advisory landed and one of our clients was affected. They had not asked us to look, and there was no incident to respond to yet. Here is what we did, and why we did not invoice for it.
On 21 October 2026 the PHP project shipped four releases that fix two critical remote code execution flaws. Here is what the advisories actually say, which versions are safe, and how to update a live business website without breaking it.
Core Web Vitals, what the thresholds actually are, and the handful of fixes that account for most real-world gains. Measured claims only — no invented conversion statistics.
Both are good at building business applications and neither is the obvious winner. What actually differs is rendering, hosting, hiring and what you already run — which is where the decision should be made.
Buying is usually cheaper, faster and lower-risk — until the software stops fitting how you work. A practical framework for deciding which side of that line your business is on.
If someone in your business copies data from one system into another every week, that is an integration waiting to be built. What APIs actually are, where they pay off, and what maintaining one costs.
The route from an idea to a working application, stage by stage: what happens at each one, what it produces, and where projects most often go wrong.
A working PHP application is an asset, not a liability — until its runtime stops receiving security patches. How to tell the difference between technical debt you can live with and risk you cannot.
Work with us
Whether you are planning an MVP, modernising an ageing application or looking for someone dependable to maintain what you already run, we are happy to tell you honestly what we would do.
