When partners evaluate SAP BTP ABAP Environment, one of the first questions is simple: What does it actually cost to get started?

With the introduction of 0.5 ABAP Compute Units (ACU), the answer has become much more attractive.

Instead of starting at 1 ACU, partners can now begin with 0.5 ACU (8 GB runtime memory), making development, test and demo landscapes significantly more cost-efficient.

At the same time, SAP BTP ABAP Environment supports two delivery options:

Multitenant SaaS solution – operated by the partnerAdd-On Product – installed and operated by the customer

Both options can be combined depending on your business model.

Commercial Model for Partners

To build and commercialize solutions on SAP BTP ABAP Environment, partners operate within the SAP PartnerEdge – Build (PE Build) commercial model.

This model provides the foundation for:

Developing and running solutionsDelivering them as multitenant SaaS or Add-On ProductsPublishing offerings via the SAP Store

A Typical Starting Point

A realistic setup for partners usually includes a small development landscape.

Development & Demo (TDD PAYG)

Development system → 0.5 ACUTest/Demo system → 0.5 ACUPersistence → 2 HCU per system

This setup is typically used for:

DevelopmentTestingCustomer demos and workshops

Cost Breakdown (TDD PAYG)

All following calculations are based on the Pay-As-You-Go for SAP BTP for cloud test, demo, and development for SAP BTP ABAP Environment. Please also refer to SAP BTP Pricing Options for more details and an online cost estimator. 

Pricing basis:

Runtime: 0.48 € / hour per 1 ACU (16 GB)For this example, we use 0.5 ACU → 0.24 € / hourPersistence: 0.10 € / hour per block (16 GB)Minimum persistence: 2 blocks → 0.20 € / hour

For the latest pricing details, refer to the SAP BTP Discovery Center.

Monthly Costs per System (0.5 ACU, 2 HCU)

For the latest pricing details, refer to the SAP BTP Discovery Center.

What This Looks Like in Practice

A simple Dev and Demo setup results in:

This is your starting point without any optimization.

Reducing Costs with System Hibernation

For non-productive systems, System Hibernation provides an effective way to reduce costs when using a consumption-based commercial model. See this blog post for more information.

When a system is stopped:

Runtime costs (ACU) → 0%Persistence costs (HCU) → 12.5%

Example Usage Pattern

Active: 12 hours per day on 20 working daysStopped: nights and weekends

Resulting Monthly Cost per System (0.5 ACU, 2 HCU)

Development & Demo Landscape

This shows how significantly costs can be reduced when systems are only used during working hours.

Going Live Option 1: Adding a Production System (Multitenant SaaS)

If you operate your solution as a SaaS offering, you typically add a production system:

Runtime → 1 ACUPersistence → 4 HCU (recommended)

Production systems are typically sized more conservatively than development systems to ensure performance and availability.

Pricing (PE Build)

Persistence requires 4 units:

4 × 111.94 € = 447.76 €

Total production cost: ~1083 € / month

Full SaaS Landscape Example

Going Live Option 2:  Add-On Product Scenario

If you deliver your solution as an Add-On Product:

You only need development and test systemsThe customer operates the production system

Result:

No production infrastructure cost on the partner sideLower operational responsibilityDeveloper extensibility for customerFlexible delivery model, especially for enterprise customers

Free TDD Capacity for SAP Partners

SAP currently offers free test, demo, and development (TDD) capacity as part of SAP Build runtime.

This includes:

cloud test, demo, and development for SAP Build runtime
(Fair use limit: 2,250 capacity units per month)

More information:

https://partneredge.sap.com/en/partnership/licenses/wp_payg_btp.html
https://partneredge.sap.com/en/products/sap-bld/about/sap_build_tdd.html

To get started:

Order “Pay-As-You-Go for SAP BTP for cloud test, demo, and development” (Material 8009282)Activate services in the SAP BTP cockpit

What This Means in Practice

For SAP BTP ABAP Environment:

1 capacity unit ≈ 1 € consumption valueFair use limit: 2,250 capacity units per month

SAP Build runtime free capacity covers runtime (ACU), but does not cover persistence (HCU), which must still be paid.

Comparison

Dev + Demo~640 €SAP Build free quota (runtime coverage)up to ~2,250 € consumption value (runtime only)Remaining persistence cost ~290 €

In many cases, the free quota can cover the runtime of development and demo systems, while persistence costs remain.

What Happens Beyond the Free Limit

If the fair use limit is exceeded:

Consumption continues seamlesslyBilling automatically switches to PAYG pricing

Summary: What It Actually Takes to Get Started

Recommended Approach for New Partners

Start with 0.5 ACU systems for development and demosEnable System Hibernation to reduce costsUse the free TDD quota during the initial phaseChoose the delivery model based on your business modelAdd a production system only when you are ready to go live 

