Security & IT
On-premise vs cloud vs private cloud: how manufacturers should choose
· 12 min read

More than half of EU companies now pay for cloud services, mostly for email, office software and file storage (Eurostat). Shop-floor software is a different decision. It runs next to production, it holds how your product is actually made, and it has to pass a security review written for machines, not laptops.
So when a plant buys software for the shop floor — work instructions, training records, quality forms — the on-premise vs cloud question comes up early, usually from IT. This guide explains the three deployment models in plain terms, what really changes between them, and the questions to answer before you choose.
Key takeaways
- The three models can run the same software. What changes is who runs it and where the data lives.
- In a plant, the network often decides. If station devices can't reach the internet, both cloud options need IT to open a connection first.
- Data stored in the EU is not automatically out of reach of US law. If jurisdiction matters, look at private cloud on infrastructure you choose, or on-premise.
- On-premise gives you the most control, and costs the most to run — for you and for the vendor.
Three deployment models, in plain terms
Vendors often call these cloud deployment models, though only two of them are cloud. When you buy an application, you're not choosing infrastructure. You're choosing where the vendor's software runs and who operates it.
Shared cloud (SaaS)
The vendor runs one platform for many customers in its own cloud. You sign in through a browser. There is nothing to install, and updates, backups and monitoring are the vendor's job. Each customer's data is kept separate, but the infrastructure is shared.
Private cloud
You get your own instance of the application — your own environment and database — that no other customer uses. The vendor usually still operates it. It can run in the vendor's cloud or in your company's own cloud subscription.
On-premise
The application runs on your own servers, in your data centre or on the plant network, under your policies. Your IT runs the servers; the vendor usually installs and updates the application, in maintenance windows you approve. If it's built for it, it can run on a network with no internet connection at all.
One warning on terms: in infrastructure discussions, "private cloud" can also mean a company's own virtualised data centre. When a vendor says "private cloud", ask who operates it and whose infrastructure it runs on.
| Shared cloud | Private cloud | On-premise | |
|---|---|---|---|
| Who runs the infrastructure | Vendor | Usually the vendor | Your IT |
| Infrastructure shared with other customers | Yes | No | No |
| Where the data lives | Vendor's cloud region | A region agreed with you, or your own cloud tenant | Your servers |
| Updates | Vendor's release schedule | Vendor, in agreed maintenance windows | Vendor or your IT, when you approve |
| Internet connection needed | Yes | Yes | No |
| Effort on your side | None | Low | Highest |
| Time to go live | Fastest | A dedicated environment to set up | Servers, installation and network changes first |
On-premise vs cloud (SaaS): what actually changes
The software can be identical. What changes is who does which job.
- Running it. In the cloud, servers, patching, backups and monitoring belong to the vendor. On-premise, they belong to you — for as long as the system runs, which in a plant can be a decade.
- Updates. Cloud customers get new versions when the vendor releases them. On-premise, you decide when to update — which also means you can fall behind.
- Speed to start. A cloud rollout can begin the week the contract is signed. On-premise waits for servers, installation and firewall changes.
- Cost. Cloud is a subscription with nothing to buy upfront. On-premise adds hardware, hosting and IT time on your side — and the licence usually costs more too. In a shared cloud, one update and one round of testing covers every customer. On-premise, the vendor installs over a VPN on your server, agrees each maintenance window with your IT, and tests each installation on its own. Private cloud sits in between, so prices typically rise from shared cloud to private cloud to on-premise.
- Control. On-premise, the data never leaves your perimeter, and your own backup, access and network rules apply without exception.
Neither model is more secure by default. A well-run cloud platform is usually patched faster than a server nobody owns. A well-run on-premise installation is not exposed to the internet at all. What decides it is who will operate the system well over its whole life.
Private cloud: the middle option
For many groups, private cloud is the option that satisfies the security policy without asking IT to run another application.
Single-tenant vs multi-tenant
A multi-tenant platform serves many customers from one application and database, kept apart by software. A single-tenant setup gives each customer its own instance. Both can be secure. Single-tenant matters when your policy says your data may not share infrastructure with other companies, or when you need control over the region and the maintenance windows.
A useful variant is a private instance that runs in your own cloud tenant. The vendor manages the application, but it lives in your subscription, under your existing cloud agreement and on your bill. For groups that already have an enterprise cloud contract, this is often the shortest route through procurement.
The question most guides skip: your plant network
Most on-premise vs cloud guides are written for office IT. In a plant, the deciding factor is often not the data. It's the network.

