Blog page

What owning an Umbraco site actually requires

Paying a developer by the hour does not make anyone responsible for your website. Someone still has to notice that work is needed, decide how urgent it is and make sure it gets done. On an Umbraco site, that work arrives whether or not anyone asks for new features. This is for whoever holds the budget or the supplier relationship for an Umbraco site going into 2027: what that responsibility covers, roughly what it costs, and how to decide who should carry it.

What happens after the code is generated

AI has changed what a development budget can buy. When an initial implementation can be generated in minutes, more of an engagement can go toward useful functionality, integrations and improvements that previously fell outside the scope. It has not changed evenly. Google's 2025 DORA research found AI adoption associated with higher delivery throughput and lower delivery stability at the same time. More gets shipped, and more breaks. Which of the two dominates is largely settled after the code is generated. That raises a reasonable hiring question: how much senior development experience do you still need?

Two deadlines and three routes

Umbraco 13 loses support on December 14, 2026 – 90 days from the date this was published. This is for whoever owns that decision on an Umbraco 13 site: the technical lead, or the person who signs off the budget. It assumes you already know what End of Life means. If you do not, that part is covered here . What follows is the two dates that bound the decision, three questions to open an assessment with, and three routes – separated by whether the work fits the time you have left.

Umbraco's high-severity security patch: What it means for v14, v15, and v16

A high-severity RCE in Umbraco's backoffice API, patched August 18, 2026 - what's actually fixed, what's still exposed, and why AI-accelerated scanning makes outdated versions riskier by the week.

Core Web Vitals on Umbraco: How This Site Scores Green

Real PageSpeed Insights data from kindbergco.com, tested live: what scores green, what doesn't yet, and the specific platform decisions behind each number.

Upgrading Umbraco 13 to 17: What Actually Breaks

Umbraco 13 to 17 is not a routine package bump. Here is what actually breaks at each version – the backoffice rewrite, removed property editors, the JSON serialization change – and a practical strategy for getting through it without surprises.