If you run a large Umbraco site, the hosting question rarely stays a purely technical one. It turns into a discussion about who is responsible when traffic spikes, how quickly security patches go live and what evidence your compliance team can put in front of an auditor. Downtime costs money, GDPR and ISO expectations keep rising, and most DevOps teams are already stretched.
This guide compares Umbraco Cloud, Umbraco's managed hosting, with independently managed hosting, which we call self-hosted Umbraco. Where it is relevant, we also cover Umbraco for Enterprise: the wider agreement that brings together hosting, premium products such as Engage and Compose, and enterprise support with dedicated SLAs.
As Umbraco Gold Partners, we advise on both routes, and we think Umbraco is a stronger long-term choice than custom-built or off-the-shelf CMS platforms for organisations of this size. See why Umbraco beats custom and off-the-shelf CMS.
Choose Umbraco Cloud when you want Umbraco HQ to take greater responsibility for the hosting platform, upgrade path, environments, security features and support model. Choose self-hosted Umbraco when infrastructure control, on-premise deployment, prescribed network architecture or an existing mature DevOps estate outweigh the value of managed hosting.
Both routes use the same core Umbraco CMS; the decision is primarily about the operating model, level of infrastructure control, support requirements, security responsibilities and total cost of ownership.
Understanding Umbraco Cloud & Self-Hosted
Umbraco Cloud is Umbraco's managed hosting platform, built on Microsoft Azure with Cloudflare in front of it. You get staging and live environments, deployments through Umbraco Deploy, automatic TLS, a web application firewall and point-in-time database restore, all running the same open-source CMS you could host yourself. Plans step up from Starter through Standard and Professional to a custom Enterprise tier.
Self-hosted Umbraco is that same CMS installed on infrastructure you control: your own IIS/.NET servers, a private data centre, or a general-purpose cloud such as Azure App Service or AWS. You have full control over the server stack, networking and pipelines, and patching, scaling, backups, monitoring and security evidence all become your team's responsibility.
In our experience, the right hosting choice is usually determined by operating model and governance requirements, rather than CMS functionality alone. The CMS is the same either way, so the useful question is who you want accountable for the platform once the site is live.
What We Assess Before Recommending Cloud or
Self-Hosting
We typically assess this during discovery by mapping technical ownership, release processes, integrations, resilience requirements and compliance obligations. Each one bears directly on the answer:
• Technical ownership. Who patches the platform, who picks up the call when production breaks, and who signs off upgrades? If the answers are vague or spread across several teams, that is usually the first sign managed hosting would reduce risk.
• Release process. How code moves from development to live, how many environments you need and how rollback works. Cloud's environments and Umbraco Deploy cover a lot of this, but some organisations must use a mandated pipeline.
• Integrations. Which systems the site talks to, and whether any need private network access or infrastructure-level configuration. This is the most common reason self-hosting stays on the table.
• Resilience requirements. Uptime expectations, traffic patterns, disaster recovery and who is accountable for each.
• Compliance and security evidence. What your auditors, legal team or procurement need to see, and whether the platform provider can supply it or your own team has to produce it.
• Total cost of ownership. The subscription set against the engineering time, tooling and out-of-hours cover that self-hosting requires.
Where a business already has an established platform-engineering team and prescribed infrastructure, self-hosting can remain the more appropriate route. For organisations without dedicated platform ownership, managed Cloud hosting can reduce operational dependency and create clearer accountability.
Pros & Cons Comparison
| Feature | Umbraco Cloud | Self-Hosted Umbraco |
| Setup |
Environments are provisioned on Azure with no server configuration. The number of environments |
Manual IIS/.NET install, domain, SSL and database setup. Timescales depend on your own provisioning and change-approval process. |
| Maintenance | Umbraco looks after the platform and infrastructure patching. Major version upgrades are still planned and tested with your agency. |
Your team (or agency) owns every patch, server update and upgrade, so it needs named ownership and time in the plan. |
| Scalability |
Resources step up by plan. Umbraco for |
Entirely your design. Scaling means provisioning and tuning infrastructure yourselves, which suits teams with the engineering depth to do it. |
| Support |
Varies by plan, from business-hours chat on Standard to chat and ticket support on Umbraco for Enterprise: 24/7 phone support with defined SLAs |
Depends on your in-house team or |
| Cost | Subscription pricing by plan: Starter, Standard and Professional are published, with Enterprise custom-priced (check Umbraco's current pricing). Umbraco for Enterprise is a wider agreement covering hosting, products and support. |
No Umbraco hosting fee, but you pay for infrastructure, engineering time, monitoring and incident cover. |
| Enterprise fit | Suits organisations that need clear accountability and uptime commitments without building a platform team. The full Enterprise benefits come through Umbraco for Enterprise. |
Suits organisations with an established platform-engineering function, mandated hosting or |
Where a cell mentions Umbraco for Enterprise, that benefit comes with the wider Enterprise agreement and is not part of every Cloud plan.
For organisations without dedicated platform ownership, Umbraco Cloud is usually the lower-risk route on cost, scalability and compliance. Where mature platform engineering and mandated infrastructure already exist, self-hosting can be the better fit.
When to Choose Umbraco Cloud for Enterprise
In our experience, Cloud is often the lower-risk choice when responsibility for platform patching, production support and security evidence is unclear or distributed across several teams. It tends to pay off most in these situations:
• Traffic comes in spikes. Campaigns, launches and seasonal peaks are easier to handle when capacity scales through the platform, not a change request.
• Compliance evidence is needed from the provider. Legal or procurement want ISO 27001 and GDPR documentation they can review, which Umbraco for Enterprise provides, rather than a document your own team has to write.
• There is no dedicated platform team. Nobody owns patching and production support day to day.
• You run several sites or brands. Consistent environments and deployments through Umbraco Deploy save repeated effort across the estate.
• Budget needs to be predictable. A fixed subscription is easier to forecast than infrastructure spend and incident response.
• Guaranteed support matters. 24/7 SLAs and a named Customer Success Manager on the Enterprise bundle replace internal escalation paths.
When self-hosting is still the right call
Self-hosting remains valid when an organisation already has a mature platform-engineering function, mandated hosting architecture or integrations that require infrastructure-level control. That usually means one or more of the following:
• An established platform-engineering team with on-call cover for comparable systems.
• A prescribed hosting or network architecture the site has to sit inside, or on-premise deployment requirements.
• Integrations that need private network access or configuration Cloud does not expose.
As an Umbraco Gold Partner, dotcraft has delivered Umbraco projects for clients including Z-Hotels and the Royal College of Surgeons Edinburgh, and the lessons from those projects are set out below.
Umbraco for Enterprise: The Game-Changer
Umbraco for Enterprise brings together what a large organisation would otherwise buy and manage separately. Not all of this comes with a standard Cloud subscription:
• The full Umbraco CMS with the premium add-ons included, and Cloud Professional hosting with dedicated, isolated resources.
• Engage for personalisation and analytics, and Compose for data orchestration.
• Commerce, Workflow, Forms, Deploy, UI Builder and AI tools, plus Extended Long-Term Support (XLTS) for a more predictable upgrade and security-patch cycle.
• 24/7 phone support with defined SLAs and a dedicated Customer Success Manager.
Real-World Examples
The following projects illustrate the delivery requirements we assess when recommending a hosting model, including content architecture, integrations and migration complexity. You will be able to see that we looked at improving an area of concern and increased the value with the right platform choices.
Z Hotels: platform flexibility
The challenge. Z Hotels needed a digital platform that matched its compact luxury positioning and could take on new hotels as the estate grew, while making location discovery and booking easier for guests.
What we delivered. An Umbraco build with an extensible content architecture, so new hotel portals could be deployed quickly, along with multilingual content, advanced Google Maps integration to show each hotel's location and transport links, and a booking integration that pulls in customer reviews.
Considerations. Multilingual content, maps and booking all had to sit inside a clean, simple journey, with the product and photography kept central.
The outcome. A streamlined booking journey and improved conversion rates, delivered between January and April 2024. In the words of Jamie Goldstein, Director at Z Hotels: "dotcraft translate strategic requirements into technical solutions with ease." Read the Z Hotels case study.
The lesson for Cloud vs self-hosted. The flexibility that let Z Hotels add hotels and integrations comes from the Umbraco CMS itself, so it is available on either hosting route. That moves the hosting question away from what the platform can do and onto who will run it as the
estate grows.
Royal College of Surgeons Edinburgh: upgrade and migration
The challenge. The College held content in multiple locations and needed to consolidate it and modernise its web presence as part of a wider brand refresh, with the site still running on older versions of Umbraco.
What we delivered. An upgrade from older Umbraco versions to a current, scalable, cloud-based Umbraco CMS, with a refreshed design built on the new brand guidelines, reusable components for content management, third-party integrations and content migration from the previous locations.
Considerations. Content had to be moved from several sources and integrations carried across, with user testing milestones along the way.
The outcome. A 50% reduction in page load times, a 40% average increase in performance and a 30% average increase in accessibility, delivered between April and November 2024. Neil Golightly, Head of Marketing and Communications, described it as "a fantastic collaboration across several teams within the College." Read the Royal College of Surgeons Edinburgh case study.
The lesson for Cloud vs self-hosted. In our experience, migrations are rarely a pure hosting exercise; version compatibility, custom integrations, deployment workflows, media handling and rollback planning should all be assessed before committing to a migration plan.
Cultkits: integration depth
The challenge. Cultkits needed a bespoke online retail platform to showcase thousands of original vintage football shirts, with e-commerce, content management, a blog, business intelligence reporting and powerful search for a growing catalogue.
What we delivered. A full-stack Umbraco build with bespoke faceted search, PayPal and Royal Mail integrations, an e-commerce module, a business intelligence reporting function, a UI component library and a navigation structure re-architected for SEO.
Considerations. A growing catalogue puts steady pressure on search and navigation, and payment and shipping integrations have to work reliably.
The outcome. Delivered over roughly three to four months, with the client reporting "a massive increase in turn-over and profit alike". Read the Cultkits case study.
The lesson for Cloud vs self-hosted. Integration-heavy projects are where the hosting question gets specific. For each integration we ask whether it needs anything beyond standard web hosting, such as private network access. If not, managed hosting removes a lot of operational overhead; if so, self-hosting stays in the frame.
Contact dotcraft to talk through how lessons like these apply to your own platform.
Decision FAQs: Umbraco Cloud vs Self-Hosted
Self-hosted Umbraco has no hosting fee, but the cost moves into infrastructure, engineering time, monitoring, out-of-hours cover and the effort of producing security evidence. Umbraco Cloud packages hosting, patching and support into a subscription, with published tiers running from £40 a month for Starter to £680 for Professional and custom pricing for Enterprise, while Umbraco for Enterprise is a wider agreement. We model this during discovery against your own team's time rather than quote a standard figure.
Cloud Professional and Enterprise plans use prioritised compute and Premium database performance, and Umbraco publishes a 99.9% uptime SLA from the Standard tier upwards. We would not claim Cloud always beats a well-resourced self-hosted setup on raw load times. The real difference is accountability: on Cloud the uptime commitment sits with Umbraco, and on self-hosting it sits with your team.
Umbraco for Enterprise comes with ISO 27001 certification and GDPR documentation that legal and procurement teams can review. Self-hosted setups can meet the same standards, but your team produces and maintains the evidence. Extended Long-Term Support (XLTS) gives a more predictable window of security patches and upgrades, which helps where upgrades have to pass through formal change approval.
Cloud runs the same CMS code and supports custom deployment through Umbraco Deploy, so most integrations work on either route. Where an integration needs infrastructure-level control, such as private network access or a prescribed hosting architecture, self-hosting can remain the more appropriate route. We check this integration by integration during discovery.
In our experience, migrations are rarely a pure hosting exercise; version compatibility, custom integrations, deployment workflows, media handling and rollback planning should all be assessed before committing to a migration plan. Umbraco offers assisted migration from on-premises setups. Cost depends on how far your current version is from the target and how much custom code and content has to move, so we scope it after a discovery review rather than
quote a typical figure.
Three of our Umbraco projects show different parts of the decision. Z Hotels shows platform flexibility for a growing hospitality estate, the Royal College of Surgeons Edinburgh shows the upgrade and migration side with a 50% reduction in page load times, and Cultkits shows how integration depth shapes hosting requirements.
Compose is available exclusively as a fully managed SaaS product, so there is no Compose infrastructure for you to install or run on either route, and it is not limited to Umbraco CMS. Self-hosting therefore does not rule it out; what changes is how you connect it, secure that connection and contract for it, since Umbraco for Enterprise includes Compose in a single agreement. For Umbraco's AI tools we check licensing, hosting and data-handling requirements product by product during discovery, because the answer depends on the tool and on where your data is allowed to go.
Conclusion
Both routes run the same Umbraco CMS, so the choice comes down to who you want accountable for hosting, security and support. If that answer is unclear today, Cloud is usually the lower-risk option. If you already have mature platform engineering and prescribed infrastructure, self-hosting may well be the right call.
Either way, we would rather map it with you properly. Book an Umbraco discovery call with dotcraft and we will walk through technical ownership, release processes, integrations, resilience and compliance with you before recommending a route.