Everything in CAP / Node.js
Type: 2
Domain
Origin
Signals
Node.js: Answers in Node.js
More
Group by: Type
Distributed through
API proxies with security and traffic policies and Developer Hub
Identity Authentication and Identity Provisioning as one tenant
Managed queues and topics over AMQP, MQTT and REST
Low-code SAP Build capability for custom Joule skills and agents
Binding onto hyperscaler object storage, chosen by plan
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed Redis from the hyperscaler via a BTP service binding
AI runtime on BTP with the Generative AI Hub
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.
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Ingests and retains compliance audit data from BTP
OAuth server issuing JWTs and holding scopes for BTP apps
Cloud Foundry runtime of SAP BTP for polyglot applications
Development environment on BTP for UI5, Fiori, mobile and CAP
Proxy from cloud apps to on-premise systems via Cloud Connector
Predefined CI/CD pipelines for SAP development projects
Vault for an application's passwords, keys and keyrings
Named, credentialed addresses of other systems resolved at runtime
Extracts header fields and line items from business documents
APIs and a UI5 component for document management in apps
Boolean and string flags read by applications at runtime
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Stores UI5 and HTML5 apps and serves them through the approuter
Event streaming and management platform in Integration Suite
Calls an application endpoint on a schedule and logs each run
SAP's AI engagement layer across SAP applications
Scans uploaded files over REST with ClamAV
Registers a multitenant application for subaccount subscriptions
One inbox for tasks across SAP applications and BTP workflows
SAP's capire/skills packaged for the pi coding agent
If your tool reads the open skill standard directly, install [capire/skills](artifact:capire-skills) and skip the wrapper.
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
Agent skills for CAP development, each a SKILL.md with references
Skill assessing API usage against the SAP API Policy
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Agent skill for SAP Customer Experience APIs, CDS and errors
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.