capire

Appearance

CAP License ​

Where can I find the new CAP license? ​

Find here the license text for the SAP Developer License 3.2 CAP.

Quote

“I am pleased that SAP has clarified the previous ambiguities in its license agreement. This enables us as SAP Partners to concentrate on the development of CAP-based SaaS and customer-specific applications without the need to engage in lengthy discussions regarding license agreements. Simultaneously, it provides our joint customers with the assurance that they will receive support when utilizing CAP as the engine for their customer-specific developments.”

Martin Stenzig, CEO, AlphaOak

tl;dr - Main Benefits and Changes ​


FAQs ​

What did we announce with CAP v9? ​

SAP SE announced a transition from the SAP Developer License 3.1 and SAP Developer License 3.2 to the SAP Developer License 3.2 CAP for all releases of all CAP libraries that are not under the Apache License 2.0. The change applies from CAP v9 (released May 2025) and all subsequent releases.

Why are we making this change? ​

The formerly used SAP Developer License 3.1 / 3.2 imposed strict rules on CAP users with respect to usage and customer support. By shifting to the SAP Developer License 3.2 CAP, SAP allows customers of SAP Business Technology Platform (BTP) or any other SAP platform to use CAP applications productively and to request support in line with their existing licensing agreement with SAP.

Which parts of CAP are affected? ​

The updated license applies for all CAP components which are not published with an Open-Source license. The license applies to both CAP Java and CAP Node.js.

What are the implications of this change for users of CAP? ​

Customers and partners and external developers in general are granted to create custom applications for productive use that are operated on BTP or any other platform licensed from SAP. In the SAP Developer License 3.2 CAP those applications are called “Customer Productive Applications”. In setups that deviate from this, CAP shall only be used for testing purposes and/or non-productive use (called “Customer Test Applications”).

While the former SAP Developer License 3.1 / 3.2 limits mass data extraction from an SAP product to a non-SAP product, including use, modification, saving or other processing of such data in the non-SAP product, the new SAP Developer License 3.2 CAP is defining an exception to the extent that the extraction is solely used for and required for interoperability with an SAP product. Allowing this, applications for e.g. product extensions are supported and interoperability of applications is enhanced.

Who is impacted by this change? ​

All users of CAP are affected starting with CAP v9.

What are the implications on the CAP Open Source strategy? ​

The change of CAP’s license model has no implications on the CAP Open Source strategy. Many CAP components and CAP plugins are already open source (mostly with Apache License 2.0) and the number will continue to grow.

What is a Customer Productive Application? ​

The SAP Developer License 3.2 CAP defines “Customer Applications”. These are in general applications developed using the CAP application programming interfaces, documentations, plugins, templates, scripts, sample code or tools. “Customer Test Applications” are for testing and non-productive use. Only if deployed and operated on BTP or any other platform licensed from SAP, productive usage is allowed and supported. These are the mentioned “Customer Productive Applications”.

What do You and Your Customer mean? ​

Some places in the SAP Developer License 3.2 CAP mention CAP users and their customers (“You and Your customers”) which should emphasize that we encourage third parties / partners to implement CAP applications for their customers as Customer Productive Applications (see What is a Customer Productive Application).

Can I get support if I have issues with CAP? ​

We offer support for Customer Productive Applications that are developed and made available by You in accordance with the SAP Developer License 3.2 CAP. You and third parties may request support in line with Your licensing agreement for SAP. All other users are referred to what is made available on the SAP Community Website by SAP at its sole discretion and by SAP Community members. For Open-Source CAP components under Apache License 2.0, the official GitHub support channels (GitHub issues) are available.

Can I continue to use previous versions of CAP that were provided under the original SAP Developer License 3.1 / 3.2? ​

The license change is not retroactive. This means, all source code and releases prior to the change remain under the SAP Developer License 3.1 / 3.2. For using CAP applications in productive environments, we strongly recommend to upgrade though. Support for older CAP versions is limited to the CAP release and support strategy that is described in CAP Release Schedule.

Will SAP provide security patches to previous releases under the original SAP Developer License 3.1 / 3.2? ​

SAP will continue to patch critical security patches, as available, to existing versions under the SAP Developer License 3.1 / 3.2 for one year, as outlined in the CAP Release Schedule. Any patches after that date will be provided under the new license only, because older CAP versions will fall out of maintenance then.

Was this page helpful?