SAP Application Frontend service

One 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.

A built UI has to live somewhere that is reachable behind a login and beside the API it talks to, and on BTP that has meant an HTML5 repository plus an application router you deploy and operate yourself. This is the managed alternative: a SaaS application, part of SAP Build, subscribed from the cockpit and tied to no runtime environment. It hosts and serves the static resources, routes backend calls to defined targets, and carries logs and observability for what it serves. Three channels put an application into it — the Generic Application Content Deployer for multi-target applications, a UI in the BTP cockpit, and @sap/appfront-cli@sap/appfront-clicliA CLI for the SAP BTP Application Frontend service, the hosted path for serving a Vue or React frontend in front of a CAP service.sap official, cap — and it keeps up to ten versions side by side on their own links, so a new one can be tested before it becomes the active one. It reads the same descriptors as the application router, which is what makes moving an existing MTA onto it a deployment change rather than a rewrite.