Cloud cost optimisation: gcloud pricing, Azure and AWS spend under control
Cloud cost optimisation lowers what you pay for Google Cloud, Microsoft Azure and AWS without weakening what you rely on, through rightsizing, commitments, storage tiers, tagging and budgets. Arke Technologies (Pty) Ltd, in Johannesburg, explains gcloud pricing, reviews cloud bills and keeps spend in check for organisations, public bodies and schools across South Africa.
Why cloud bills grow faster than budgets
Most cloud resources are charged for as long as they are switched on, whether or not anyone uses them. Bills grow quietly, and the causes are the same on every platform:
Oversized servers, sized for a peak that never came or copied from on-premises specifications.- Resources nobody owns: test environments left running, unattached disks, old snapshots, idle load balancers and reserved IP addresses.
- Data on the move: egress to the internet and between regions, often missing from the business case.
- Storage in the wrong class: backups and archives kept in the most expensive tier.
- Licences inside the bill: Windows Server, SQL Server and marketplace software charged by the hour.
- The exchange rate: list prices in US dollars, paid from a budget set in rand.
- No allocation: without labels or tags, no department sees its share, so nobody is accountable for it.
gcloud pricing: how Google Cloud charges, and where money leaks
gcloud is the name of Google Cloud's command-line tool, and many people use it as shorthand for the platform, so gcloud pricing means Google Cloud's price list. Google charges Compute Engine machines per second after the first minute, applies sustained-use discounts automatically to some machine families, and offers committed-use discounts, resource-based or spend-based, for one- or three-year terms. Spot VMs cost much less for work that can be interrupted.
Common leaks on Google Cloud: machines that Google's own Recommender already flags as idle or oversized; Cloud SQL instances running a high-availability standby for a test system; Cloud Storage kept in the Standard class where Nearline or Coldline would do; and egress from serving files straight out of a bucket instead of through a cache. Exporting billing data to BigQuery gives the line-by-line view that the console summary hides. For the platform itself, see Google Cloud services.
Cloud vendor management: contracts, licences and renewals
Cloud vendor management is the commercial side of the same job: knowing every provider behind your cloud, what you pay each one and when you can change it. Platforms, marketplace software, SaaS subscriptions, security and backup tools, connectivity and licences go into one register:
- Every contract, with its owner, term, notice period, renewal date, price basis (per user, per gigabyte or per site), currency and exit terms.
- Licences reconciled to people: unused seats removed and users moved to the plan they need. We supply Microsoft 365 and Google Workspace licences monthly or annually; see software licensing.
- Network subscriptions beside the cloud contracts. SD-WAN is usually priced per site by bandwidth tier, feature edition and term, and VeloCloud pricing typically follows that pattern, so VeloCloud cost rises with every branch and every bandwidth upgrade. A renewal is the moment to test whether each site still needs its tier; see SD-WAN and site connectivity.
- Ownership changes can reset terms at renewal, as many VMware customers found when licensing moved to subscription bundles. A register gives you the notice period to respond; see private cloud and virtualisation.
- Exit costs priced before you sign: data egress, export formats and notice periods.
Cloud budgets in the public sector and schools
Public bodies and schools approve their budgets in rand, for a financial year at a time; cloud platforms bill monthly, by use, in US dollars. We close that gap with a monthly forecast per department or school, actual-against-budget reporting and an early warning when a line will overrun.
Commitments need the right approval. A committed-use discount or reservation is a financial obligation that can run for three years. For a municipality, MFMA section 33 governs contracts whose obligations run beyond the three years covered by the budget; for departments and public entities, the accounting officer's delegations under the PFMA apply. We document the savings case and the risk so the decision can be approved and audited. King IV Principle 12 asks governing bodies to govern technology and information in a way that supports the organisation's strategic objectives, and our monthly reports give them the spend evidence to do so. See PFMA, MFMA and ICT procurement and IT for schools and education.
Risks of cutting cloud costs, and how we prevent them
A saving that breaks a service is not a saving. The guardrails we apply:
- Backups and disaster recovery are never trimmed below your retention policy without written approval; see backup and disaster recovery.
- Rightsizing is tested under load, with a rollback, in an approved change window.
- Deletions follow owner confirmation; nothing unlabelled is removed on assumption.
- Security logging is tuned, never switched off where POPIA, audit or incident response depends on it.
- Every change goes through change control, and any incident it causes is handled on the SLA's P1 to P4 scale.
What cloud cost optimisation costs
Last reviewed: September 2026.
We quote a cost review as a project, after a short assessment, and include ongoing optimisation in managed cloud under your SLA, reported at the monthly service review. The price depends on the number of platforms, accounts, subscriptions and projects, the state of labelling, the size of the estate and how much redesign the savings need. We publish no rates and promise no savings percentage before we have seen the bills.
Governance, compliance, procurement and continuity
- Governance: one SLA, with incidents prioritised P1 (critical outage) to P4 (low-impact request) and response and resolution targets agreed to your business impact; a monthly service review with the cost report; documented escalation paths; approved, logged changes.
- Compliance: cost changes respect POPIA data-residency and security requirements, controls stay aligned with ISO/IEC 27001 and the CIS Controls, and reports and approvals are kept ready for audit under the PFMA or MFMA and King IV.
- Procurement: Level 1 B-BBEE contributor, which gives buyers 135% procurement recognition (sworn affidavit available on request); CSD number, SARS tax compliance status and company documents available on request; SBD forms completed where a bid requires them. A cost review is bought against a proposal and your purchase order, ongoing optimisation runs under an SLA, and we respond to tenders where you run one. See procuring from Arke.
- Continuity: billing accounts, commitments, reports and the vendor register are yours; we work through read-only or individual, logged access, everyone with access is bound by confidentiality, and we hand everything over at exit, with the documentation.