TLS Certificate Automation: Get Ready Before March 2027
TLS certificates now last 200 days and drop to 100 in March 2027. A practical guide to automating renewals with ACME and monitoring expiry before outages.
Hosting in Iraq is changing. A practical method for IT leaders to place each system locally, regionally or in the cloud, with resilience and an exit plan.

For many organisations, hosting in Iraq has meant putting systems abroad and hoping the international link holds. That is starting to change. Local data centre capacity is being built, and global cloud providers are now in talks about the market.
In my view, IT leaders should not wait for "the cloud to arrive". They should decide now where each system belongs. That decision should rest on how sensitive the data is, how much downtime the system can tolerate, how fast users need it, and how easily the organisation could move it later.
Several things have happened in a short period.
At the same time, connectivity is still not something to take for granted. The IODA monitoring project recorded a critical drop in Iraq's connectivity on 5 September 2026, with alerts for Baghdad and Diyala. Fibre cable damage and power outages have also caused disruptions across the region.
And more services now need to stay up all the time. The KRG's e-Psule payment platform, launched in February 2026, has processed more than three million transactions across nine banks and licensed wallets. The aim is to collect 90% of government revenue through it by the end of 2028. When that much depends on a platform, where it is hosted is a board-level question.
The common mistake is to pick a provider first and then decide what to put there. Turn it round. List every system and place it in one of these groups:
For each system, record four things: who owns it, how sensitive the data is, its RTO (how long it can be down) and its RPO (how much data you can afford to lose). A public brochure site might tolerate a day of downtime. A payment gateway might tolerate minutes. These numbers drive everything that follows.
Once systems are classified, compare where each could run against the same criteria. Here is the table I use as a starting point. Treat it as a general guide, not a verdict. Your own providers and contracts will change the answers.
| Criterion | On-premises | Local colocation / Tier III site | Regional cloud | In-country hyperscaler (future) |
|---|---|---|---|---|
| Latency for users in Iraq | Low | Low | Depends on international links | Expected to be low |
| If the international link fails | Local users unaffected | Local users unaffected | Local users may lose access | Local users unaffected |
| If local power fails | Depends on your own UPS and generators | Should be designed for redundancy, so verify it | Not affected locally | Should be designed for redundancy |
| Data stays in country | Yes | Yes | No | Yes |
| In-house skills needed | High: hardware, power, cooling, networking | Medium: you run servers, they run the facility | Medium: different, cloud-specific skills | Medium |
| Ease of leaving | Hardware is a sunk cost | Moderate | Hard if you rely on proprietary services | Same lock-in risk as any cloud |
| Local time zone and language support | Your own team | Usually yes | Varies | Not yet known |
Most organisations will end up with a mix. Citizen data and payments may sit locally. A public website may sit in a regional cloud behind a content delivery network. AI experiments may run wherever the compute is available. That is fine, as long as each choice is deliberate and written down.
Hosting decisions in Iraq have to assume that links and power will fail sometimes. Practical steps:
Backups matter, but they are not the whole answer. As Sygnia notes on ransomware response, organisations need tested recovery and a plan for data theft as well. Readiness should be measured by real outcomes, such as how long it actually takes to restore critical operations. Keep backups isolated from production, and test restores every quarter.
New facilities will market themselves well. Ask for evidence, not labels:
Banking, payments, health and government may each have their own rules on where data can be hosted. Confirm with your regulator or legal adviser before you choose. Don't rely on assumptions or what a vendor tells you.
The best time to plan leaving a provider is before you sign. Prefer portable building blocks such as containers, standard databases and infrastructure-as-code. Document your data export formats. Make sure the contract states that your data will be returned and deleted when you leave. This also keeps a future move to an in-country cloud region simple if one launches.
Every hosting model splits responsibility differently. Write down who patches what, who monitors what and who responds to incidents. Whatever the model, use MFA for all admin access, encrypt data at rest and in transit, and keep your own encryption keys where you can.
If your organisation wants local, managed hosting rather than running its own server room, that is one valid option. My company, Standing (standingtech.com), provides cloud hosting, managed services and information security services for organisations in Iraq and the Kurdistan Region. Whoever you choose, put them through the same questions above.
CIOs are being asked to show value, govern data better and keep spending under control. A hosting plan with measured results does all three. Here is a simple 90-day plan:
After that, review placement once a year, or whenever a new local provider or cloud region becomes available.
The infrastructure around hosting in Iraq will keep changing over the next few years. Organisations that know their systems, their recovery targets and their exit routes will be able to move when better options appear. The one thing I'd ask every IT leader to do this quarter is classify your workloads and test one real restore. Everything else builds on that.
🤖 Researched and drafted with AI assistance, guided by my editorial standards. Spotted something wrong? Tell me.