Latest From our Blog
Singapore is a hub, so we run two lanes: MAS/PDPA-regulated data stays in ap-southeast-1, while portable workloads shift to ap-southeast-5 (Malaysia) for ~13% arbitrage. Multi-cloud commitment management across AWS, Azure, and GCP, billed in SGD.
Singapore is expensive to run in and tightly regulated. MAS TRM guidelines and the PDPA pin financial and personal data to approved in-region infrastructure — but a lot of your estate isn't regulated and doesn't have to stay.
SquareOps classifies your workloads first, keeps MAS/PDPA data in ap-southeast-1, and moves portable workloads to ap-southeast-5 (Malaysia) for roughly 13% lower compute — plus commitments and waste teardown across AWS, Azure, and GCP.
Four families of optimization, all executed inside ap-southeast-1 — no residency compromise.
Right-sized Savings Plans and Reserved Instances tuned to your real usage curve — coverage without over-committing.
Move suitable workloads to Arm-based Graviton for better price-performance — assessed, tested, and rolled out safely.
Spot capacity for fault-tolerant and batch workloads, with graceful interruption handling so reliability holds.
Continuous rightsizing of EC2, RDS, and EKS from real utilization — cut the gap between provisioned and used.
Before any commitment purchase, we strip out the spend that delivers nothing. Typical idle-resource reclaim in a mid-size ap-southeast-1 account:
Ranges are illustrative for a mid-size AWS account — your free 37-check audit returns figures specific to your environment.
Run the free 37-check Cloud Cost Audit. We review your ap-southeast-1 account and return a prioritized teardown plan with a SGD savings estimate — no obligation.
Run a Free Scan in SpendZeroSingapore-anchored delivery covering the SEA region — residency held in ap-southeast-1, arbitrage run into ap-southeast-5.
We understand MAS TRM, PDPA, and the realities of running across Singapore and Malaysia — not a generic offshore engagement bolted onto APAC.
Real client outcomes and a success-fee model that ties our reward to your savings.
Commitment portfolio plus waste teardown, with MAS-bound data held in ap-southeast-1 and portable workloads moved to ap-southeast-5.
Non-residency services shifted to ap-southeast-5 (Malaysia) for materially lower compute, regulated data untouched.
Unified AWS, Azure, and GCP commitment management and showback across a multi-cloud estate.
"They knew exactly which workloads could move and which had to stay for MAS. We got the arbitrage savings without any compliance worry."
Where MAS/PDPA compliance and aggressive cost targets coexist, our two-lane model fits.
Banks, insurers, and fintech under MAS TRM — regulated data held in ap-southeast-1 with full audit evidence.
Multi-tenant platforms where margin depends on cost-per-customer — arbitrage the portable tier, commit the rest.
Regional supply-chain and tracking systems spanning SEA — multi-cloud commitments and waste teardown.
All fees billed in SGD with GST at 9%. Pick the model that matches your risk appetite.
A no-cost 37-check review of your AWS account with a prioritized savings estimate. The best place to start.
We're paid primarily from the money we save you. Incentives aligned, downside risk minimized.
Ongoing optimization with SpendZero — anomaly detection, commitment management, and continuous rightsizing.
Point us at your AWS account and we'll run all 37 checks — idle compute, orphaned storage, NAT and load-balancer waste, commitment gaps, and Graviton candidates — then hand you a prioritized plan with a SGD savings estimate. Everything stays in ap-southeast-1.
Residency, billing, and how the optimization actually works.
For workloads that are not pinned by MAS or PDPA residency, shifting compute to the ap-southeast-5 (Malaysia) region typically lowers compute cost by around 13% versus ap-southeast-1 (Singapore). We only move workloads we have classified as portable, and we keep regulated data in Singapore.
We run a data-classification exercise first, mapping each workload against MAS TRM and PDPA obligations. Regulated financial and personal data stays in ap-southeast-1; everything else is a candidate for arbitrage, commitments, or rightsizing. Residency is decided by the data, never by price alone.
Yes. Many Singapore estates span AWS, Azure, and GCP. We manage commitments — Savings Plans, Azure reservations, GCP CUDs — and showback across all three so coverage and allocation follow real usage in one view.
A no-cost review of your account against 37 cost and efficiency checks — idle compute, unattached storage, orphaned NAT gateways and load balancers, commitment coverage gaps, Graviton candidates, and more — returning a prioritized plan with an SGD savings estimate. No commitment required.
Our optimization is built around them. Regulated workloads stay in approved in-region infrastructure, every change is logged with a residency rationale for MAS and PDPC review, and the arbitrage lane is strictly limited to non-residency workloads.
Both. We can run a one-time teardown, classification, and commitment exercise, or operate ongoing managed FinOps with SpendZero across your multi-cloud estate. Most Singapore clients start with the free audit, then move to managed FinOps.
Same residency-first approach, localized to each market's rules and currency.
Talk to a SquareOps FinOps engineer about your ap-southeast-1 workloads, or kick off with the free 37-check audit. Residency-first, billed in SGD.
Start Your Free Scan