Colocation vs Public Cloud for Singapore Businesses: The 2026 Repatriation Decision

Between 2015 and 2022, the answer to almost every Singapore infrastructure question was the same: move it to the cloud. The cloud was faster to provision, cheaper than owning hardware, and required no capital outlay. The consultants recommended it, the vendors promoted it, and the SaaS-ification of enterprise software made it inevitable anyway.

In 2026, the calculation is more nuanced. Cloud repatriation — moving workloads back from public cloud to owned or colocated infrastructure — is no longer an edge case. For Singapore businesses in regulated industries, the driver is often not cost alone — it is data sovereignty, regulatory compliance, and predictability.

This article focuses specifically on the decision between colocation (renting space in a Singapore data centre) and public cloud (AWS, Azure, Google Cloud), for organisations with specific workloads that do not fit cleanly into a pure cloud model. If you are making this decision for the first time, or revisiting it in 2026, here is the framework.

What Colocation Is and Is Not

Colocation means your organisation owns the servers and storage equipment but rents physical space, power, cooling, and network connectivity from a third-party data centre. In Singapore, major colocation providers include:

• Equinix Singapore — SG1-SG5 campuses in Jurong, with direct interconnect to major cloud providers
• ST Telemedia Global Data Centres (STT GDC) — Singapore carrier-neutral facilities
• Keppel Data Centres — Green-rated facilities at multiple Singapore locations
• Global Switch Singapore — Large carrier-neutral facility in Tai Seng

What colocation gives you:

• Physical infrastructure (power, cooling, physical security) managed by a professional data centre operator
• Connectivity to multiple carriers and cloud on-ramps from a single facility
• Your own hardware, under your direct control
• Predictable cost per rack or per U (rack unit) per month
• Regulatory certainty — you know exactly where your data is

What colocation does not give you:

• Server management — you still provision, patch, and maintain your own hardware
• Automatic scalability — adding capacity requires purchasing and racking hardware
• Software-defined agility — spinning up a new environment in colocation takes days or weeks, not minutes

The correct comparison is therefore not "colocation vs cloud" as if they are interchangeable. It is a question of which workloads belong in colocation and which belong in public cloud — and for most Singapore businesses, the answer involves both.

The Regulatory Context: Why Colocation Matters for Singapore's Regulated Industries

The most significant driver of colocation decisions in Singapore is not cost — it is regulatory compliance, particularly for financial services.

MAS TRM Guidelines (Technology Risk Management): The Monetary Authority of Singapore requires financial institutions to maintain full accountability for technology risk across all IT systems, including those hosted by third parties. MAS TRM 2021 Guideline 9.4 specifies that outsourcing to cloud providers does not transfer regulatory responsibility — the FI remains accountable. For critical systems, FIs must ensure the cloud provider meets MAS Technology Risk Management standards and must have the right to audit.

More practically, regulated organisations need to understand where data is processed, what contractual controls apply, and whether audit or oversight rights meet their internal and regulatory expectations. Some financial institutions are comfortable with properly governed Singapore-region cloud services; others still prefer colocation for highest-sensitivity systems where physical control, audit evidence, and data sovereignty certainty are non-negotiable.

Healthcare: Singapore's Ministry of Health healthcare provider licensing requirements and the National Electronic Health Record (NEHR) framework impose specific obligations on how patient data is handled. The Healthcare Services Act 2020 and associated subsidiary legislation create obligations that some healthcare providers prefer to address through colocation of sensitive workloads rather than public cloud.

Defence supply chain and government-adjacent organisations: Companies in Singapore's defence and government technology supply chain may be subject to handling requirements for restricted data that explicitly prohibit public cloud storage.

When Colocation Wins the Analysis

Colocation makes financial and operational sense in three specific scenarios:

Scenario 1: High-performance, predictable workloads at scale

The economics of public cloud are attractive when workloads are unpredictable or bursty — you pay only for what you use. When workloads are large, predictable, and run continuously, the economics reverse.

An illustrative comparison for a 20-server environment running 24/7:

Indicative figures. Actual costs vary significantly by instance type, reserved pricing, and storage class.

For established Singapore businesses with predictable compute and storage requirements above a certain scale, the 5-year total cost of ownership for colocation is substantially lower than public cloud. The crossover point varies by workload profile, but as a general rule: when your monthly cloud bill for a specific workload exceeds SGD 8,000–10,000 and the workload is non-bursty, a colocation ROI analysis is worth running.

Scenario 2: Data sovereignty certainty is non-negotiable

