As SAP landscapes evolve and digital transformation accelerates, organizations are often faced with a key architectural decision: how to deliver a unified, intuitive, and scalable user experience across their SAP systems. Whether you’re running a single S/4HANA system or managing a hybrid landscape with multiple backends and cloud services, the way you deploy SAP Fiori apps plays a crucial role in user productivity and IT agility.
Let’s explore three core deployment models for SAP Fiori: Embedded Fiori Launchpad, Frontend Server (FES) hub deployment, and SAP Build Work Zone, comparing their capabilities, benefits, and use cases.
Embedded Fiori Launchpad (FLP)
The Embedded Launchpad model hosts the Fiori Launchpad directly within the backend system, such as S/4HANA. Both the UI components and the OData services reside in the same environment.
Key Benefits:
- Simplified architecture and reduced maintenance.
- Faster deployment, especially in greenfield implementations.
- No need for cross-system configuration or integration layers.
Considerations:
- Best suited for single-system landscapes.
- Not ideal for multi-backend or hybrid scenarios.
- Limited scalability as organizational complexity grows.
- Apart from SAP Build Work Zone, this will be the only deployment option from 2027
FES (Frontend Server) / Hub Deployment
This approach uses a dedicated SAP Gateway system to host the Fiori Launchpad and connect to one or more backend systems (e.g., S/4HANA, ECC, BW). It separates the UI layer from the application logic and data.
Key Benefits:
- Enables a central access point for multiple backend systems.
- Better separation of UI and backend services.
- Easier reuse of UI content across various SAP environments.
Considerations:
- Requires system-to-system trust setup (SAML, RFCs).
- Slightly more complex infrastructure and lifecycle management.
- May introduce latency due to remote OData calls.
- This deployment option will not be available from 2027
SAP Build Work Zone
SAP Build Work Zone is a modern, cloud-based digital experience platform built on SAP Business Technology Platform (BTP). It provides a unified entry point for SAP, non-SAP, and third-party applications, while offering advanced capabilities like business content cards, workflow integration, and enterprise branding.
Key Benefits:
- Cloud-first, scalable architecture ideal for hybrid IT environments.
- Seamless integration with SAP S/4HANA, SAP SuccessFactors, Ariba, and more.
- Extensible with custom widgets, collaboration tools, and third-party content.
- Enhanced user experience with responsive design and personalization.
Considerations:
- Requires SAP BTP subscription and initial setup.
- More configuration effort for trust, destinations, and identity provisioning.
- May involve a learning curve for teams new to BTP or SAP cloud services.
Which Approach fits your organization?
| Scenario | Recommended Approach |
| Single S/4HANA system with minimal integration needs | Embedded Fiori Launchpad |
| Multiple SAP systems needing a unified FLP (Deprecated from 2027) | Frontend Server (Hub Deployment) |
| Enterprise-wide, cloud-enabled experience with 3rd-party integration | SAP Build Work Zone |
Use Case
ETZ Global recently required to upgrade one of our clients to a new S4 HANA Version. This client was still using a Hub Deployment Landscape and with our recommendation, we established 3 various options:
- Upgrade the S4 HANA system
- Upgrade the S4 HANA and the FES System
- Move to embedded Fiori
Upgrade the S4 HANA system
With the upgrade of the backend only, our investigation concluded that many components would not be supported between the old FES and the new S4 HANA system.
Upgrade the S4 HANA and the FES System
From a user perspective it made senses to keep the same deployment option but with an upgraded system. But, taking into consideration the cost, maintenance and of course the deprecation of this option beyond 2027, this option was not feasible.
Move to embedded Fiori
As we discussed the benefits and pitfalls with the different approaches, we recommended to move embedded Fiori to future proof the infrastructure of the client as well as to prepare for the inevitable move towards SAP Build Work Zone.
Conclusion
Choosing the right SAP Fiori deployment model is not a one-size-fits-all decision. It depends on your current landscape, long-term strategy, and user experience goals. While Embedded Fiori is perfect for streamlined setups, FES offers flexibility for larger landscapes but will be deprecated soon, and SAP Build Work Zone leads the way for cloud-centric enterprises looking to provide a cohesive digital workspace.
Need help evaluating your options or planning your Fiori landscape or upgrading your S/4 System? Our team of SAP UX and BTP experts at ETZ Global are here to guide you on your journey.
