RISE with SAP Private vs Public Cloud. Which edition fits your enterprise.

Private Edition suits companies with heavy custom code and deep industry processes. Public Edition costs less per user and suits standard processes, but it upgrades twice a year and accepts no modifications, so the real saving depends on your custom code.

RISE with SAP comes in two editions. Private Edition gives you your own S/4HANA tenant, run by SAP on a hyperscaler. Public Edition puts you on a multi tenant cloud with a standard data model that every customer shares.

The edition decides how much of your custom code survives, how often you retest and what you pay for five years. For wider context, see our SAP knowledge hub, the SAP advisory practice, the RISE negotiation guide and the Vendor Shield subscription.

What is the difference between RISE with SAP Private Edition and Public Edition?

Private Edition is single tenant: your S/4HANA system, custom code, integrations and add ons run in an SAP managed tenant on AWS, Microsoft Azure or Google Cloud. Public Edition is multi tenant: SAP runs one codebase for all customers, and you adopt its standard processes and data model.

Private Edition accepts customization and allows a conversion of your existing ECC system. Public Edition accepts only a new implementation, so ECC history arrives as migrated data. SAP now also sells Private Edition inside a commercial package called SAP Cloud ERP Private, so expect that name on newer quotes.

Nine factors compared

How to weigh the factors

Score all nine factors against your own SAP system. If you run a custom heavy ECC system, give customization headroom and industry depth the most weight. If you are starting fresh with standard processes, give implementation time and cost the most weight.

How much cheaper is RISE Public Edition than Private Edition?

On subscription alone, Public Edition costs roughly 28 to 29 percent less than Private Edition at every size we model. The fee covers the platform, SAP's managed services and the standard application. Both editions price per Full Use Equivalent (FUE): one Advanced Use user, five Core Use users or thirty Self Service users each count as 1 FUE.

Five year cost at four company sizes

The per user columns divide each five year total by five and by the user count. Per user cost falls with volume in both editions, while the percentage gap stays close to constant.

Which costs sit outside the subscription?

• BTP for Public Edition. Any extension that cannot be built in ABAP Cloud inside the tenant runs on SAP BTP and consumes credits you pay for.
• Infrastructure beyond the base tiers for Private Edition. Extra production and non production tiers (sold in sizes XS to 4XL), memory extensions, disaster recovery and connection packages are billed on top of the SAP fee.
• Included BTP credits. Under SAP's 2024 Private Edition packaging, the bundle includes BTP credits equal to 1 percent of net annual contract value, with a floor of €10,000 and a cap of €20,000 a year.
• Implementation. For both editions, expect 1 to 2 times the year one subscription.

Worked example: a 2,000 user company over five years

Say you run 2,000 users, so year one subscription is about $3.6M on Private Edition and $2.6M on Public Edition. Every other figure below is a hypothetical assumption; replace them with your own quotes.

The list gap of $5.0M, about 28 percent, becomes $4.6M, about 18 percent. Now raise the custom code rebuild to 1,000 objects. The Public Edition rebuild line grows to $6.0M, the total reaches $25.0M, and the gap falls to $1.0M, under 4 percent of the Private Edition total.

How much custom code can each edition carry?

Private Edition carries Z tables, custom transactions, classic ABAP and modifications, much as ECC does. Public Edition allows no modifications. Custom logic runs through key user tools, ABAP Cloud code that calls only released APIs, or side by side apps on SAP BTP.

ABAP Cloud can hold custom tables, but it cannot take ECC code as it stands. Code that touches SAP tables directly or calls unreleased function modules must be redesigned.

Five customization patterns and where each fits

• Custom Z tables in ECC. They move to Private Edition with the conversion. On Public Edition they must be rebuilt in ABAP Cloud or on BTP.
• Custom transactions on standard tables. They run on Private Edition. On Public Edition they need a rebuild on released APIs or a side by side app on BTP.
• Custom screens and forms. Both editions support them through Fiori, with tighter limits on Public Edition.
• Industry specific configuration. Private Edition carries the full IS suite. Public Edition carries a subset.
• Third party add ons. Private Edition supports more certified add ons. Public Edition depends on SAP certified partners on BTP.

What does a clean core program involve?

A clean core program lifts custom code out of the ERP core and rebuilds it on released interfaces, usually on BTP. On a large ECC system it runs three to five years. At the end, your core is ready for Public Edition, because the custom logic no longer depends on SAP internals.

Much of the effort goes into deciding what to keep, because each unused object you retire drops out of the rebuild estimate.

How often does each edition upgrade, and what does that cost you?

Public Edition gets two major releases a year, in February and August, applied on SAP's schedule. You cannot skip one. Private Edition gets a new base release every two years, and each release has seven years of mainstream maintenance.

Most Private Edition customers upgrade every three to five years, on a window they choose. SAP performs the technical upgrade, but planning, testing and sign off stay with you in both editions.

Three upgrade trade offs

1. Faster innovation on Public Edition. Every six months brings new features. Smaller features between releases can be switched on when you are ready.
2. Higher regression test load on Public Edition. Every release needs validation, especially of extended processes. SAP's Test Automation Tool helps, but someone must maintain the scripts.
3. Longer regression cycle on Private Edition. Each upgrade is a project lasting several quarters, but it comes only once every few years.

