App hosting
Where a built frontend lives and what serves it — the static files of a frontend application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.
Overview
The HTML5 Application Repository stores a built UI5 or HTML5 application and serves it through the application router@sap/approuterSAP'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; the Application Frontend Service does the same without a runtime of your own to deploy to.
No community artifact is documented here.
Where a built frontend lives and what serves it — the static files of a UI5 application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.
The HTML5 Application RepositorySAP HTML5 Application Repository service for SAP BTPStores 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 stores the static HTML, CSS and JavaScript a built UI5 app compiles to, and the application router reads it from there at runtime; the Application Frontend serviceSAP Application Frontend serviceOne 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 hosts the same kind of built app as a subscribed SaaS application instead.
Not covered: Neither service is UI5-specific: both store any built HTML5 frontend the same way. SAP-samples/ui5-deploymentsSAP-samples/ui5-deploymentsA sample that deploys one UI5 freestyle application to SAP BTP, Cloud Foundry Environment through three approuter setups, standalone, managed and hybrid, each built into an MTA archive.sap official, ui5 packages a UI5 app for these two paths and demonstrates the packaging, not the hosting itself.
No community artifact is documented here.
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 BTPStores 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 serviceOne 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/approuterSAP'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.
No community artifact is documented here.
Artifacts
Seen working
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
Details
Coverage
For your agent
- Ref
capability:app-hosting- JSON
- /capabilities/app-hosting.json
- MCP
- Connecting an agent