A buyer side selection framework for CIOs, CFOs, general counsel, procurement leaders, and software asset management leads weighing on premise, Private Cloud Edition inside RISE, Public Cloud Edition inside GROW, and hyperscaler bring your own license against the 2027 ECC maintenance cliff and a ten year cost horizon.
A buyer side selection framework for CIOs, CFOs, general counsel, procurement leaders, and software asset management leads weighing on premise, Private Cloud Edition inside RISE, Public Cloud Edition inside GROW, and hyperscaler bring your own license against the 2027 ECC maintenance cliff. Drawn from 500+ enterprise client engagements, industry recognition, and $2B+ under advisory.
S/4HANA carries four active deployment vehicles in 2026. On premise. Private Cloud Edition inside RISE with SAP. Public Cloud Edition inside GROW with SAP. Hyperscaler bring your own license on AWS, Azure, or Google Cloud.
Each model carries distinct commercial mechanics, distinct customization scope, distinct exit complexity, and distinct ten year total cost positions. SAP account teams default to Private Cloud Edition as the recommended path. The recommended path is not always the optimal path for the customer.
The buyer side discipline frames the decision against five drivers. Customization scope. Operational control. Integration footprint. Total cost across a ten year horizon. Exit complexity. The combined score across the five drivers shapes the deployment model selection.
The deployment model decision is a commercial decision wrapped in technical language. Most procurement teams accept the SAP account team framing. The framing favors Private Cloud Edition because Private Cloud Edition delivers the highest revenue per customer to SAP across the ten year horizon.
The most important move is to insist on a written four model comparison from the SAP account team before any deployment commitment. The comparison forms the negotiation anchor across the deployment selection cycle.
Read the related RISE negotiation guide, the S/4HANA migration negotiation playbook, the GROW with SAP negotiation guide, the ECC to S/4HANA migration framework, the RISE TCO calculator, the SAP advisory practice, and the SAP knowledge hub.
SAP S/4HANA reached general availability in 2015 as the successor to the ECC business suite. The product runs on the SAP HANA in memory database. The architecture introduced the simplified Universal Journal, the Material Number extension, and a redesigned core data services model.
SAP committed in 2020 to end mainstream maintenance on the ECC business suite at the close of 2027. Extended maintenance runs to the end of 2030 at premium pricing. Customers on the ECC platform must move to S/4HANA, an alternative ERP, or a third party support arrangement before the maintenance cliff closes.
SAP reports more than thirty thousand S/4HANA customers as of mid 2026. The installed base is split across the four deployment vehicles. The Private Cloud Edition inside RISE carries the largest share by customer count. The on premise edition retains the largest share by transactional volume.
RISE with SAP launched in 2021 as the strategic subscription bundle. GROW with SAP launched in 2023 as the mid market multi tenant variant. The hyperscaler BYOL model expanded across AWS, Azure, and Google Cloud through documented certification programs.
The 2027 maintenance cliff drives the largest enterprise software migration program in the SAP customer base since the R/3 to ECC transition. SAP estimates that roughly twenty thousand enterprise customers must complete conversion or extended maintenance contracting by the cliff date.
The cliff creates documented SAP commercial leverage. Customers facing the cliff carry urgency that the SAP account team can convert into deployment model commitments. The buyer side discipline reframes the urgency by opening the deployment discussion early.
| Deployment vehicle | Launch year | Customer count band | Customization scope |
|---|---|---|---|
| S/4HANA on premise | 2015 | Approximately 12,000 | Full ABAP code retention |
| Private Cloud Edition (RISE) | 2021 | Approximately 11,000 | High customization with managed scope |
| Public Cloud Edition (GROW) | 2023 | Approximately 5,500 | Standardized scope, key user extensions |
| Hyperscaler BYOL | 2017 | Approximately 3,800 | Full ABAP code retention on hyperscaler |
| S/4HANA Cloud public edition (legacy) | 2017 | Approximately 2,200 (sunset) | Folded into Public Cloud Edition |
Enterprise S/4HANA programs sit between USD 20m and USD 400m across the conversion and operate horizon. The ten year cost delta between deployment models lands at ten to twenty five percent of the program. The deployment model decision carries direct CFO impact at the financial reporting level.
The buyer side stakes also cover operational continuity. The selected model shapes the customer ability to retain custom code, integrate legacy systems, and run sector specific workloads. Operational continuity ranks alongside total cost in the deployment decision.
The SAP commercial agenda favors subscription revenue over license revenue. Subscription delivers higher net present value per customer, higher recurring revenue, and lower churn risk. The SAP account team incentive plan rewards subscription conversion.
The buyer side discipline separates the SAP commercial agenda from the customer commercial optimum. The two are not always aligned. Document the gap explicitly across the deployment model evaluation.
The four deployment vehicles carry distinct technical mechanics and distinct commercial boundaries. The decision starts with mechanics. The negotiation starts with commercial boundaries.
The on premise edition runs S/4HANA inside the customer data center. The customer owns the perpetual licenses. The customer manages the infrastructure, the database administration, the basis operations, and the upgrade cycle. Maintenance runs at twenty two percent of net license value annually.
On premise retains the full ABAP code base. Brownfield conversion from ECC preserves the custom code estate at conversion. Integration patterns run through the standard SAP middleware stack across the customer infrastructure.
The on premise model carries the highest customer operational responsibility and the lowest SAP commercial dependency. The buyer side position remains strong across the contract term because SAP commercial leverage is limited to the maintenance renewal.
The Private Cloud Edition delivers S/4HANA as a managed subscription inside the RISE with SAP commercial wrapper. SAP operates the dedicated single tenant infrastructure on a customer selected hyperscaler. SAP manages the database administration, the basis operations, and the upgrade cycle.
The Private Cloud Edition preserves the brownfield conversion path. Custom ABAP code converts during the migration. The integration patterns extend through the SAP Business Technology Platform and the standard middleware stack.
Private Cloud carries SAP commercial dependency across infrastructure, operations, and the upgrade cycle. The customer signs a three to five year subscription term. Annual price uplift mechanics run inside the executed contract.
The Public Cloud Edition delivers a multi tenant standardized S/4HANA stack inside the GROW with SAP commercial wrapper. SAP operates the shared infrastructure. The release cycle runs on a fixed quarterly cadence across all Public Cloud customers.
The Public Cloud Edition forces greenfield reimplementation. Custom ABAP code is not supported. Configuration runs through standardized scope items, key user extensions, and the SAP Business Technology Platform extension framework.
Public Cloud Edition carries the lowest customer operational responsibility and the highest standardization. The model fits net new ERP deployments, divisional carve outs, and mid market scale customers without significant custom code estate.
The hyperscaler BYOL model deploys the on premise S/4HANA binary inside AWS, Azure, or Google Cloud. The customer retains the perpetual license. The customer manages the basis operations, the database administration, and the upgrade cycle on the hyperscaler infrastructure.
The BYOL model preserves license ownership while shifting infrastructure cost from capital expenditure to operating expenditure. The integration patterns and the custom code estate map identically to the on premise model. Hyperscaler commercial discounts run on top of the standard SAP license commercial framework.
| Attribute | On premise | Private Cloud | Public Cloud | Hyperscaler BYOL |
|---|---|---|---|---|
| License model | Perpetual | Subscription | Subscription | Perpetual on cloud |
| Infrastructure operator | Customer | SAP | SAP | Customer |
| Upgrade cadence | Customer controlled | SAP managed, customer agreed | SAP fixed quarterly | Customer controlled |
| Custom ABAP support | Full | Full | Limited extensions | Full |
| Brownfield conversion path | Yes | Yes | No, greenfield only | Yes |
| Mainstream maintenance horizon | 2040 | Subscription term | Subscription term | 2040 |
| Typical contract length | Open ended | 3 to 5 years | 3 to 5 years | Open ended license, hyperscaler term |
The deployment model decision runs across five documented drivers. The five drivers carry weight against the customer operating context. The combined score shapes the model selection.
Customization scope measures the customer custom ABAP code estate and the extent of process variation from standard SAP scope. High customization customers carry significant brownfield value that the on premise model and the Private Cloud Edition preserve. Low customization customers can move directly to the Public Cloud Edition.
The buyer side test asks how many active Z programs and Z objects exist inside the productive client. Customers with more than five thousand active Z objects typically rule out the Public Cloud Edition. Customers with fewer than five hundred active Z objects can consider the Public Cloud Edition as a viable path.
Operational control measures the customer preference for direct control of the upgrade cycle, the basis operations, and the integration patterns. High control customers retain on premise or hyperscaler BYOL. Medium control customers select Private Cloud Edition. Low control customers select Public Cloud Edition.
The buyer side test asks who controls the production upgrade calendar. Customers with regulated calendar constraints, integration freeze windows, or industry specific calendar pressure typically retain the customer controlled models. Customers with mature managed service experience accept the Private Cloud Edition operator role.
Integration footprint measures the breadth of third party systems connected to the SAP estate. High integration customers carry connection patterns across middleware, point to point interfaces, and custom RFC calls. The integration patterns shape the deployment model viability.
The buyer side test catalogues every active integration pattern by class. Customers with more than fifty active integration patterns typically rule out the Public Cloud Edition because the standardized integration framework cannot host every pattern. The on premise model and the Private Cloud Edition preserve the integration estate.
Ten year total cost compares license, subscription, support, infrastructure, integration, and operational cost across the model alternatives. The comparison runs against a documented horizon to normalize the upfront license cost against the recurring subscription cost.
The buyer side test runs a structured TCO model with the four deployment vehicles modeled side by side. Use the SAP RISE TCO calculator as the starting point. Incorporate hyperscaler infrastructure cost, custom integration retention, and conversion services in the model.
Exit complexity measures the cost and effort of leaving the deployment model at term end. On premise carries the lowest exit complexity. Public Cloud Edition carries the highest exit complexity because data export and process rebuild require greenfield reverse engineering.
The buyer side test maps the exit cost across the four vehicles. The exit cost forms the strategic anchor for the negotiation discussion. Without explicit exit cost mapping the customer faces unbudgeted complexity at term end across the subscription models.
Score each deployment vehicle across the five drivers on a one to ten scale. Apply weights against the customer operating context. The weighted total selects the optimal deployment vehicle for the specific customer.
The scoring exercise also documents the rationale for the selection. The documentation supports the financial reporting position, the audit committee briefing, and the executive committee approval. Without documented rationale the deployment decision carries governance exposure.
Each deployment vehicle carries documented commercial mechanics. The commercial mechanics shape the buyer side negotiation across the deployment selection cycle.
On premise carries the traditional SAP license commercial model. Perpetual licenses purchased against the standard price list. Annual maintenance at twenty two percent of net license value. Indexation clauses against the maintenance line. Named user metrics, engine metrics, and Digital Access volume blocks.
The on premise commercial mechanics expose the customer to the SAP license audit framework. The named user reclassification, the indirect access exposure, and the engine activation findings apply across the on premise estate. Read the audit survival guide for the structured response.
Private Cloud Edition runs on the Full User Equivalent metric. The Full User Equivalent aggregates the contracted user population across named user categories into a single subscription metric. The infrastructure consumption runs against the SAP managed hyperscaler footprint.
The annual subscription includes the S/4HANA software, the SAP Business Technology Platform credits, the managed infrastructure, and the basis operations. Annual price uplift mechanics run at three to five percent or a documented index, whichever is higher.
The Private Cloud Edition commercial mechanics carry documented traps. The Full User Equivalent calculation is not transparent at order form signature. The BTP credit allocation runs short for most enterprise customers. The infrastructure overage carries premium pricing.
Public Cloud Edition runs on a per user per month subscription with documented edition tiers. Essential, Premium, and Premium Plus editions carry distinct functional scope and distinct price points. The infrastructure runs inside the SAP managed multi tenant footprint.
The Public Cloud commercial mechanics carry the lowest negotiation flexibility. SAP defends the published price list more rigidly inside the Public Cloud Edition because the multi tenant operating model constrains custom commercial structures.
Hyperscaler BYOL combines the standard SAP license commercial model with the hyperscaler commercial framework. The SAP license cost runs against the standard price list with the standard maintenance line. The hyperscaler infrastructure cost runs against the AWS, Azure, or Google Cloud commercial agreement.
The hyperscaler commercial layer carries committed use discounts, reserved capacity discounts, and Enterprise Discount Program incentives. The hyperscaler commercial framework operates independently of the SAP license commercial framework.
| Cost layer | On premise | Private Cloud | Public Cloud | Hyperscaler BYOL |
|---|---|---|---|---|
| Software license | Perpetual upfront | Included in subscription | Included in subscription | Perpetual upfront |
| Annual support | 22% of net license | Included in subscription | Included in subscription | 22% of net license |
| Infrastructure | Customer capex | Included in subscription | Included in subscription | Hyperscaler opex |
| Basis operations | Customer or partner | SAP managed | SAP managed | Customer or partner |
| Upgrade cycle | Customer controlled | SAP managed, customer agreed | SAP fixed | Customer controlled |
| Integration platform | BTP at list | Included credits plus overage | Included credits plus overage | BTP at list |
Lock in measures the cost and effort of leaving the deployment vehicle at term end. The buyer side discipline maps lock in across infrastructure, operations, data, custom code, and integration.
On premise carries the lowest infrastructure lock in. The customer owns the hardware and the data center contract. Private Cloud Edition routes infrastructure through SAP. Public Cloud Edition routes infrastructure through SAP at the highest concentration. Hyperscaler BYOL sits inside the hyperscaler infrastructure commercial framework.
The hyperscaler selection inside Private Cloud Edition runs through SAP. The customer does not contract directly with AWS, Azure, or Google Cloud for the underlying infrastructure. The arrangement compresses the customer hyperscaler commercial leverage.
Operations lock in measures the dependency on a single operator for basis, database, and upgrade activities. On premise and hyperscaler BYOL preserve customer or partner operations. Private Cloud Edition routes operations through SAP. Public Cloud Edition routes operations through SAP with the highest concentration.
The operations transition cost at term end runs against documented benchmark data. Moving operations back from SAP to a partner typically carries six to twelve months of program effort and USD 1m to USD 5m of transition cost on enterprise scale estates.
Data lock in measures the cost of exporting the productive client data at term end. On premise carries the lowest data lock in. Private Cloud Edition data export runs against documented SAP procedures with SAP support. Public Cloud Edition data export carries the highest complexity because the standardized data model differs from the customer historical state.
The buyer side response is to negotiate explicit data export language at contract signature. The language covers the export format, the export support scope, the export timeline, and the export cost across the contract term and beyond.
Custom code lock in measures the future portability of the customer ABAP code estate. On premise, Private Cloud Edition, and hyperscaler BYOL preserve the custom code estate. Public Cloud Edition does not host the custom code estate at all. Moving from Public Cloud back to brownfield typically requires full code reconstruction.
The custom code estate carries documented commercial value. Enterprise custom code estates frequently represent USD 10m to USD 100m of historical investment. The lock in mapping must reflect the historical investment exposure.
Integration lock in measures the cost of rerouting third party system connections at term end. On premise and hyperscaler BYOL preserve the integration estate. Private Cloud Edition retains the integration patterns inside the SAP middleware stack. Public Cloud Edition forces integration redesign at the standardized framework.
The buyer side response is structured integration cataloguing ahead of any deployment selection. Document every active integration pattern. Map every pattern to the four deployment vehicles. Identify the integration patterns that require redesign per vehicle.
Private Cloud Edition carries documented exit complexity that most procurement teams underestimate at contract signature. The exit cost across infrastructure transition, operations re insourcing, data export, and integration rebuild routinely lands at USD 5m to USD 20m on enterprise scale estates.
The buyer side response is to negotiate exit language at contract signature. The language covers data export at no charge, infrastructure transition support, operations handover scope, and integration platform credit continuation. Without explicit exit language the customer faces unpriced complexity at term end.
Six recurring trap patterns shape the deployment model decision across documented enterprise engagements. Each trap has a documented corrective move.
The written comparison documents the SAP position across on premise, Private Cloud Edition, Public Cloud Edition, and hyperscaler BYOL. The comparison covers software cost, infrastructure cost, support cost, operational cost, and exit cost across a ten year horizon.
The written comparison forms the negotiation anchor across the deployment selection cycle. Track the comparison receipt against the deployment decision calendar. The timing window is one hundred and twenty days ahead of the deployment commitment date.
Catalogue every active integration pattern by class, by transport, and by document creation impact. Document every named user impersonation pattern. Map every pattern to the four deployment vehicles. Identify the patterns that require redesign per vehicle.
The catalogue documents the integration retention cost across deployment models. Track the count of mapped patterns against the count of active integration platforms. The timing window is sixty days ahead of the deployment evaluation. Read the indirect access guide.
Reject any deployment commitment without documented exit language. Negotiate explicit data export at no charge, infrastructure transition support, operations handover scope, and integration platform credit continuation inside the executed order form.
The exit language protects against unbudgeted complexity at term end. Track the exit language presence inside every executed subscription order form. The timing window is thirty days ahead of any deployment commitment signature.
Run the documented TCO model with the four deployment vehicles modeled side by side. Use the SAP RISE TCO calculator as the starting point. Apply five percent annual uplift on subscription models. Apply three percent annual uplift on on premise maintenance.
The TCO model documents the financial case across the deployment decision. Track the modeled ten year cost against the budget envelope. The timing window opens twelve months ahead of the deployment commitment and remains open through any annual reforecast.
Reject any deployment commitment that exposes the customer to uncapped price uplift across the subscription term. Counter with explicit price protection language inside the executed order form. Cap the annual uplift at three percent or a documented index, whichever is lower.
The price protection language carries direct CFO impact across the contract term. Track the price protection presence inside every executed subscription document. The timing window is sixty days ahead of any deployment commitment signature.
Three structural shifts shape the deployment model agenda across 2026 to 2028. Each shift carries documented buyer side response.
The maintenance cliff drives the largest enterprise software commitment volume across the SAP customer base. SAP account teams compress the deployment evaluation calendar against the cliff. The buyer side response is the early start. Open the deployment evaluation eighteen to twenty four months ahead of cliff impact.
The early start reclaims the negotiation calendar and separates the deployment decision from any urgency commitment. The early start also opens the buyer side comparison across the four deployment vehicles without SAP commercial compression.
The hyperscaler commercial frameworks across AWS, Azure, and Google Cloud compete directly with the Private Cloud Edition. The hyperscaler BYOL model preserves SAP license ownership while delivering hyperscaler infrastructure economics. The combined commercial framework runs against the Private Cloud Edition subscription on the ten year horizon.
The buyer side response is structured hyperscaler negotiation alongside the SAP deployment evaluation. Read the AWS vendor management playbook, the Microsoft Azure ELA negotiation guide, and the Google Cloud PPA negotiation guide.
Public Cloud Edition through GROW with SAP matures across the mid market segment. The standardized scope, the fixed release cadence, and the limited customization scope fit the mid market operating model. The Public Cloud Edition customer count grows at the fastest pace across the four vehicles.
The buyer side response for enterprise customers is to document the Public Cloud Edition viability against the customer custom code estate. Customers with limited custom code can evaluate Public Cloud Edition as a viable path. Customers with significant custom code typically rule out Public Cloud Edition early.
SAP offers four S/4HANA deployment vehicles. The on premise edition retains license ownership inside customer data centers. The Private Cloud Edition delivers S/4HANA as a managed subscription inside RISE with SAP. The Public Cloud Edition delivers a multi tenant variant inside GROW. Hyperscaler BYOL deploys S/4HANA inside AWS, Azure, or Google Cloud.
Private Cloud Edition delivers a dedicated single tenant S/4HANA stack with high customization scope inside the RISE wrapper. Public Cloud Edition delivers a multi tenant standardized S/4HANA stack with limited customization, fixed release cycle, and a public catalog of best practice scope items. Private Cloud preserves brownfield conversion. Public Cloud forces greenfield reimplementation.
Yes. SAP continues to sell on premise S/4HANA licenses under the standard price list across 2026 and beyond. Mainstream maintenance on the on premise S/4HANA installation runs through 2040 under the announced commitments. The on premise model remains a documented purchase path for customers who prefer license ownership over subscription.
The total cost depends on the contract horizon, the existing install base, the customization scope, and the integration footprint. Across a ten year horizon the on premise model frequently lands ten to twenty five percent below RISE Private Cloud. Private Cloud delivers operational simplification. Public Cloud lands below both on a true SaaS scope.
SAP ECC mainstream maintenance ended at the close of 2027 under the published roadmap. Extended maintenance runs to the end of 2030 at a premium charge. Customers must move to S/4HANA, alternative ERP, or third party support before the maintenance window closes.
RISE introduces three documented lock points. The infrastructure and operations layer sits inside the SAP commercial wrapper. The hyperscaler selection runs through SAP rather than the customer. The exit path back to on premise carries documented complexity around data export, custom code retention, and integration rebuild. Negotiate exit language at contract signature.
Start with a documented total cost comparison across the four deployment vehicles. Include license, subscription, support, infrastructure, integration, and operational cost. Compare against a ten year horizon. Insist on a written model comparison from the SAP account team. Negotiate price protection, exit language, and conversion credits inside the executed order form.
The most common trap is conflating Private Cloud Edition with traditional on premise inside the same commercial framing. Private Cloud Edition is a subscription with documented infrastructure lock and standardized exit complexity. Treating it as a like for like on premise replacement leads to renewal surprises at the third anniversary and complicated exit at term end.
The S/4HANA deployment models guide sits inside the broader Redress Compliance SAP advisory practice. Engage on a single deployment evaluation, the coordinated SAP commercial cycle, or the always on advisory subscription.
SAP Services · SAP Knowledge Hub · Download the RISE Negotiation Guide · RISE TCO Calculator · SAP Audit Survival · Vendor Shield
The practice runs four engagement models against the S/4HANA deployment decision.
Read across the wider SAP library:
The RISE with SAP Negotiation Guide covering the Full User Equivalent metric, the BTP credit allocation, the infrastructure overage exposure, and the exit language alongside the deployment selection framework. Stages the SAP subscription commercial position across the contracted term.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for CIOs, CFOs, general counsel, procurement leaders, and software asset management leads.
“The SAP account team had framed the deployment decision as a single path discussion. The Private Cloud Edition wrapped the S/4HANA conversion, the infrastructure, the operations, and the BTP credits into a single five year subscription at a premium price point.”
“Redress ran the buyer side four model comparison. The hyperscaler BYOL alternative preserved license ownership while delivering thirty percent infrastructure savings against the SAP managed footprint. The ten year cost gap landed at USD 18m in favor of the BYOL path.”
“The executed deployment commitment selected the hyperscaler BYOL path with documented exit language and price protection. Net commercial improvement against the opening SAP position landed at USD 18m across the ten year horizon. Forty four percent improvement against the initial commercial proposal.”
We work for the buyer. Always. There is no other side of our table.
SAP deployment model intelligence, RISE commercial mechanics, GROW edition pricing, hyperscaler BYOL frameworks, and the broader SAP commercial signals from the Redress Compliance SAP advisory practice.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
