The three deployment options

SAP S/4HANA reaches customers in three shapes. The software family is the same, but who runs it, how far you can change it and how often it changes are very different. An architect who mixes these up promises the business things the chosen option cannot deliver, and a test lead who mixes them up plans the wrong amount of regression testing. This lesson sets out the three options in plain terms; the rest of the course compares them dimension by dimension.

Public cloud, private cloud, on-premise

SAP S/4HANA Cloud Public Edition is software as a service. SAP runs one code line for all customers, upgrades it on SAP's schedule and controls what can be changed. Customers configure, extend through released interfaces and test, but they do not own the system technically. SAP now markets it as SAP Cloud ERP; most offerings for net-new, standard-led companies are packaged around it.

SAP S/4HANA Cloud Private Edition is the same software as on-premise SAP S/4HANA, run for one customer in a dedicated landscape that SAP manages, usually on a hyperscaler. It is the usual target of RISE with SAP, the subscription bundle that combines the ERP, infrastructure, technical managed services and tools. SAP documents also use the name SAP Cloud ERP Private. Because it is the same software, a company can convert an existing SAP ERP system into it and keep its custom code.

SAP S/4HANA on-premise is the classic licensed product. The customer, or a hosting partner the customer hires, installs and runs it on infrastructure of the customer's choosing. Functionally it matches the private edition release for release; what differs is who does the technical work and how it is contracted.

Five dimensions that matter

When you compare options, compare the same things every time. This course uses five dimensions: scope and fit (does the standard cover the processes?), extensibility (what may be changed and how), cadence (how often the software changes underneath you), operations (who does what), and testing implications (how much regression testing the option demands and when). Cost and contract terms matter too, but they follow from these choices rather than drive the architecture.

Variants you will hear about

Contracts add names that sound like extra options. SAP's roles and responsibilities document covers the private edition together with a tailored option, which differs in the services included rather than in the software. For the largest SAP ERP customers who cannot finish their move before extended maintenance ends, SAP announced SAP ERP, private edition, transition option: a time-bound subscription that keeps SAP ERP running with business continuity services beyond 2030 while the customer completes its transformation. That is a bridge for SAP ERP, not a fourth way to run SAP S/4HANA. When you meet a new name, ask the same three questions: which software, run by whom, and changed how often.

Contoso's choice

Contoso Motor Co. runs SAP ECC 6.0 EHP 8 with years of custom code, including a custom table of core return agreements for fleet customers. Its program, led by Grace from the PMO, is a system conversion to SAP S/4HANA Cloud Private Edition under RISE with SAP, with systems CMD, CMQ and CMP. A conversion keeps history and custom code, which rules out the public edition: moving there would mean a new implementation and a redesign of everything that does not fit released interfaces. On-premise was possible technically, but Contoso did not want to keep running data centers and databases.