Skip to content
umbracolombia

Bogotá

Umbraco in Spanish / Monthly roundup · September 2026

Umbraco roundup for September 2026, with the 2027 price list and the 13 to 17 upgrade

Umbraco's 2027 price list, a Cloud deploy error when moving from 13 to 17, a major Smidge release, Engage.AI in beta and how Umbraco developers use AI.

Author
Equipo Umbracolombia
Published
Period
September 2026
Reading
6 min

September 2026 brought no security advisory and no Umbraco release that forces work this week. The one item with a date attached is commercial: on 30 September Umbraco published its price list for 2027, and if you renew anything with Umbraco next year, that is the post to read first.

The rest of the month split into two conversations: the move from Umbraco 13 to 17, where the friction shows up in small places rather than in the code, and AI, both as new Umbraco features and as a change in how developers work.

The 2027 price list

Annual Price Update 2027 (opens in a new tab), by Mats Persson on the Umbraco blog, lists the new prices. They take effect on 1 January 2027, or at the first renewal after that date, for new and existing customers alike, and Umbraco says they are mainly based on price indexing.

Some of the lines that matter most to agencies and their clients:

  • Umbraco Cloud Starter goes from €45 to €48 a month, Standard from €280 to €290, and Professional from €730 to €765.
  • Development environments go from €45 to €48 a month and staging environments from €70 to €75.
  • Umbraco Forms goes from €100 to €105, and Umbraco Commerce from €2,800 to €2,900 a year.
  • Heartcore Professional goes from €1,100 to €1,200 a month, the largest relative increase on the list at roughly 9%.

Most of the increases sit between about 3.5% and 7%. None of them changes a platform decision. They do change a quote, and any proposal you send now that runs into 2027 should use the new figures.

The 13 to 17 upgrade, one small trap at a time

Nathaniel Nunes (opens in a new tab) wrote the most useful post of the month. His upgraded site ran fine locally and failed to deploy on Umbraco Cloud with NETSDK1045. The Kudu log explained it: the build machine had no SDK matching the project’s target framework, fell back to an older one and wrote its own global.json, producing the error it then reported. The fix is the .NET runtime setting in the Cloud portal, under Configuration, Advanced, Runtime Settings, which Umbraco’s major upgrade guide lists among the first steps. Change it before you push, and expect the site to restart.

Nunes also shipped a small package, Umbraco.Community.PropertyNavigator (opens in a new tab), that brings back the field dropdown editors used in the version 13 Content app to jump to a property on a long node. Editors on content-heavy sites notice exactly this kind of missing shortcut after an upgrade.

Vite, the build tool many backoffice extension projects use, published a beta of the 8.3 line (opens in a new tab) through its release bot, with no human author on the page. It adds devtools integration with the dev server and several build fixes. Watch it for your extension builds; a beta is not something to adopt.

Smidge gets a major version

The announcement of Smidge’s new major version (opens in a new tab) carries no byline on the page; it is written in the first person by the library’s maintainer on Shazwazza, Shannon Deminick’s blog. Smidge handles runtime bundling and minification for ASP.NET Core applications. Two fixes stand out. A long-reported production crash, with null entries appearing in bundles, turned out to be concurrent requests writing to the same list. And requests for missing cache files, which used to throw a 500 and which the author calls an easy denial-of-service path, now return a 404. It is a major version with breaking changes, including a single built-in minifier and a merged package structure, so read that list before updating a solution that references Smidge directly.

AI inside Umbraco products

Corné Hoskam (opens in a new tab) announced the public beta of Engage.AI on his blog: a copilot in the Engage section of the backoffice that answers marketers’ questions about campaigns, segments and A/B tests from Engage’s own data. It works through 17 tools, all read-only, designed from 115 questions real marketers asked. It is a separate, opt-in package built on Umbraco.AI, so a site that does not install it keeps Engage free of AI. The detail worth noting is that the copilot never presents “no data” as “zero”.

Matt Brailsford (opens in a new tab) describes an internal experiment: a “Decision” capability in Umbraco AI, with Automate actions that ask a yes/no, pick-one or score question and get back a typed answer plus a confidence value. His argument is that most AI steps in an automation are decisions, and a chat model is the wrong tool for them. He is clear about the status: “read this as where my head is at, not a roadmap promise.”

In a second post, Brailsford (opens in a new tab) solves port conflicts for anyone running several agent sessions in separate git worktrees: a package stores each worktree’s port in its own git folder. An update to the post explains why his first approach, per-worktree git config, failed: git worktree add copies that config, so a new worktree could report someone else’s port.

What community developers are saying about working with AI

Justin Neville (opens in a new tab), on the Nevitech blog, wrote the most practical of these. He reviews everything the model produces, never lets it commit, and works from specs with OpenSpec before any code is written. He also notes that recent Umbraco versions regularly catch models out with invented APIs. His line on ownership is the one to keep: “Whatever comes out of the model, your name goes on it.”

Owain Williams (opens in a new tab), on Owain.Codes, sets himself a rule: stop asking for solutions and start asking for explanations, with a set of prompts that force the model to justify its approach. In Time to reset (opens in a new tab) he goes further and questions what prompting has done to the enjoyment of coding, and proposes keeping one side project written entirely by hand.

Jeremy Wagner (opens in a new tab), on web.dev, offered a prompt for auditing a front end’s polyfills and workarounds against the Interop 2027 proposals. The proposal window has closed, but the audit prompt still works as a way to find dead weight in the front end of an Umbraco site.

Community and ecosystem

Jonas Poulsen (opens in a new tab), on the Umbraco blog, describes the Umbraco Education Program: partners teach at universities and colleges, and Umbraco provides the Fundamentals course material and certification free to students. Companies choose Umbraco when local developers exist, and developers learn it when companies use it. For the Colombian market, the program is worth a serious look from any partner with a university relationship.

In this month’s uProfile (opens in a new tab), Aaron Sadler, who maintains UmbNav, mentions that he submitted a fix to the core for a memory growth issue he found in every version since 13, and published a community package while HQ investigates. That comes from an interview, not an advisory, so confirm it in the core repository before acting on it.

What to do with September

The price list is the easy part: update your 2027 quotes. The harder part is that every upgrade post this month describes friction outside the code, in a portal setting or a missing editor shortcut. Budget the 13 to 17 move around those details, not only around the code changes, and put it in the same conversation as the 2027 renewal.

Sources