We have expanded our Klang Valley cloud region, adding capacity for both general-purpose cloud workloads and GPU compute. The expansion is live for new and existing customers, and it was brought online without taking the region offline. New instances can be provisioned from the portal today. Existing customers can move into the new capacity at no cost, scheduled around their own working hours.
What we added to the region
The expansion adds general-purpose cloud capacity and GPU capacity in the same region. General-purpose instances cover web tiers, application servers, databases and internal tooling, with local NVMe storage and private networking between instances. GPU capacity is intended for training, fine-tuning, inference serving and rendering, and it sits on the same private network as the rest of the region, so a training job can read its dataset from an instance beside it rather than across the public internet.
Physically, the new capacity sits in racks with dual A and B power feeds, redundant cooling and diverse network paths out of the hall. We commissioned the cabinets with a burn-in period before placing customer workloads on them, and we plan against observed growth rather than a forecast alone. When a hall approaches its agreed threshold, the next build starts, so capacity arrives before the demand curve does.
Nothing about the way you use the platform changes. The same portal, the same API, the same images and the same private networking model apply to the new capacity. If you already run workloads in this region, your instances keep their addresses, their volumes and their snapshots. You can place new work in the expanded capacity by selecting it when you create an instance, and no migration is required to stay where you are.
- Additional cloud and GPU capacity
- Free migration, scheduled in MYT
- No change to existing pricing in Ringgit
- Backups continue to replicate across in-country regions
Where your data sits
All workloads in this region run on hardware we operate inside Malaysia. That covers the compute, the storage and the network path between them. Customer data, backups and model checkpoints remain in country, and they are governed by Malaysian law, including the Personal Data Protection Act 2010. We can name the facility in your contract, which is the difference between a policy and an address.
Backups written here replicate to our other in-country region, so a second copy exists without leaving the country. Snapshot and backup data is encrypted at rest, replication traffic is encrypted in transit, and restore procedures are exercised rather than documented. A backup that has never been restored is a hypothesis, and we would rather test it on a schedule than during an incident.
- Customer data and backups
- Model checkpoints and training artefacts
- Volume snapshots and replicas
- Access and audit logs
Data residency stops being a policy statement and becomes something you can point at.
Migrating existing workloads
New instances are available immediately from the portal, with no waiting list and no approval step. Existing customers can migrate into the expanded capacity at no cost, and we schedule those moves during local business hours, Monday to Friday between 9:00 and 18:00 MYT, so your own team is awake if a decision is needed. Nothing moves without a window you have agreed.
On our side, a migration is a sequence of small steps rather than one cutover. We drain connections from the old instance and let in-flight requests finish, then shift DNS with a short TTL while both instances are still serving. The previous instance stays available until the new one has passed its health checks, and rollback remains possible for the whole window. Maintenance that could affect you is announced at least seven days in advance.
- We agree the window with you before anything moves
- Traffic is drained rather than dropped
- DNS changes use a short TTL with rollback ready
- The old instance stays up until health checks pass
Pricing stays in Ringgit
There is no change to existing pricing in Ringgit and no surcharge for the new capacity. Invoices continue to be issued in Ringgit with Sales and Service Tax shown separately, and you can settle by FPX online banking, DuitNow QR, Touch 'n Go eWallet or card. Nothing in this expansion adds a currency line item that you have to explain to an auditor.
How we run the region
The region is monitored continuously, with security monitoring running around the clock and engineering support during local business hours. We watch capacity headroom, storage latency, network path health and error rates, and we review those numbers against the growth we are actually seeing. Maintenance is announced at least seven days ahead, and any incident that affects customers is followed by a written review within five business days.
The commitments around this region do not change with the expansion. Availability is contracted at 99.95%, security incidents are acknowledged within fifteen minutes, and support runs during MYT business hours with escalation outside them. If something goes wrong, you will hear it from us before you read it on a status page, and you will get the timeline afterwards.
- Capacity headroom reviewed against growth
- Storage and network path health
- Error rates and latency per service
- Restore testing on a quarterly schedule
How to move
If you want to move into the expanded capacity, open a request from the portal and we will schedule the window with you. If you would rather stay exactly where you are, nothing changes and nothing is required. Either way, the answer to where your data is processed is the same one we have given since this region opened.
