Cloud & Virtualization
Google Cloud
GCP compute and networking for workloads that benefit from its data and container services.

Capabilities
What we implement
- VPC and firewall design
- Compute sizing
- Managed database selection
- Workspace integration
Security
How it is hardened
- IAM policy design
- Service account hygiene
- Audit logging
Editions & pricing
Google Cloud editions and vendor pricing
Vendor list prices for the editions we deploy. Deployment, migration, hardening and support are quoted separately by Techno Trader PK — they are never bundled into these figures.
| Edition | Licensed by | Vendor list price |
|---|---|---|
| Compute Engine e2-standard-2 | per instance / month | Quote only |
| Compute Engine e2-standard-4 | per instance / month | Quote only |
Prices are checked against the vendor's published price list. Last verified 9 Sept 2026. Vendor list prices exclude tax and can change without notice. Vendor pricing page
Architecture
Google Cloud environment reference
Projects are the isolation boundary, IAM is granted on groups rather than individuals, and networking is shared rather than duplicated per team.
01 · Organisation & IAM
Organisation / foldersProjects per environmentGroups & IAM rolesOrg policiesAccess granted to groups at folder level; service accounts scoped and keyless wherever workload identity allows.
02 · Edge
Cloud DNSCloud Load BalancingCloud Armor / CDNGlobal load balancing with managed certificates and WAF rules at the edge.
03 · Network
Shared VPCSubnets per regionCloud NATFirewall rulesShared VPC keeps one network model while projects retain their own resource ownership.
04 · Compute & data
Compute EngineGKECloud RunCloud SQLCloud StorageManaged services chosen where they remove operational burden; instances sized from observed utilisation.
05 · Operations
Cloud MonitoringCloud LoggingBackup & DR serviceBudgetsLog sinks retained centrally, alerting on SLOs, budget notifications enabled per project.
FAQ
Google Cloud questions we are asked
- When does Google Cloud make more sense than AWS or Azure?
- Where the estate is container-heavy, data and analytics workloads dominate, or the organisation already runs Google Workspace identity. Otherwise selection follows cost, skills and support expectations.
- Do we need GKE, or is Cloud Run enough?
- Cloud Run handles stateless HTTP services with far less operational overhead. GKE is warranted when you need custom networking, operators, stateful workloads or fine-grained scheduling.
- How is spend controlled?
- Committed use discounts for steady workloads, autoscaling and preemptible or spot nodes where interruption is acceptable, plus per-project budgets and quota limits.
- Can Workspace identity be used for cloud access?
- Yes. Workspace groups drive IAM bindings, with 2-step verification enforced so cloud access inherits the same identity controls as mail.
Related
Other cloud & virtualization platforms
Google Cloud is referenced to describe engineering capability. All trademarks and product names are the property of their respective owners; no partnership or endorsement is implied.
Ready to scope the work?
Share your environment and objectives. You will get an engineering response covering scope, approach and considerations.