Umbraco vs. Optimizely (Episerver)
Optimizely is enterprise-grade, with strong built-in personalisation and experimentation (A/B testing, its wider DXP suite) as part of the core offering, higher licensing cost, and typically a bigger implementation team and budget behind it. Umbraco is open source at its core, with no per-seat licensing fee, .NET-native like Optimizely, and generally more cost-effective for mid-market projects, with personalisation available through add-ons like Umbraco Engage rather than baked into the base price. If experimentation and personalisation at scale are core to the business case and the budget supports it, Optimizely is a reasonable choice. If you want a capable, extensible CMS without enterprise licensing overhead, Umbraco usually wins on cost without giving up much on capability for most projects.
Umbraco vs. Sitecore
Sitecore sits in a similar enterprise/DXP tier to Optimizely: powerful, complex, expensive, and historically strong in large enterprise marketing organisations with the budget and team to run it properly. Umbraco is leaner, faster to stand up, and has a meaningfully lower total cost of ownership, which matters more the smaller the team maintaining the site.
Umbraco vs. WordPress
WordPress runs on PHP, has by far the largest plugin ecosystem of any CMS, and generally the lowest development cost to get something running. The trade-off is plugin quality variance and a larger security surface area as a site grows and accumulates plugins. Umbraco's ecosystem is smaller but generally higher quality, and it's a stronger fit for teams already on a Microsoft stack, or ones that want more structured content modelling than WordPress's post/page model naturally gives you.
Umbraco vs. headless-only platforms
Platforms like Contentful or Sanity are content-as-a-service: frontend-agnostic, flexible, but you build and maintain the entire front end yourself, and typically lose the built-in page-building and editor experience a traditional CMS gives non-technical editors. Umbraco isn't strictly either/or against these, it can run traditionally (coupled, rendering its own pages) or headless via its own Content Delivery API, so it's worth knowing that before ruling it out for a headless project.
How to actually choose
In rough order of what tends to matter most: budget and licensing model, what stack your team already works in (.NET vs. PHP vs. JavaScript), how important built-in personalisation and experimentation are versus something you're happy to add later, and whether you've got in-house delivery capacity or need an agency around it. None of these platforms is universally "better," they're built for different budgets and different organisational shapes.
Where I fit into this
I work specifically in Umbraco, so take the comparisons above as an honest attempt at fairness rather than neutrality I don't actually have. If Umbraco does turn out to be the right fit, see what I do, or for the agency-vs-independent-developer side of the decision, this comparison covers that in more depth.