AWS, Azure, and Google Cloud all offer Singapore-region infrastructure. For many workloads, configuring services to use Singapore regions is sufficient, but the actual data residency position depends on the specific service, backup, replication, support, and logging configuration.

However, regional configuration is not the same as absolute data sovereignty. Configuration errors, backup settings, logging, support access, or vendor legal processes may affect where data is processed or who can access it. The vendor controls the infrastructure, not you.

In colocation, the equipment is yours. The data centre is in Singapore. You control the access logs, the network configuration, and the data sovereignty documentation. For organisations where the auditor, regulator, or client requires this level of certainty, colocation provides it in a way that public cloud does not.

Scenario 3: Latency-sensitive workloads requiring sub-5ms connectivity

Applications that require sub-5ms latency to the data centre — real-time financial applications, low-latency database clusters, applications with tight response time SLAs — benefit from colocation at a facility with direct connections to your Singapore offices or exchange points.

Singapore's colocation facilities, particularly Equinix SG at Jurong, have direct physical interconnects to all major carriers and cloud providers. A Singapore business with a colocation rack at Equinix SG1 can achieve sub-2ms latency to its servers — latency that is difficult or impossible to achieve consistently from a public cloud even within the Singapore region.

When Public Cloud Wins

Public cloud is the right choice for four workload types:

Variable or unpredictable demand. Applications that spike seasonally or unpredictably — e-commerce platforms, event ticketing, marketing campaign landing pages — benefit from cloud elasticity. You cannot provision colocation capacity in response to a spike that lasts three days.

Rapid development and iteration. Cloud's self-service provisioning, managed database services, and CI/CD integrations make it significantly faster for development and testing environments. The speed advantage over colocation is real and material for engineering teams.

Globally distributed or multi-region applications. Public cloud's global network of regions makes it straightforward to deploy applications close to users in multiple geographies. Building equivalent global reach with colocation hardware is disproportionately expensive and complex.

SaaS-dependent applications. If your application is built on SaaS services that run in specific cloud regions (Salesforce, ServiceNow, SAP S/4HANA Cloud), your integration latency is minimised by being in the same cloud, in the same region.

The Hybrid Architecture: What Most Singapore Organisations Actually Run

A pure colocation strategy and a pure public cloud strategy both have limitations. Most Singapore organisations above a certain maturity level run hybrid architectures:

Tier 1 — Colocation for core, sensitive workloads: Production databases, financial processing systems, identity and access management infrastructure, high-availability systems with performance requirements.

Tier 2 — Public cloud for agile and scalable workloads: Development and staging environments, machine learning workloads, analytics platforms, globally distributed SaaS layers, disaster recovery compute capacity.

Tier 3 — SaaS for productivity and collaboration: Microsoft 365, Google Workspace, Slack, CRM, HR systems — where vendor management is simply not a strategic activity for most businesses.

The design question is not "cloud or colocation" but "which workloads go where, and how do they connect."

Connection between colocation and cloud is achieved through:

• Direct Connect (AWS) / ExpressRoute (Azure) / Cloud Interconnect (Google Cloud): Dedicated private connections from the Singapore DC to the cloud provider's network — bypassing the public Internet for lower latency and more predictable performance
• SD-WAN overlays: Software-defined WAN linking colocation, cloud, and office environments
• Cloud on-ramps: Available at Equinix and other Singapore facilities, providing physical interconnects to multiple cloud providers from a single rack

How Aggasys Positions Colocation Engagements

Aggasys works with Singapore clients as an implementation and managed services partner — we are not a colocation facility ourselves. Our role is to:

1. Assess which workloads belong in colocation vs cloud — based on performance requirements, regulatory obligations, cost profile, and growth trajectory
2. Design the hybrid architecture — specifying how colocation, cloud, and office environments connect and how data flows between them
3. Manage the infrastructure — providing ongoing managed services for servers in colocation, including monitoring, patching, incident response, and hardware management

For a Singapore financial institution, healthcare provider, or enterprise business considering or revisiting a colocation decision, this is the type of analysis that should precede any infrastructure commitment.

What We Typically See When Clients Revisit Their Cloud Strategy

Cloud bills that have grown beyond the original business case. The initial cloud migration was justified on a cost model that assumed reserved instances, minimal egress, and right-sized compute. The actual environment has on-demand instances running 24/7, significant egress charges, and storage that has accumulated without lifecycle management. The bill is 2–3x the projected cost.

