Cloud or On-Premise? The Saudi Version of the Question

The cloud-versus-on-premise argument is usually conducted in generalities. In the Kingdom it has specifics: where the data is allowed to live, what your regulator expects of your sector, and whether anyone in the building is actually responsible for the server in the cupboard.

Residency is a question of fact

Start by finding out what applies to you rather than assuming. Some sectors have explicit requirements about where data is held and how it may be transferred. Major providers now run regions inside the Kingdom, so “cloud” and “the data stays in Saudi Arabia” are no longer opposites — which removes the strongest historical argument for keeping a server room.

• What does your regulator require of your sector specifically?
• Does any data leave the Kingdom, including through backups and support access?
• Who is on call at 2am, and what is the actual recovery time?
• When were your backups last restored, rather than merely taken?
• What happens to the system when the person who set it up leaves?

On-premise is not cheaper, it is differently paid

A server bought outright looks cheaper than a subscription until you count the replacement cycle, the licences, the power, the backup that has to be tested, the security patches and the person whose weekend it becomes. Most of the on-premise systems we are asked to rescue were fine for three years and then hit all of those costs at once.

A backup nobody has restored is not a backup. It is a folder with a reassuring name.

The honest middle

Plenty of companies land on a split: the core system hosted in a Saudi region, with a specific workload kept local because a machine on the factory floor cannot wait for a network. That is a legitimate architecture, not a compromise — provided the split is a decision rather than an accident of history.

Whichever way it goes, write down the recovery time you are willing to accept and test against it. That single number resolves most of the argument.