Cloud vs on-premise ERP: data residency, cost and control
Where your production database physically sits, who runs it, and what each choice costs — with the in-Kingdom residency requirements that decide it for many Saudi organisations.
| What you are comparing | Cloud | On-premise / private |
|---|---|---|
| Where data sits | The provider's data centre — ask which country, and where backups go | Your data centre or your own virtual machines |
| Who operates it | The provider: patching, backups, availability | Your team or your contractor |
| Cost shape | Operating expense, predictable per period | Capital up front, plus staff and hardware refresh |
| Time to start | Days | Weeks — procurement, provisioning, hardening |
| Works when the internet is down | Branch stops unless the till holds offline | Local network keeps running |
| Meeting a residency mandate | Only if the provider hosts in-country and proves it | By construction |
Residency is a requirement, not a preference
For many Saudi organisations — government-linked entities, healthcare, regulated finance, and anyone whose contracts say so — production data must remain inside the Kingdom. That single sentence removes most of the market before any feature comparison starts, so establish it first.
When you ask, ask about backups too. Residency that covers the primary database while the nightly backup replicates to another region is not residency, and that detail is usually in the small print rather than the sales deck.
The hybrid middle
These are not the only two options. A common arrangement keeps the production database on infrastructure you choose — our EU platform in Frankfurt, in-Kingdom hosting on request, or your own site — with a cloud replica for reporting and analytics. Operational data stays where the rules require; the load of reporting sits somewhere cheaper to scale.
Point of sale usually needs a local answer regardless of the model: a till that cannot sell when the connection drops is a business risk, so offline capability with later reconciliation matters more than deployment topology.
Compare the real cost, not the licence
On-premise costs more than the hardware: patching, backup verification (a backup you have never restored is a hope), someone available when it fails at month-end, and a refresh cycle every few years. Cloud costs more than the subscription: bandwidth, integration, and the migration you will want the day you change providers.
The question worth asking either way is the exit one. Can you take a full, usable export of your data — transactions, master data, signed invoice XML — on demand and without a paid project? If not, the deployment model is the smaller of your problems.
When on-premise is clearly right
A mandate that requires it. Sites with genuinely poor connectivity, where a plant or remote branch cannot depend on a link. An existing, well-run data centre with the staff to operate it. In those cases on-premise is not conservatism, it is the correct engineering decision — and any vendor who cannot deploy that way has disqualified itself rather than educated you.