Regulatory audit findings. A MAS examination or internal audit flags gaps in data sovereignty documentation for cloud-hosted systems. The organisation cannot demonstrate with certainty that data is not leaving Singapore under any circumstances. Colocation for the relevant systems resolves this cleanly.

Performance limitations for specific applications. A database system that performs acceptably in proof-of-concept hits latency or throughput limits in production because the cloud instance type is not equivalent to the physical hardware that was replaced. Colocation allows the original hardware specification to be maintained.

Unexpected complexity of multi-cloud connectivity. Connecting multiple cloud providers and on-premise offices through public Internet creates reliability and security challenges that were not anticipated. A colocation facility with direct cloud interconnects resolves this with dedicated, private connectivity.

Frequently Asked Questions

What is colocation exactly?

Colocation means your organisation owns its servers and storage hardware but rents physical space, power, cooling, and network connectivity from a third-party data centre — such as Equinix Singapore, STT GDC, Keppel Data Centres, or Global Switch Singapore. You get professionally managed physical infrastructure, connectivity to multiple carriers and cloud on-ramps, and full control over your own hardware at a predictable cost per rack or per U per month. What you don't get is automatic scalability or software-defined agility — adding capacity means purchasing and racking new hardware, and spinning up a new environment takes days or weeks rather than minutes.

How much does colocation cost in Singapore?

For a 20-server environment running continuously, colocation typically costs SGD 8,000–12,000/month for equivalent compute (hardware amortised plus rack rent and power), versus SGD 45,000–80,000/month for the equivalent on public cloud. Storage for 100TB runs roughly SGD 800–1,500/month in colocation versus SGD 3,500–6,000/month on S3 Standard. Over a 5-year period, this works out to roughly SGD 0.9–1.5M for colocation (including a hardware refresh) versus SGD 3.0–5.2M for public cloud — though actual figures vary significantly by instance type, reserved pricing, and storage class, so these should be treated as indicative rather than a quote.

When does colocation beat cloud?

Colocation wins in three scenarios: predictable, high-scale workloads running 24/7 (the general rule is that once a specific workload's monthly cloud bill exceeds roughly SGD 8,000–10,000 and it isn't bursty, a colocation comparison is worth running); situations where data sovereignty certainty is non-negotiable, since in colocation the hardware and data centre are entirely yours to audit rather than vendor-controlled; and latency-sensitive workloads requiring sub-5ms connectivity, where a colocation rack at a facility like Equinix SG1 can achieve sub-2ms latency that's difficult to match consistently in public cloud. Public cloud remains the better fit for variable demand, rapid development, globally distributed applications, and SaaS-dependent workloads.

Does PDPA affect whether I should use colocation or cloud?

PDPA's Protection Obligation requires reasonable security arrangements for personal data, and where that data is hosted is part of that picture. Regional cloud configuration (using Singapore-region AWS, Azure, or Google Cloud infrastructure) is not the same as absolute data sovereignty — configuration errors, backup settings, logging, support access, or vendor legal processes can still affect where data is actually processed or who can access it, since the vendor controls the infrastructure rather than you. With colocation, the equipment is yours and the facility is in Singapore, so you control the access logs and data sovereignty documentation directly. This is a bigger factor for MAS-regulated financial institutions and healthcare providers under NEHR/Healthcare Services Act obligations, but the same "who actually controls the data" question applies under PDPA for any Singapore business.

Does a hybrid model — some workloads in cloud, some colocated — make sense?

Yes, and it's what most Singapore organisations above a certain maturity level actually run rather than picking one model exclusively. A common pattern is: core, sensitive workloads (production databases, financial processing, identity and access management) in colocation; agile and scalable workloads (development/staging, machine learning, analytics, DR compute) in public cloud; and productivity/collaboration tools (Microsoft 365, Google Workspace, CRM, HR systems) left as SaaS. The two environments are then connected via dedicated private links such as AWS Direct Connect, Azure ExpressRoute, or Google Cloud Interconnect, SD-WAN overlays, or cloud on-ramps available at facilities like Equinix. The design question isn't "cloud or colocation" — it's which workloads belong where and how they connect.

Book a Free Infrastructure Assessment with Aggasys

If you are reviewing a cloud or colocation decision for your Singapore business — whether it is a first deployment, a repatriation analysis, or an existing environment that has grown beyond its original design — Aggasys provides a free infrastructure assessment. We will review your current workloads, identify which belong in cloud vs colocation, and provide a cost comparison with a recommended architecture.

Book your free assessment: aggasys.com/contact or call (+65) 6250 0045.