What contract terms should you negotiate for either edition?

Both editions sit on SAP's cloud paper, and the data export clause and BTP commitment matter most. Ask for these terms on either edition.

Contract terms to ask for

• Data export. The right to a full export of your data at any contract event, in a usable format.
• BTP commitment. Negotiate the BTP credit pool inside the RISE subscription, not on separate paper, so it shares the same discount and term.
• Annual escalator. Cap it at three to five percent on both editions, including at renewal.
• Termination for convenience. A defined notice period and a refund clause for any prepaid years.
• Indirect access. Your Digital Access terms written into the order form, with the document volumes you expect.
• Edition change right. If you start on Private Edition, a written option to move to Public Edition with credit for the unused term.
• FUE reduction at renewal. The right to reduce the FUE count at renewal if your business shrinks or divests.

Where SAP's paper stays silent unless you ask

SAP's cloud order forms usually arrive without a data export clause. Insist on it in the order form itself, and do the same for the BTP commitment and termination for convenience. Side letters get lost when account teams change.

How does Digital Access differ between the editions?

Digital Access is counted per document in both editions, and the exposure is broadly the same. SAP measures inside the Public Edition tenant it runs, while Private Edition follows the on premises method. Because SAP runs the count on Public Edition, ask to see the document report you will receive before you sign.

What will SAP's account team say, and how should you answer?

SAP's reps are paid on cloud bookings (see what SAP sales is paid on), and their arguments follow from that. These lines come up most often.

• "Public Edition is where the innovation goes." Ask for a written list of features in your scope that are Public Edition only. Private Edition still gets feature packs every six months.
• "You need a clean core anyway, so go Public now." You can pursue a clean core on Private Edition at your own pace. Ask SAP to price the rebuild of your custom code first.
• "You can move to Public Edition later." There is no conversion path into Public Edition, only a new implementation. Ask for the edition change right and the term credit in writing.
• "BTP credits are included." Ask for the exact entitlement and compare it with your extension plan. The entitlement stops at €20,000 a year, which is small next to most extension plans.
• "This price only holds until quarter end." The deadline tracks the rep's quota. Our note on SAP fiscal quarter timing explains when SAP has the most room on price and how to plan your signing date around it.

What do we see when companies choose between the editions?

Two patterns come up repeatedly in the RISE edition reviews we run, each led by a former SAP commercial executive who now advises the customer. The first starts with cost: a team picks Public Edition for the lower list price, then finds it has not staffed for regression testing twice a year.

The second is industry depth. Among large companies, the gap in Industry Solutions coverage is the most common reason the decision lands on Private Edition. Once a company maps the IS processes it runs against Public Edition scope items, one or two missing processes are often enough to decide it.

Why we disagree with choosing Public Edition to force a clean core

A common piece of advice says to pick Public Edition because it forces a clean core. We think that gets the order wrong. On a custom heavy ECC system, it makes the whole clean core program a condition for go live, and the business waits while code is rebuilt.

The better course is to go live on Private Edition, run the clean core program alongside, and hold a contractual right to switch editions once the core is ready.

Public Edition saves money on the price list. Private Edition saves your custom code from a four year rewrite. Your own system should decide which saving matters more.

Which RISE edition fits your company?

Match the edition to the system you run today. Four profiles cover most cases.

How the answer shifts with company size

A 500 user company with standard finance and sales processes can often go live on Public Edition in the 4 to 9 month window, and the release cycle is manageable with a small team. SAP also sells Public Edition to midsize firms through GROW with SAP; our RISE versus GROW comparison explains the difference.

A 10,000 user group across several countries usually has decades of custom code, local legal requirements and IS processes. Private Edition with a clean core program is the realistic start, even though the subscription gap in dollars is widest there.

How to check your own position

• SAP Readiness Check. Run it on your ECC production system for simplification items, add on compatibility and a custom code summary.
• ABAP Test Cockpit. Run the S/4HANA readiness checks and the ABAP Cloud readiness checks to see which objects would break.
• SCMON or usage procedure logging. Collect at least a year of usage so you can retire dead custom code before anyone prices a rebuild.
• Table TADIR. Count repository objects in the Z and Y namespaces for a first view of custom code volume.
• Public Edition scope items. Compare SAP's published scope items for your industry with the IS processes you run.
• Digital Access evaluation. Estimate the document volumes your interfaces create before you negotiate the clause.

How does Redress help with the RISE edition decision?

We score the edition choice inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program and the Software Spend Assessment. We take no money from SAP. Read how our benchmarking works, learn more about us, see our locations or contact the team.

What to do next

1. Count your custom code. Z tables, custom transactions and ABAP extensions, with usage data showing which are still used.
2. Map industry depth. Compare your IS suite usage with Public Edition coverage, process by process.
3. Size regression capacity. Work out the team that can absorb two upgrades a year, and what it costs.
4. Build the five year cost model. Include subscription, extra infrastructure, BTP and implementation for both editions.
5. Map Digital Access. List the interfaces that create documents and estimate volumes before the clause is drafted.
6. Plan the BTP commitment. Negotiate it inside the RISE subscription so it carries the same discount and term.
7. Lock the data export clause. Write it into the order form itself.
8. Get an independent review. Have someone without a stake in either edition score the choice before you sign.

Frequently asked questions