Everything in UI5
Type: 2
Domain
Origin
Signals
More
Group by: Capability
Distributed through
APIs and a UI5 component for document management in apps
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Development environment on BTP for UI5, Fiori, mobile and CAP
IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
Joule's generative AI inside SAP Build Code
Development environment on BTP for UI5, Fiori, mobile and CAP
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Stores UI5 and HTML5 apps and serves them through the approuter
Key-user adaptation and personalisation for UI5 apps on SAP BTP
Role-based portal sites with pages, apps and widgets
One inbox for tasks across SAP applications and BTP workflows
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
Predefined CI/CD pipelines for SAP development projects