DXP hosting options

This document provides an overview of various head technologies commonly used in digital experience platforms, detailing their corresponding support models and the roles of Optimizely, partners, and customers in platform, hosting, and implementation. It serves to clarify the division of responsibilities and the ecosystem surrounding different front-end development stacks within the Optimizely environment.

Optimizely-managed (modern cloud)

DXP – classic

• Type – PaaS
• Who owns infrastructure? – Optimizely
• Front-end hosting – In DXP (App Service)
• Head technology (examples) – ASP.NET Core MVC or Razor, often complemented with React or Angular or Vue components
• Support (platform or application) – Optimizely for platform or hosting, partner or customer for the solution

DXP – headless via Content Delivery API

• Type – PaaS and external front end
• Who owns infrastructure? – Optimizely DXP or customer (front end)
• Front-end hosting – Vercel, Azure, on-premises, and so on.
• Head technology (examples) – Typically Next.js or React, but also other JS frameworks (Vue, Angular, and so on)
• Support (platform or application) – Optimizely for the DXP platform, partner or customer for the front end or app

DXP – headless with Optimizely Graph and Optimizely front-end hosting

• Type – PaaS back end and managed front end
• Who owns infrastructure? – Optimizely
• Front-end hosting – Optimizely front-end hosting
• Head technology (examples) – Next.js or React through Optimizely Graph
• Support (platform or application) – Optimizely for DXP and front-end hosting, partner or customer for implementation

CMS (SaaS) and own front-end hosting

• Type – Fully CMS (SaaS)
• Who owns infrastructure? – Optimizely CMS, customer or partner (front end)
• Front-end hosting – Vercel, Netlify, Azure Static Web Apps, and so on.
• Head technology (examples) – Mainly Next.js or React via Optimizely Graph, but in practice any modern JS framework
• Support (platform or application) – Optimizely for CMS (SaaS), partner or customer for the front end

CMS (SaaS) and Optimizely front-end hosting

• Type – Fully CMS (SaaS) and managed front end
• Who owns infrastructure? – Optimizely
• Front-end hosting – Optimizely front-end hosting
• Head technology (examples) – Next.js or React (recommended today), possibly other compatible JS stacks
• Support (platform or application) – Optimizely for CMS and front-end hosting, partner or customer for implementation or UX

Own or legacy hosting

CMS 12 self-hosted

• Type – IaaS or own platform
• Who owns infrastructure? – Customer or partner
• Front-end hosting – Wherever the customer wants (App Service, AKS, VMs, …)
• Head technology (examples) – ASP.NET Core MVC or Razor or headless with React or Next.js, for example.
• Support (platform or application) – Customer or partner for infra and operations, optionally Optimizely for product support via license or maintenance

Legacy on-premises

• Type – VMs or on-premises
• Who owns infrastructure? – Customer or partner
• Front-end hosting – In own data centers
• Head technology (examples) – ASP.NET MVC, WebForms, jQuery or classic JS, possibly older SPA solutions
• Support (platform or application) – Customer or partner for operations, optionally Optimizely or partner for product support