App hosting

The answer in CAP is BTP's hosting services: cds add portal wires a multitenant app to the HTML5 Application RepositorySAP HTML5 Application Repository service for SAP BTPserviceStores built UI5 and HTML5 applications and serves them at runtime through the approuter, so an app ships no static server of its own.sap official, btp behind the SAP Cloud Portal service, and cds add app-frontend points a single-tenant app at the Application Frontend serviceSAP Application Frontend serviceserviceOne managed entry point that hosts a built frontend, serves its static files and routes its backend calls — subscribed in the cockpit rather than deployed into a runtime.sap official, btp instead.

Not covered: cds add approuter and cds add workzone route to the same services and add no hosting of CAP's own: a hand-built application router@sap/approuterappSAP's Node.js application router: the single entry point in front of a business application's microservices, which authenticates the user, forwards each request to a backend by route and serves static content.sap official, btp, or SAP Build Work Zone's managed one through the Fiori Launchpad. CAP wires the binding; the hosting stays a BTP service either way.