App hosting
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.
Showing artifacts, examples and content with confirmed Web Components applicability. View All UI5
Overview
A UI5 Web Components app builds to the same kind of static bundle as a freestyle one — the library's own README describes the components as suitable for anything from static web sites to complex web applications, and expects them bundled along with the rest of the app rather than pulled from a CDN — so 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 and 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 store and serve it exactly as they do any other built HTML5 frontend.
Not covered: Neither service reads what framework produced the bundle, so the flavor changes nothing about where it stops: the same boundary as the door's own assessment applies.
No community artifact is documented here.
Artifacts
Details
Coverage
For your agent
- Ref
capability:app-hosting- JSON
- /capabilities/app-hosting.json
- MCP
- Connecting an agent