# Deployment Scenarios To install the framework, start with the [Quickstart](/get_started/quickstart) — this page is about where the endpoint may live, per system. abap2UI5 apps run directly via an HTTP service — the fastest and simplest setup. This works on every ABAP release and with both ABAP language versions (Standard ABAP and ABAP for Cloud). But production use may need extra considerations across different system environments. ## S/4 Public Cloud In `S/4 Public Cloud`, the HTTP endpoint needs `S_DEVELOP` authorization, which makes it unfit for production. To make the app reachable for business users, install a separate frontend app and add an extra tile. See [S/4 Public Cloud](/configuration/s4_public_cloud) for details. ## S/4 Private Cloud In `S/4 Private Cloud`, you can make the HTTP endpoint reachable for business users and manage extra authorizations. To also use the SAP Fiori Launchpad, install an extra frontend app. See [Fiori Launchpad](/configuration/launchpad) for details. ## S/4 On-Premise The setup in `S/4 On-Premise` matches `S/4 Private Cloud`. Follow the [Fiori Launchpad](/configuration/launchpad) guide. ## R/3 NetWeaver The setup matches `S/4 Private Cloud`. Depending on your release, you might also be able to add the apps to Launchpads. Follow the [Fiori Launchpad](/configuration/launchpad) guide. ## R/3 NetWeaver (<7.50) For R/3 NetWeaver versions below 7.50, install the downported version with syntax tweaks for earlier releases. abap2UI5 runs on releases as far back as 7.02. See [Downporting](/advanced/downporting) for details. ## BTP ABAP Environment The setup in `BTP ABAP Environment` matches `S/4 Public Cloud`. Follow the [S/4 Public Cloud](/configuration/s4_public_cloud) guide.