​ When partners evaluate SAP BTP ABAP Environment, one of the first questions is simple: What does it actually cost to get started?With the introduction of 0.5 ABAP Compute Units (ACU), the answer has become much more attractive.Instead of starting at 1 ACU, partners can now begin with 0.5 ACU (8 GB runtime memory), making development, test and demo landscapes significantly more cost-efficient.At the same time, SAP BTP ABAP Environment supports two delivery options:Multitenant SaaS solution – operated by the partnerAdd-On Product – installed and operated by the customerBoth options can be combined depending on your business model. Commercial Model for PartnersTo build and commercialize solutions on SAP BTP ABAP Environment, partners operate within the SAP PartnerEdge – Build (PE Build) commercial model.This model provides the foundation for:Developing and running solutionsDelivering them as multitenant SaaS or Add-On ProductsPublishing offerings via the SAP Store A Typical Starting PointA realistic setup for partners usually includes a small development landscape.Development & Demo (TDD PAYG)Development system → 0.5 ACUTest/Demo system → 0.5 ACUPersistence → 2 HCU per systemThis setup is typically used for:DevelopmentTestingCustomer demos and workshops Cost Breakdown (TDD PAYG)All following calculations are based on the Pay-As-You-Go for SAP BTP for cloud test, demo, and development for SAP BTP ABAP Environment. Please also refer to SAP BTP Pricing Options for more details and an online cost estimator. Pricing basis:Runtime: 0.48 € / hour per 1 ACU (16 GB)For this example, we use 0.5 ACU → 0.24 € / hourPersistence: 0.10 € / hour per block (16 GB)Minimum persistence: 2 blocks → 0.20 € / hourFor the latest pricing details, refer to the SAP BTP Discovery Center.Monthly Costs per System (0.5 ACU, 2 HCU)Component Calculation Monthly Costs Runtime0.24 € × 730 h~175 €Persistence0.20 € × 730 h~145 €Total per system ~320 €For the latest pricing details, refer to the SAP BTP Discovery Center.What This Looks Like in PracticeA simple Dev and Demo setup results in:System Monthly Cost Development (0.5 ACU + 2 HCU)~320 €Test / Demo (0.5 ACU + 2 HCU)~320 €Total~640 € / monthThis is your starting point without any optimization.Reducing Costs with System HibernationFor non-productive systems, System Hibernation provides an effective way to reduce costs when using a consumption-based commercial model. See this blog post for more information.When a system is stopped:Runtime costs (ACU) → 0%Persistence costs (HCU) → 12.5%Example Usage PatternActive: 12 hours per day on 20 working daysStopped: nights and weekendsResulting Monthly Cost per System (0.5 ACU, 2 HCU)Active usage (runtime + persistence)~106 €Hibernation (reduced persistence)~11 €Total per system~116 € / monthDevelopment & Demo LandscapeSystem monthly costs Development~116 €Test / Demo~116 €Total~233 € / monthThis shows how significantly costs can be reduced when systems are only used during working hours. Going Live Option 1: Adding a Production System (Multitenant SaaS)If you operate your solution as a SaaS offering, you typically add a production system:Runtime → 1 ACUPersistence → 4 HCU (recommended)Production systems are typically sized more conservatively than development systems to ensure performance and availability.Pricing (PE Build)Material description price (€ / month) 8006181SAP BTP ABAP environment runtime (16 GB)635.46 €8006182SAP BTP ABAP environment persistence (16 GB)111.94 €Persistence requires 4 units:4 × 111.94 € = 447.76 €Total production cost: ~1083 € / monthFull SaaS Landscape ExampleDevelopment~320 €Test / Demo~320 €Production~1083 €Total~1,723 € / month  Going Live Option 2:  Add-On Product ScenarioIf you deliver your solution as an Add-On Product:You only need development and test systemsThe customer operates the production systemResult:No production infrastructure cost on the partner sideLower operational responsibilityDeveloper extensibility for customerFlexible delivery model, especially for enterprise customers Free TDD Capacity for SAP PartnersSAP currently offers free test, demo, and development (TDD) capacity as part of SAP Build runtime.This includes:cloud test, demo, and development for SAP Build runtime(Fair use limit: 2,250 capacity units per month)More information:https://partneredge.sap.com/en/partnership/licenses/wp_payg_btp.htmlhttps://partneredge.sap.com/en/products/sap-bld/about/sap_build_tdd.htmlTo get started:Order “Pay-As-You-Go for SAP BTP for cloud test, demo, and development” (Material 8009282)Activate services in the SAP BTP cockpitWhat This Means in PracticeFor SAP BTP ABAP Environment:1 capacity unit ≈ 1 € consumption valueFair use limit: 2,250 capacity units per monthSAP Build runtime free capacity covers runtime (ACU), but does not cover persistence (HCU), which must still be paid.ComparisonScenario Monthly CostDev + Demo~640 €SAP Build free quota (runtime coverage)up to ~2,250 € consumption value (runtime only)Remaining persistence cost ~290 €In many cases, the free quota can cover the runtime of development and demo systems, while persistence costs remain.What Happens Beyond the Free LimitIf the fair use limit is exceeded:Consumption continues seamlesslyBilling automatically switches to PAYG pricing Summary: What It Actually Takes to Get StartedEstimated monthly cost per scenario – choose one these options: Dev + Demo (no hibernation)0.5 ACU, 2 HCU~640 €Dev + Demo (with hibernation)0.5 ACU, 2 HCU, working hours only~233 €Full SaaS landscape (no hibernation)Dev + Demo + Production (1 ACU + 4 HCU)~1,720 €Full SaaS landscape (with hibernation)Dev + Demo + Production (1 ACU + 4 HCU)~1,310 €Add-On model (partner side only)Dev + Demo with hibernation~233 €With free TDD quota of SAP Build Runtime covered, persistence remains~290 € (Dev + Demo) Recommended Approach for New PartnersStart with 0.5 ACU systems for development and demosEnable System Hibernation to reduce costsUse the free TDD quota during the initial phaseChoose the delivery model based on your business modelAdd a production system only when you are ready to go live   Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog