Compare
PortvMind Cloud vs Google Cloud: services, regions and GPUs
Updated: · Comparison generated from structured data
Direct answer
Choosing between PortvMind Cloud and Google Cloud depends first on location, required services and GPU access. 4 documented capabilities are only available on PortvMind Cloud and 1 only on Google Cloud. Measured performance is covered on the benchmark pages.
Executive summary
PortvMind Cloud and Google Cloud document 25 and 22 of the same 26 criteria respectively, with 21 capabilities in common. PortvMind Cloud bills per-minute and Google Cloud bills per-second. PortvMind Cloud has 2 full regions in Türkiye; Google Cloud has an announced Türkiye region. PortvMind Cloud offers H100, H200, L40S; Google Cloud offers H100, H200.
Key findings
- 01 Capabilities documented only by PortvMind Cloud: Open-source cloud stack (OpenStack-based), S3-compatible object storage, Infrastructure located in Türkiye, NVIDIA L40S instances.
- 02 Capabilities documented only by Google Cloud: Managed database.
Overview
| PortvMind Cloud | Google Cloud | |
|---|---|---|
| Headquarters | Türkiye | Mountain View, United States |
| Operator | vMind Bilgi Teknolojileri | Google LLC |
| Regions | Two published regions in Türkiye — İstanbul (tr-ist-01) and Ankara (tr-ank-01). Services are limited to these regions. | Global regions; a Türkiye region has been announced (with Turkcell) but is not yet open. |
| Billing model | Per minute — Per-minute pay-as-you-go. Stopping a resource stops the compute charge; allocated disks and stored data keep accruing. Monthly figures in the calculator are 720-hour estimates, excluding tax. New accounts receive a free usage allowance (published as ₺2,000 on the Turkish site and $45 on the English pricing page). | Per second — Compute Engine VMs are billed per second with a one-minute minimum; sustained- and committed-use discounts apply to eligible machine types. |
| Documented capabilities | 25 / 26 | 22 / 26 |
| Technologies | OpenStack, Kubernetes, S3 API, Terraform, REST API | Kubernetes (GKE), Terraform, Cloud Storage XML API |
Availability and regions
PortvMind Cloud
- İstanbul tr-ist-01 Generally available
- Ankara tr-ank-01 Generally available
Google Cloud
- Frankfurt europe-west3 Generally available
- Türkiye (announced) turkiye-announced Coming soon
Features
| Criterion | PortvMind | Google Cloud |
|---|---|---|
| Data residency | ||
| Infrastructure located in Türkiye Generally available compute and storage capacity physically located in Türkiye (full region or local zone). | Yes Full regions in İstanbul (tr-ist-01) and Ankara (tr-ank-01). | Planned Announced November 2025; not yet open. |
| Compute & GPU | ||
| Virtual machine instances Self-service virtual machines with selectable CPU/RAM profiles. | Yes | Yes |
| Per-second or per-minute billing Standard compute billed at per-second or per-minute granularity rather than per started hour. | Yes Per-minute billing. | Yes Per-second with a one-minute minimum. |
| Dedicated / single-tenant resources Dedicated hosts, bare metal or organisation-dedicated cloud capacity. | Yes | Yes Sole-tenant nodes. |
| NVIDIA H100 instances On-demand or reservable instances with NVIDIA H100 GPUs. | Yes Published prices for 1–4 GPU profiles. | Yes |
| NVIDIA H200 instances On-demand or reservable instances with NVIDIA H200 GPUs. | Yes Listed option; price not in public table. | Yes |
| NVIDIA L40S instances On-demand or reservable instances with NVIDIA L40S GPUs. | Yes Listed option; price not in public table. | No |
| Platform & automation | ||
| API and Terraform automation Documented API plus an available Terraform provider for infrastructure as code. | Yes | Yes |
| Open-source cloud stack (OpenStack-based) The provider publicly states that its IaaS control plane is built on OpenStack or an equivalent open-source stack. | Yes OpenStack, Kubernetes and S3-compatible storage. | No |
| Kubernetes | ||
| Managed Kubernetes Provider-operated Kubernetes control plane. | Yes | Yes |
| Kubernetes node autoscaling Worker node count scales automatically within configured limits. | Yes | Yes |
| Kubernetes LoadBalancer integration Services of type LoadBalancer provision a provider load balancer automatically. | Yes Public and internal load balancers. | Yes |
| Kubernetes storage classes (CSI) Persistent volumes provisioned dynamically through a provider storage class. | Yes | Yes |
| Storage & data | ||
| Block storage volumes Persistent, attachable and expandable block volumes. | Yes | Yes |
| Volume snapshots Point-in-time snapshots of block volumes. | Yes | Yes |
| S3-compatible object storage Object storage reachable through the S3 API or an S3-compatible API. | Yes | Partial XML API interoperability with HMAC keys; not full S3 API parity. |
| Managed backup service Scheduled backup and restore for instances or volumes managed by the provider. | Yes Instances, volumes and Kubernetes PVCs. | Yes |
| Managed database Provider-operated relational database service. | Planned Announced as coming soon; not generally available. | Yes |
| Networking | ||
| L4 load balancer (TCP/UDP) Transport-layer load balancing. | Yes NetBalancer (TCP/UDP). | Yes |
| L7 load balancer (HTTP/HTTPS) Application-layer load balancing with HTTP health checks. | Yes AppBalancer (HTTP/HTTPS). | Yes |
| Reassignable static public IP Static public addresses that can be moved between resources (Floating/Reserved/Elastic IP). | Yes | Yes Static external IP addresses. |
| Private networks / VPC Isolated tenant networks with custom CIDR ranges. | Yes Isolated networks with custom CIDR. | Yes |
| Virtual router with NAT Managed router or NAT gateway for egress and inter-subnet routing, including static routes. | Yes Router with NAT option and static routes. | Yes Cloud Router and Cloud NAT. |
| Security groups / cloud firewall Stateful, API-managed network access rules. | Yes | Yes VPC firewall rules and policies. |
| Security & auditing | ||
| Control-plane audit logging A provider service that records management (API/console) operations against cloud resources. | Yes vTrail (provider-supplied capability information). | Yes Cloud Audit Logs. |
| User identity attribution in audit events Each audit event identifies the authenticated principal that performed the operation. | Yes vTrail records the authenticated user, project and scope (provider-supplied). | Yes |
Pricing and GPUs
| Provider | NVIDIA H100 | NVIDIA H200 | NVIDIA L40S | Türkiye infrastructure |
|---|---|---|---|---|
| PortvMind Cloud | Generally available gpu.h100s / gpu.h100m profiles TRY 195.835 / GPU-h 1, 2, 3 or 4 GPUs per server; 80 GB (81,920 MB) VRAM per GPU; 26 vCPU and 496 GB RAM per GPU; local NVMe disk included. | Generally available GPU / AI Compute (H200 option) Listed as an available GPU option; configurations and prices are not included in the public calculator table and are provided via the console or sales. | Generally available GPU / AI Compute (L40S option) Listed as an available GPU option; configurations and prices are not included in the public calculator table and are provided via the console or sales. | Yes |
| Google Cloud | Generally available A3 High / A3 Mega Up to 8 H100 GPUs per VM; zone availability varies. | Generally available A3 Ultra 8 H200 GPUs per VM; zone availability varies. | Not offered | Announced |
Prices are shown in the currency each provider publishes; no exchange-rate conversion is applied.
Benchmarks
Sources
- [1] Hakkında — PortvMind Cloud ve vMind — PortvMind Cloud Provider (first-party) accessed:
- [2] PortvMind Cloud — homepage and calculator price tables — PortvMind Cloud Provider (first-party) accessed:
- [3] PortvMind Cloud — Turkish homepage — PortvMind Cloud Provider (first-party) accessed:
- [4] Cloud pricing approach — PortvMind Cloud Provider (first-party) accessed:
- [5] Services and capability status (llms-full.txt) — PortvMind Cloud Provider (first-party) accessed:
- [6] GPU / AI Compute — PortvMind Cloud Provider (first-party) accessed:
- [7] VKE — managed Kubernetes — PortvMind Cloud Provider (first-party) accessed:
- [8] Agent Cloud — PortvMind Cloud Provider (first-party) accessed:
- [9] New Google Cloud region coming to Türkiye — Google Cloud Official documentation accessed:
- [10] GPU locations — Compute Engine — Google Cloud Official documentation accessed:
- [11] Cloud Audit Logs overview — Google Cloud Official documentation accessed:
Related research
Provider discovery
AWS alternatives with infrastructure in Türkiye
AWS, PortvMind Cloud, Google Cloud, Azure and the other tracked providers when a workload needs an AWS alternative in Türkiye.
Cloud security & auditing
AWS CloudTrail alternatives: audit logging on other clouds and OpenStack
CloudTrail's equivalents on Google Cloud, Azure, OpenStack-based clouds and smaller providers, compared on scope, identity, retention, export and integrity.
GPU & AI infrastructure
Best GPU for LLM inference: matching H100, H200 and L40S to model size
Which GPU to use for LLM inference by model size, precision, context length and concurrency — a sizing guide for Qwen, Llama, DeepSeek and MiniMax.
Cloud security & auditing
Cloud activity monitoring: how audit logs, alerts and metrics fit together
The difference between cloud audit logging, activity monitoring and performance monitoring, and how to build alerts on audit events across providers.