Enterprise Cloud Services for South African Business
Build a cloud environment your operations can depend on.
Architecture, migration, hybrid operations, backup, security and managed support for selected enterprise cloud environments.
Discuss enterprise cloud services →Senior expertise focused on what the organisation needs to protect and improve.
Architecture, migration, hybrid operations, backup, security and managed support for selected enterprise cloud environments. Every engagement begins with the operating context, evidence and a clearly defined outcome.
A practical, accountable service.
Architecture and design
Design identity, networking, resilience, security, cost controls and operating responsibility.
Migration & hybrid cloud
Move workloads with dependency mapping, validation, rollback planning and controlled transition.
Managed cloud operations
Monitor, secure, optimise and support agreed production environments with clear accountability.
Clear steps. Visible decisions.
What cloud computing in South Africa actually involves
Cloud computing has stopped being a strategy and become an operating decision, made repeatedly, one workload at a time.
The South African context adds three considerations that a generic cloud conversation leaves out.
Local regions exist and they change the calculation. AWS operates the Africa (Cape Town) region. Microsoft Azure operates South Africa North in Johannesburg and South Africa West in Cape Town. In-country hosting means lower latency for South African users and a simpler data residency position.
POPIA shapes where data can sit. Transfers of personal information outside South Africa are restricted unless specific conditions are met. That does not prohibit offshore hosting and it does mean the decision has to be made deliberately rather than by default.
Connectivity and egress cost more than they do elsewhere. Moving large volumes of data in and out of cloud services from South Africa is a real line item, and architectures designed without it in mind produce bills nobody predicted.
None of that argues for or against cloud. It argues for assessing per workload, which is the position taken across every page in this pillar.
The cloud services we deliver
Cloud architecture
Landing zone design, account and subscription structure, identity, network topology, logging and policy baseline. The structural decisions that are expensive to change later. Covered on cloud architecture.
Cloud migration
Assessment per workload, migration approach selection, execution and cutover, with a documented position on what should not move. Covered on cloud migration.
Hybrid cloud
On-premises and cloud operating as one environment, with hybrid identity, connectivity and consistent management. The state most South African mid-market estates are actually in. Covered on hybrid cloud.
Cloud backup and storage
Backup into cloud storage, immutability, retention, tiering and the egress arithmetic that decides whether a restore is practical. Covered on cloud backup and storage.
Cloud security
Identity, least privilege, network exposure, encryption, logging and preventive guardrails across AWS and Azure. Covered on cloud security.
Managed cloud services
Ongoing operation: cost control, patching, monitoring, backup and capacity, on AWS and Azure. Covered on cloud managed services.
Microsoft 365 is a cloud service and it is a different discipline from cloud infrastructure. Covered separately on Microsoft 365 management.
AWS South Africa and Azure South Africa
Both major providers operate in-country and the practical differences are worth stating.
AWS South Africa
The Africa (Cape Town) region, af-south-1. Full-featured for mainstream services, with newer services arriving later than in the largest regions. Worth checking availability for anything specialised before committing an architecture to it.
Azure South Africa
South Africa North in Johannesburg is the primary region. South Africa West in Cape Town is Microsoft’s paired region, but access and service availability there are restricted for specific customer scenarios. Treat an in-country dual-region design as a workload-specific option to validate, not as an assumption. AWS currently has one public cloud region in Africa, in Cape Town.
Latency
In-country hosting is materially better for South African users than a European or American region. For interactive applications and anything chatty between client and server the difference is noticeable rather than theoretical.
Cost
Local region pricing generally sits above the largest global regions. Where a workload has no residency or latency requirement, that difference is worth weighing rather than assuming local is automatically correct.
Data residency
Hosting locally removes the transborder question for the data that sits there. It is not automatic, because backups, logging, analytics and managed-service control planes can still move data offshore. Establishing where data actually goes is a design exercise.
How we assess a workload
Six questions per workload, and the answers rarely point the same way for every system in an estate.
Does it have a residency or regulatory constraint? If personal information or regulated data is involved, that shapes the region before anything else does.
Is the demand steady or variable? Variable and unpredictable demand is where cloud economics work. Steady, high-utilisation workloads are frequently cheaper on owned hardware over a three to five year horizon.
What does the licensing do? Some licence models behave very differently on cloud infrastructure, particularly core-based database licensing. This can move the cost substantially in either direction and it is the factor most often missed.
How chatty is it? Applications with heavy client-server interaction or large data movement carry latency and egress costs that a diagram does not show.
What does it depend on? A workload with dependencies on on-premises systems does not move cleanly on its own, and moving it alone produces a hybrid arrangement nobody designed.
Is there a functional reason to move it? A stable application on hardware with life left in it, moved for no functional reason, spends money and adds risk in exchange for nothing.
What Namandla delivers
Cloud assessment
Workload-by-workload analysis, current cloud position where one exists, cost with attribution, security posture and architecture review.
Design and build
Landing zone, identity, network, policy and security baseline on AWS or Azure.
Migration
Phased, per workload group, with fallback and a written position on what stays.
Managed cloud operations
Cost, security, patching, backup, monitoring and capacity.
Hybrid integration
Identity, connectivity and consistent management across on-premises and cloud.
Cloud services are delivered remotely nationally. Onsite work in Gauteng where a hybrid environment or a migration needs it.
Common questions about Enterprise Cloud Services
What cloud services do you provide in South Africa?
Cloud architecture, migration, hybrid cloud, cloud backup and storage, cloud security and managed cloud operations, across AWS and Azure including the local South African regions.
We work with both major platforms rather than specialising in one, because the right platform depends on the workload, the existing licensing position and the residency requirement rather than on a supplier preference. Microsoft 365 is handled separately, since tenant administration is a different discipline from cloud infrastructure.
Is AWS available in South Africa?
Yes. AWS operates the Africa (Cape Town) region and Microsoft Azure operates South Africa North in Johannesburg and South Africa West in Cape Town, so both major providers offer in-country hosting.
The local regions carry the mainstream service catalogue, and newer or more specialised services arrive there later than in the largest global regions. Check availability for the specific services your architecture depends on before committing, because discovering a gap after migration is expensive to unwind.
Does POPIA require us to host in South Africa?
Not outright. POPIA restricts transfers of personal information outside South Africa unless specific conditions are met, including that the recipient is subject to a law or binding agreement providing adequate protection.
Hosting locally removes the question for data that stays there, and it is not automatic. A workload in a local region can still send data offshore through backups, logging, analytics or a managed service whose control plane sits elsewhere. Where you handle personal information at scale, mapping where data actually goes is worth doing explicitly, and whether your processing complies is a question for your information officer.
Should we move everything to the cloud?
No. Assess per workload. Some are cheaper, faster or simpler on premises, and some cannot move for latency, licensing or regulatory reasons.
The workloads that usually should move are email, file storage, backup targets, development environments and anything with unpredictable demand. The ones that usually should not are latency-sensitive production systems, anything with a licence model that penalises virtual cores and stable applications on hardware with life left in it.
Is cloud cheaper than on-premises?
It depends entirely on the workload profile. Variable and unpredictable demand is cheaper in cloud. Steady, predictable, high-utilisation workloads are frequently cheaper on owned hardware over three to five years.
The comparison people get wrong is capital against operating cost rather than total cost. An honest comparison includes hardware refresh, facilities, power, cooling, hypervisor licensing, backup infrastructure and the staff time to run it, against cloud compute, storage, transfer and management.
Which is better, AWS or Azure?
Neither in general. Azure frequently suits Windows-dominant estates with existing Microsoft licensing, because hybrid identity and licence benefits carry across. AWS has a broader service catalogue and a longer track record in some areas.
For most South African mid-market workloads either will do the job well. The decision is more usefully made on your existing licensing position, your team’s familiarity, whether you need two in-country regions and which platform has the specific services your architecture needs available locally.
What about our internet connectivity?
It becomes a dependency. A cloud-hosted line-of-business application means your connectivity is now part of your production infrastructure rather than a convenience.
That changes the resilience requirement: a second link with tested failover stops being optional. It also makes egress cost a real design consideration, because moving large volumes of data out of cloud services from South Africa is a genuine line item. Covered on multi-site connectivity.
Can you manage a cloud environment somebody else built?
Yes, and it is most of what we take on. Assessment first: cost with attribution, security configuration, identity and access, backup coverage and architecture, before anything changes.
The recurring findings are resources nobody switched off, over-broad identity permissions, no tagging so spend cannot be attributed, snapshots being treated as backups and the assumption that the provider is protecting your data. All of those are addressable without rebuilding.
When should we not use cloud services at all?
Where the workload is steady and high-utilisation, the hardware has life left in it, the licensing penalises virtual infrastructure and there is no functional gain from moving.
That combination is more common than cloud marketing suggests, particularly for a single line-of-business application on a stable server. We will say so during the assessment rather than finding a reason to move it. The cost of an unnecessary migration is not just the project, it is the ongoing bill for something that used to be a depreciated asset.