There are several deployment options available for SAP Fiori. The following is an excerpt from the SAP Fiori Deployment Options and System Landscape Recommendations presentation available at https://www.sap.com/documents/2018/02/f0148939-f27c-0010-82c7-eda71af511fa.html.
In summary, for SAP S/4HANA, the embedded SAP Fiori front-end server (FES) deployment is recommended. Using the SAP FES as a central hub is still a recommended option for SAP Business Suite scenarios. You can also combine both options in a mixed scenario: an SAP Fiori front-end server hub with a central launchpad and central services such as My Inbox, combined with system-specific local launchpads.
Following SAP’s strategic directions towards SAP Intelligent Enterprise and SAP Business Technology Platform (SAP BTP), SAP is investing in a central entry point SAP Build Work Zone, standard edition (formerly known as SAP Launchpad service) on SAP BTP. This central entry point acts as UX integrator for all SAP and non-SAP solutions, for on-premise and cloud products.
The following figure shows the deployment options when focusing on an SAP S/4HANA implementation.

The on-premise deployment SAP Fiori for SAP S/4HANA with an embedded SAP Fiori front-end server is the recommended setup. To simplify the activation of SAP Fiori for SAP S/4HANA, there are task-lists to automate the setup of SAP Fiori launchpad, Fiori apps and business roles, and so on.
An SAP S/4HANA system with a dedicated SAP Fiori front-end server hub (for each SAP S/4HANA system) might be an option for certain use cases.

For multi-system SAP Business Suite scenarios, the SAP Fiori front-end server hub deployment is the recommended setup. The SAP Fiori UI components, the SAP Fiori launchpad content, and the SAP Gateway server are bundled on a central, front-end server, while the classical UIs and the business logic remains on the back-end system. This setup allows one central entry point (SAP Fiori launchpad) to business applications from multiple systems.
As the SAP Fiori UI components of SAP Business Suite systems are compatible with several back-end versions, it is also possible to connect back-end systems from different releases to a central SAP Fiori front-end server.

For multi-system scenarios with only one single SAP S/4HANA system in combination with an existing SAP Business Suite landscape, a central SAP Fiori front-end server as hub is still a possible option.
In addition to the Fiori UIs of SAP Business Suite systems, the Fiori UIs of the SAP S/4HANA system are also deployed on the central SAP Fiori front-end server. This setup requires that the SAP Fiori front-end server is upgraded to an appropriate version, which is required by the SAP S/4HANA product.
The following table shows the initial FES release and possible upgrade paths for SAP S/4HANA (all as of July 2022):
SAP S/4HANA | ...comes with FES release | ...upgrade possible to |
---|---|---|
SAP S/4HANA 1709 | SAP FES 4.0 | SAP FES 5.0 SAP FES 6.0 |
SAP S/4HANA 1809 | SAP FES 5.0 | SAP FES 6.0 SAP FES 2020 SAP FES 2022 |
SAP S/4HANA 1909 | SAP FES 6.0 | SAP FES 2020 SAP FES 2021 SAP FES 2022 |
SAP S/4HANA 2020 | SAP FES 2020 | SAP FES 2021 SAP FES 2022 |
SAP S/4HANA 2021 | SAP FES 2021 | SAP FES 2022 |
SAP S/4HANA 2022 | SAP FES 2022 | full system upgrade SAP S/4HANA 2023 |
Note
The newest SAP FES 2023 can only be installed as part of an SAP S/4HANA 2023 system. Thus, it’s not possible to upgrade only the SAP Fiori front-end server components to SAP FES 2023 for lower SAP S/4HANA releases. To consume new UI technology innovations that are delivered with SAP FES 2023, you need to do a full system upgrade to SAP S/4HANA 2023.
The SAP Fiori front-end server hub offers one central entry point (SAP Fiori launchpad) to business applications from multiple systems.

In this mixed scenario, one or several SAP S/4HANA systems are added to an existing system landscape where a central SAP Fiori front-end server as hub is already in place. For the newly added SAP S/4HANA system, the embedded FES is the recommended approach.
The Fiori UIs, the SAP Fiori launchpad content, and the SAP Gateway server are deployed on the same server as the back-end components. In consequence, there is a dedicated SAP Fiori launchpad for each additional SAP S/4HANA system. To connect the central SAP Fiori launchpad with the system-local SAP S/4HANA launchpad, a URL tile can be defined, which launches the local launchpad or an app. The benefit of this setup is that the existing SAP Fiori front-end server hub deployment is not impacted.

For scenarios with several SAP S/4HANA systems, the embedded deployment is the recommended setup. The Fiori UIs, the SAP Fiori launchpad content, and the SAP Gateway Server are deployed with the back-end components on the same server.

In this setup, every system has its own SAP Fiori launchpad. Content configuration is done on each system with local scope. An optimized runtime performance, a simplified software lifecycle and user/authorization management are all benefits of the embedded deployment.
Outlook: SAP Fiori Deployment Options 2025
SAP Fiori front-end server 2023 will be the last version which can be used as a standalone server for SAP S/4HANA or as a FES hub for Business Suite systems. In future, the embedded deployment option is planned to be the only option, meaning the SAP Fiori UIs and the back-end of SAP S/4HANA as well as the SAP FES components are installed on the same server.
For SAP Business Suite systems, SAP FES 2023 is the last front-end server version which is supported and thus has end of maintenance in alignment with SAP Business Suite. Future UI technology innovations delivered with ABAP Platform (including SAP_UI software component) will not be available for SAP Business Suite systems.

SAP offers advanced UX integration capabilities to help organizations establishing a central entry point and providing users easy access to SAP, custom-built and third-party applications, services and tasks – either from on-premise or cloud. Users also benefit from a harmonized user experience based on SAP Fiori 3 design.
SAP Build Work Zone, standard edition offers capabilities to implement a common SAP Fiori launchpad experience in the cloud, based on UX services such as branding, tasks, notifications and secure single sign-on.
From an operations perspective, connected solutions and systems remain self-contained entities regarding their software lifecycle management, authorizations and business content structure. While each system still has its local home page or launchpad as entry point, business users can preferably and conveniently access all their relevant apps through the central SAP Build Work Zone, standard edition.
Administrators have two options for integration:
- Manual integration of single applications using templates for common UI technologies such as SAPUI5, Web Dynpro ABAP or SAP GUI for HTML. Web applications can also be integrated using the generic (dynamic) URL launcher. You can configure applications to open in-place (with embedded UI using iFrames) or in a new tab.
- Advanced content federation: SAP products can serve as content providers by exposing selected business content including roles, applications, and related metadata. The data exchange is based on a Common Data Model (CDM) format, which is used to generically describe the content structure. Each provider system is responsible for exposing its content according to CDM.

When SAP Fiori apps are deployed on premise, the UI components are installed on the SAP Fiori front-end server (hub or embedded deployment). To access business data from the back-end, OData service calls are handled by the SAP Gateway component on the SAP Fiori front-end server, which calls the OData service implementation, which is done in the back-end system leveraging the Gateway back-end components.
When deploying SAP Fiori apps on SAP BTP, the SAP Fiori UI components are installed on SAP BTP while connecting to the respective back-end system using the SAP Cloud Connector. The OData request is then handled by SAP Gateway in the same way as for the on-premise setup.
With an SAP Business Suite system as back-end, there is the OData Provisioning service on SAP BTP as an alternative data access method. This lightweight service manages the OData communication. Take note of the restricted scope compared to a full SAP Gateway Server.