- Station devices sit on the production network. The tablets, terminals and MES screens operators use are often on a network kept separate from the office and from the internet.
- Every connection out has to be approved. Under IEC 62443, the main standard for industrial (OT) security, a plant is divided into zones, and every path between zones — including to the internet — is a controlled conduit.
- A cloud application needs one of those paths. Station devices must reach the vendor's platform. That's one more conduit for IT to approve, and in some plants the answer is no.
- On-premise avoids the question. Installed inside the plant network, the software never needs a path out. Private cloud sits in between: a path is still needed, but to one known, dedicated destination.
Ask this before you compare vendors: where will the device at the workstation sit, and what is it allowed to reach?
Data residency vs data sovereignty
The two terms get mixed up, and they answer different questions.
- Data residency is where the data is physically stored. "Hosted in Frankfurt" is a residency statement. It settles most GDPR questions about where personal data is kept.
- Data sovereignty is whose laws can reach the data. That depends on the provider, not only the data centre. US-headquartered cloud providers are subject to the US CLOUD Act, which lets US authorities request data the company controls wherever it's stored. In 2025, Microsoft's French legal director told a French Senate inquiry under oath that he could not guarantee EU customer data would never be handed to US authorities.
The big providers are responding: Microsoft completed its EU Data Boundary in 2025, and AWS launched a separate European Sovereign Cloud in January 2026.
For many plants, EU residency answers the question. When your legal team says jurisdiction matters too — typically in defence, export-controlled programmes or work for government customers — the realistic options are a private instance on infrastructure you choose, or on-premise.
Air-gapped networks: what still works offline
Some networks have no internet connection at all. Air-gapped networks are common in defence and in production areas closed by policy. Software can run there only if it's installed inside, and only the parts that don't call outside services will work.
What typically stops working:
- Automatic translation
- AI features, such as generating content or assessments
- Speech: voice-over and transcription
- Vendor remote support
- Automatic updates — new versions have to be brought in deliberately
"Works offline" is not an answer. Ask each vendor for the exact list of features that need a connection.
The rules that shape the choice
Outside defence and classified work, no regulation requires on-premise for shop-floor software. Several make IT ask harder questions.
- NIS2. Manufacturers of machinery, motor vehicles, electrical equipment, electronics and medical devices are in scope from medium size (generally 50+ employees). The directive includes managing the security of your suppliers — software vendors among them.
- TISAX. In automotive, the assessment covers the supplier, wherever its systems are hosted. Moving OEM information into a vendor's cloud doesn't take it out of scope.
- Export control and defence work. Technical data on controlled programmes often has to stay on networks the company controls.
- The EU Data Act. Since 12 September 2025, cloud and SaaS providers serving EU customers must support switching to another provider or back to your own infrastructure. Switching charges are limited to cost until January 2027 and disappear after that.
For your IT review
How to choose: five questions to answer first
- What does your security policy actually require?
Ask IT for the written rule. "Data must stay in the EU" and "data must stay on our network" lead to different answers.
- Can station devices reach the internet?
Ask the OT or network team. If the production network is closed, on-premise is usually the only practical option.
- Who will run the system for the next ten years?
On-premise needs an owner in IT — for servers, backups and update windows — not just an installation.
- How fast do you need to go live?
Shared cloud can start within days. On-premise depends on server provisioning and your IT's queue.
- Which features need a connection — and can you do without them?
In a multilingual plant, translation and AI features often matter more than expected.
As a rule of thumb:
-
Shared cloud
Single plants and first rollouts, where IT wants no footprint and station devices can reach the internet.
-
Private cloud
Groups whose policy rules out shared infrastructure, or who want the software in their own cloud tenant.
-
On-premise
Closed plant networks, defence and export-controlled work, and policies that keep data on your own network.
Checklist: what your IT team will ask a vendor
Bring these to the first technical call with any vendor. A good answer is specific.
Which deployment models do you offer — and is it the same product in each?
Good answer: one product, with the differences between models listed.
Where exactly is our data stored, and which company operates the infrastructure?
Good answer: a named region and provider, not just "in the EU".
Which features stop working without internet?
Good answer: a named list, not "it works offline".
Which certification covers your own company?
Good answer: ISO/IEC 27001 for the vendor's own security management, not only its cloud provider's.
How do users sign in?
Good answer: single sign-on through your identity provider (SAML 2.0 or OpenID Connect), or Active Directory.
Is a data processing agreement part of the contract?
Good answer: yes, as standard, not on request.
How do we get our data out?
Good answer: full export through the interface and an API, at any time.
Who installs and updates the software, and who can access our environment?
Good answer: a defined update process, named roles and logged access.
Where REWO fits
REWO runs in all three models, and it's the same product in each:
- Shared cloud on Microsoft Azure in Frankfurt, operated by us.
- Private cloud — a dedicated, single-tenant instance with its own environment and database, managed by us. It can run in your own cloud tenant.
- On-premise on your own servers, including on air-gapped networks. REWO runs on any virtual machine.
On an air-gapped network, automated translation, AI-assisted authoring and speech are unavailable. Authoring, delivery to the station, sign-off, versioning and the full audit record all run locally. The features that use Azure services can also run on your own Azure subscription instead of ours.
REWO is developed and operated under an ISO/IEC 27001-certified information security management system, and the data processing agreement is part of the contract.
Deployment choice is often why manufacturers choose us. A global automotive supplier and a European defence manufacturer both picked REWO because it could run on their own infrastructure. Their products are sensitive, so the knowledge of how they're made had to stay inside their own network — and many work instruction platforms are cloud-only.
Read next: Security & deployment · Work instructions for defence · How to compare work instruction software
FAQ
Not automatically. On-premise removes exposure to the internet and keeps data inside your perimeter, but only if someone keeps the servers patched, backed up and monitored. A well-run cloud platform is often better maintained than an on-premise server nobody owns.
Because each installation is separate work for the vendor. In a shared cloud, one update and one round of testing covers every customer. On-premise, the vendor installs over a VPN on each customer's server, coordinates maintenance with each IT team, and tests every installation individually. Private cloud sits in between: a separate environment, but one the vendor can maintain directly.
Where it runs and who runs the infrastructure. A private cloud is a dedicated instance, usually operated by the vendor, in its cloud or yours. On-premise runs on your own servers, maintained by your IT team.
Yes, if it's built for it. Features that call outside services — automatic translation, AI and speech — won't work on a fully offline network. Everything else can.
Hybrid usually means the core application runs on-premise while selected services, such as translation or AI, run in the cloud. Your data stays on your network, except the content you send to those services — for example, text going out for translation. It also needs the plant network to allow those connections.


