ERP for Beginners: Cloud vs On-Premise ERP: On-prem, Public Cloud, Private Cloud, Hybrid

Somewhere around month six of an ERP selection project, the conversation turns to a question that sounds technical but is actually strategic. Where is this thing going to live?

On your own servers? In the vendor's cloud? In a managed private instance? Some hybrid mix? The answer shapes the cost profile, the upgrade cadence, the customisation ceiling, and the relationship with the vendor for the next decade. Which is why it's worth understanding well before you're negotiating with account managers.

This is the fifth episode of our ERP for Beginners series, and we're going to pull apart each of the four real options — on-premise, public cloud, private cloud, hybrid — along with the three dimensions every choice trades against each other.

The three dimensions

Before the options, the axes. Every deployment choice is trading three things.

Control. How much of the system can you customise? How much of the infrastructure do you own? How much say do you have in when changes get pushed?

Innovation speed. How fast do new features arrive? Are you always on the latest version, or are you two major releases behind because upgrading is a project?

Cost shape. Is this capex (big upfront purchase, amortised over years) or opex (predictable monthly subscription)? Who's responsible for infrastructure, backups, security patching?

No option optimises all three. Pick high control, you lose innovation speed. Pick fast innovation, you lose control. Pick predictable opex, you accept less flexibility. This tension is the whole point of the deployment conversation.

Option one — on-premise

The classical install. You buy a perpetual licence, your IT team deploys the software on your own servers in your own data centre, and your IT team runs everything from there. Hardware, network, backups, security patches, upgrades — all yours.

On-premise is the oldest deployment model and the one with the most control. Every line of custom code is yours to write. Every configuration setting is yours to flip. Every customisation is allowed — because the vendor has no visibility into your instance and no opinion on what you should and shouldn't do.

The tradeoff is speed. When the vendor releases a new version, you decide when to upgrade — which in practice means "never, because upgrades are painful". Major on-premise ERP upgrades are eighteen to thirty-six month projects in their own right. Companies routinely run on versions that are five, eight, ten years behind current. They know they should upgrade. They just can't afford the disruption.

Cost is mostly capex. A big upfront licence purchase. Plus hardware, plus annual maintenance to keep the vendor obligated to help you. Plus implementation, which often doubles the licence cost. Plus internal IT headcount to run the thing.

Who fits? Mature enterprises with heavy customisation. Industries with strict data-residency requirements (pharma, defence, government). Customers who've already sunk years of customisation into the product and aren't going to re-do it all just to move to the cloud.

Option two — public cloud (SaaS)

The opposite end of the spectrum. The vendor runs the software as multi-tenant SaaS. Your data is logically separated from every other customer's, but the underlying infrastructure is shared. You don't install anything — you log in through a browser.

NetSuite was the first ERP built this way, in 1998. Workday followed in 2005 in the HR space. Over the last fifteen years, the Tier-1 incumbents have rebuilt their products for this model — SAP S/4HANA Cloud (public edition), Oracle Fusion Cloud ERP, Microsoft Dynamics 365 Business Central.

The tradeoffs here are the inverse of on-premise. Customisation is deliberately limited. You can configure (flip switches, set parameters, define extensions), but you can't modify the base product with custom code the way you could on-prem. That sounds restrictive, and it is — but it's also the whole point. Standard processes are the product. If you need the process to work differently, public cloud isn't for you.

Upgrades are continuous. Two to four major releases per year, pushed automatically, with limited ability to opt out. You're always on the latest version, which is genuinely good for getting new features but occasionally bad when a release changes behaviour you depended on.

Cost is subscription. Per user per month, paid annually. No big upfront licence. The infrastructure cost is the vendor's problem — hardware, patching, backups, uptime. The predictability is the main financial benefit.

Who fits? Startups. Greenfield deployments where there's no legacy system to migrate from. Fast-growing SMBs that need to move quickly. Subsidiaries of larger companies that want to stand up a regional instance in weeks rather than months.

Option three — private cloud

Between on-prem and public cloud sits a deliberate middle path. Private cloud (sometimes called single-tenant cloud, or vendor-managed cloud) is single-tenant — your instance is yours alone — but the vendor runs the infrastructure.

