Umbraco for publishers: an MIT-licensed .NET CMS

What is Umbraco?

Umbraco is a content management system built on Microsoft .NET. The project’s repository describes it as “a free and open source .NET content management system” and lists the MIT licence. The company behind it states on its About page that it was founded in 2003, is headquartered in Odense, Denmark, and that Umbraco is the most widely used open-source CMS built on .NET. That is the company’s own claim, and we have not checked it independently.

Technically, it is an ASP.NET Core and C# application. The product page says it follows the Microsoft .NET release cadence and runs on Windows, macOS or Linux. Umbraco sells services around the free core, notably Umbraco Cloud for managed hosting.

Who is Umbraco best for?

Umbraco suits a publisher that already has, or can hire, .NET developers. A magazine or news site inside an organisation with a Microsoft-oriented IT department is the natural fit: the stack, hosting and security reviews are familiar. An agency that builds in C# can also deliver Umbraco sites for several publishing clients under one licence, since the licence has no per-site fee.

It suits less well a small newsroom with no developer. Templates, content models and integrations are code. If you want an editor to launch a site from a theme and plugins, look at the systems on the CMS directory that are built for that. Publishers that already run PHP or Node.js teams will gain little by adding a .NET stack.

Editorial workflow

Umbraco’s documentation describes five default user groups: Administrators, Editors, Translators, Writers and Sensitive Data. Writers can read, create and update documents but cannot publish, which gives a basic submit-for-review pattern. Translators are limited to read and update. Custom groups can be restricted by section, language, document and property value, so a freelancer can be limited to one section of the site.

Scheduling is built in. The documentation says each document can be scheduled for publishing and unpublishing at a set time, and Umbraco converts the editor’s local time to server time. One operational catch is stated in the same page: scheduling relies on the server making HTTP(S) requests to itself, so rewrites, DNS or firewall rules can break it, and load-balanced setups need extra configuration.

The product page also lists version control, audit trails and split-view editing. We have not opened the detailed documentation for those features, so we do not describe how approval stages work beyond the user groups above. If you need multi-step editorial approvals with named reviewers, check what the version you plan to run offers.

SEO, structured data and feeds

We did not find an Umbraco page in this research that documents built-in sitemaps, RSS feeds, structured data or redirect management, so we make no claim about them. The documentation page we tried for the redirect tracker no longer exists at that address. Because pages are rendered by templates that developers write in ASP.NET Core, titles, meta descriptions, canonical tags and JSON-LD depend on how your developers build them, or on packages you add.

For a news publisher that is a real checklist item. Before committing, confirm how a build handles an XML news sitemap, article structured data and 301 redirects when headlines or URLs change. Our guides cover what to look for, and the feature checklist lists the items.

Media, multilingual and performance

Umbraco’s product page lists built-in multilingual support, with content delivered to websites, apps and other channels. User groups can be limited by language, which helps translation teams. The language-variant documentation page we tried was unavailable, so we cannot describe how translated versions are stored or linked.

On performance and caching, the documentation pages we opened say nothing specific, and we make no claims. Publishers on Umbraco Cloud are on Azure and Cloudflare according to the vendor. Self-hosters would arrange their own caching and CDN.

Hosting and requirements

The requirements documentation states .NET 10.0 or higher for local development, with support following Microsoft’s long-term support policy. For databases it names SQL Server with a minimum of SQL Server 2016 and case-insensitive collation, and SQLite as an alternative. The database account needs read and write permissions and the db_ddladmin role for installs and upgrades.

Supported operating systems are those where that .NET version is supported, including Windows, macOS and Ubuntu and other Linux distributions. The documentation also mentions IIS on Windows Server and Azure through Umbraco Cloud. See our self-hosted guide for the general costs of running your own server.

Extending Umbraco

The headline extension point is the Content Delivery API. The documentation describes it as built-in headless capability that returns content as JSON. It is opt-in: you enable it in configuration and in Program.cs, then rebuild the DeliveryApiContentIndex in the Examine Management dashboard. It is a retrieval interface, so editors still work in the Umbraco back office.

Umbraco Cloud adds Umbraco Deploy for content synchronisation, and Umbraco Forms is included on all Cloud plans, according to the vendor. We have not checked the size of the package ecosystem and will not quote one. Extending Umbraco means writing C#, so budget developer time rather than expecting plugin installs to cover everything. Our headless guide explains when to put a separate front end on a CMS like this.

What Umbraco costs

The software costs nothing under the MIT licence, which also lets agencies build commercial products on it; see our licence guide. The costs are hosting, .NET development and support. Self-hosting needs a Windows or Linux server with a supported database, so a managed database is a likely additional line.

Umbraco Cloud’s product page lists features but no prices, offering a pricing calculator and a discovery call instead. We therefore publish no figure for it. Treat it as a quoted service and compare it against your own hosting estimate using the cost guide.

Where Umbraco falls short

• It needs .NET skills. If your team is PHP or JavaScript, the hiring and tooling cost is real.
• Built-in publishing features are documented, but we found no vendor documentation on news-specific tooling such as news sitemaps or article schema, so those may need development or packages.
• Scheduled publishing depends on the server being able to call itself over HTTP(S), which complicates load-balanced and locked-down environments.
• Managed hosting has no public price, so budgeting needs a sales conversation.
• Our assessment is from documentation only. We have not installed it, and how we test explains what that status means.

The verdict for publishers

Umbraco is a sound choice where .NET is already the house stack. It gives editors a conventional back office, scheduling and group-based permissions, and gives developers an MIT-licensed codebase and an opt-in headless API. The licence cost is zero and the managed option is there if you do not want to run servers.

It is a poor choice as a first CMS for a small newsroom with no developer, and the missing public documentation on SEO tooling means a news publisher should test a build for sitemaps, structured data and redirects before committing. Run a trial against your own checklist first.