The big Tier-1 vendors have formal private-cloud programmes. SAP's is called RISE with SAP. Oracle has Oracle Cloud at Customer and similar arrangements. Microsoft has dedicated Dynamics hosting options.

The pitch is: you get to keep your configuration and your custom code (which you can't do in public SaaS), but the vendor takes over hosting, backups, patching, and infrastructure responsibility (which you don't want to do on-prem anymore). It's not the fastest to innovate — upgrades are still coordinated, not automatic — but it's a meaningful improvement over the on-prem project cycle.

This is where most of the big ECC-to-S/4HANA migrations are actually landing. A customer who spent fifteen years customising ECC isn't going to throw all of that away to move to public cloud and its standardised processes. Private cloud lets them bring their customisation with them, while escaping the on-premise treadmill.

Cost shape is opex — subscription — but the infrastructure cost is wrapped into it. Effectively more expensive per user than public cloud, because you're paying for a dedicated stack instead of sharing.

Who fits? Mid-to-large enterprises moving off on-premise. Customers with heavy customisation they can't or won't abandon. Industries that need more control over change windows than public cloud offers.

Option four — hybrid

Hybrid is less of a deployment model and more of a reality. Big global businesses end up running different workloads in different deployments — either during a multi-year migration, or because different regions and business units have different constraints.

A typical hybrid scenario: the corporate finance and consolidation runs on on-premise SAP because it's been there for twenty years. A newer subsidiary in Asia runs on S/4HANA public cloud because they started fresh last year. HR moved to Workday five years ago. Regional distribution hubs run on NetSuite. They all talk to each other over APIs and middleware.

Hybrid's "option" status is almost a misnomer — more often, it's the stable state that emerges after a decade of acquisitions, migrations, and regional choices. For the first five years of any multinational's cloud journey, the picture is almost always hybrid.

The challenge with hybrid is integration. Each system has its own master data, its own processes, its own upgrade cadence. Keeping them in sync is an ongoing engineering project, not a one-off implementation.

How companies actually choose

No single formula. But in practice, four questions narrow the decision to two or three options fast.

Greenfield or legacy? No existing ERP — go public cloud SaaS. Fastest and cheapest. Heavy legacy customisation — private cloud keeps your work. Somewhere in between — it depends on how much of the legacy is worth preserving.

What's the pace of change you can absorb? If your users can handle quarterly new features rolling in automatically, public cloud works. If your users are still adjusting to the last change from three years ago, on-prem or private cloud gives you control over when changes arrive.

What's the regulatory context? Some industries and jurisdictions require data to stay in specific geographies, or require explicit control over infrastructure. That can eliminate public cloud in parts of your business, even when it'd be fine for others.

What's the implementation appetite? A public-cloud go-live can happen in three to six months for a simple company. On-premise or private cloud for a large enterprise is eighteen to thirty-six months. If the business is impatient, the answer is cloud; if they're patient and value-fit more than speed, Tier-1 on-prem or private cloud is still worth it.

Answer those four and the shortlist writes itself.

The shift that's still happening

If you step back, the last twenty years of ERP have been a slow migration from on-premise to some flavour of cloud. Public cloud grew up first in the SMB segment; private cloud emerged to serve enterprises that couldn't accept public's standardisation; hybrid became the accidental default for everyone running multiple systems.

That shift isn't finished. Plenty of large enterprises still run on-premise ECC or equivalent, and they will for years. SAP's mainstream support for ECC ends in 2027, which forces the decision for most remaining customers. Oracle and Microsoft have their own versions of the same story.

The interesting question, if you're watching this industry, is less "cloud vs on-prem?" — that's settled — and more "which kind of cloud?" A private-cloud migration is cheaper and less disruptive than re-implementing in public cloud, but you never quite get the full benefits of SaaS. A public-cloud move is more disruptive but gets you fully onto the vendor's innovation curve.

There's no universally right answer. There's the answer that fits where your business actually is — and where it needs to be in five years.

Episode six is the season-one finale. We'll tour the full vendor landscape — SAP, Oracle, Microsoft, NetSuite, and the mid-market and specialty names — and cover how companies actually choose between them.