Compare
Amazon Web Services vs Vultr: services, regions and GPUs
Updated: · Comparison generated from structured data
Direct answer
Choosing between Amazon Web Services and Vultr depends first on location, required services and GPU access. 7 documented capabilities are only available on Amazon Web Services and 0 only on Vultr. Measured performance is covered on the benchmark pages.
Executive summary
Amazon Web Services and Vultr document 25 and 18 of the same 26 criteria respectively, with 18 capabilities in common. Amazon Web Services bills per-second and Vultr bills per-hour. Amazon Web Services has a Local Zone in Türkiye; Vultr has no infrastructure in Türkiye. Amazon Web Services offers H100, H200, L40S; Vultr offers H100, L40S.
Key findings
- 01 Capabilities documented only by Amazon Web Services: Per-second or per-minute billing, Volume snapshots, Virtual router with NAT, Control-plane audit logging, User identity attribution in audit events, Infrastructure located in Türkiye, NVIDIA H200 instances.
- 02 Capabilities documented only by Vultr: none.
Overview
| Amazon Web Services | Vultr | |
|---|---|---|
| Headquarters | Seattle, United States | West Palm Beach, United States |
| Operator | Amazon Web Services, Inc. | The Constant Company, LLC |
| Regions | Global regions; in Türkiye an Istanbul Local Zone (GA May 2026) with a subset of services, parented to Europe (Frankfurt). | Cloud locations on six continents, including several in Europe; none in Türkiye. |
| Billing model | Per second — On-demand Linux EC2 instances are billed per second with a 60-second minimum; other operating systems and services have their own meters. | Per hour — Hourly billing. GPU plans bill on a 730-hour month (actual calendar hours); standard compute instances cap monthly billing at 672 hours. |
| Documented capabilities | 25 / 26 | 18 / 26 |
| Technologies | Nitro System, S3 API, CloudFormation, Terraform | Kubernetes (VKE), S3 API, Terraform |
Availability and regions
Amazon Web Services
- Europe (Frankfurt) eu-central-1 Generally available
- Istanbul Local Zone istanbul-local-zone Generally available
Vultr
- Frankfurt fra Generally available
- Amsterdam ams Generally available
Features
| Criterion | AWS | Vultr |
|---|---|---|
| Data residency | ||
| Infrastructure located in Türkiye Generally available compute and storage capacity physically located in Türkiye (full region or local zone). | Yes Istanbul Local Zone with a subset of services (GA May 2026); not a full region. | No |
| 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-second for Linux on-demand (60 s minimum). | No Hourly billing. |
| Dedicated / single-tenant resources Dedicated hosts, bare metal or organisation-dedicated cloud capacity. | Yes Dedicated Hosts and bare-metal instances. | Yes Bare Metal. |
| NVIDIA H100 instances On-demand or reservable instances with NVIDIA H100 GPUs. | Yes | Yes |
| NVIDIA H200 instances On-demand or reservable instances with NVIDIA H200 GPUs. | Yes | Unverified |
| NVIDIA L40S instances On-demand or reservable instances with NVIDIA L40S GPUs. | Yes | Yes |
| 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. | No | 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 | 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 | Unverified Instance snapshots are available; block-volume snapshots not assessed. |
| S3-compatible object storage Object storage reachable through the S3 API or an S3-compatible API. | Yes Native S3. | Yes |
| Managed backup service Scheduled backup and restore for instances or volumes managed by the provider. | Yes | Yes |
| Managed database Provider-operated relational database service. | Yes | Yes |
| Networking | ||
| L4 load balancer (TCP/UDP) Transport-layer load balancing. | Yes | Yes |
| L7 load balancer (HTTP/HTTPS) Application-layer load balancing with HTTP health checks. | Yes | Yes |
| Reassignable static public IP Static public addresses that can be moved between resources (Floating/Reserved/Elastic IP). | Yes Elastic IP addresses. | Yes Reserved IPs. |
| Private networks / VPC Isolated tenant networks with custom CIDR ranges. | Yes | Yes |
| Virtual router with NAT Managed router or NAT gateway for egress and inter-subnet routing, including static routes. | Yes Route tables and NAT Gateway. | Unverified |
| Security groups / cloud firewall Stateful, API-managed network access rules. | Yes | Yes Firewall groups. |
| Security & auditing | ||
| Control-plane audit logging A provider service that records management (API/console) operations against cloud resources. | Yes AWS CloudTrail. | Unverified |
| User identity attribution in audit events Each audit event identifies the authenticated principal that performed the operation. | Yes | Unverified |
Pricing and GPUs
| Provider | NVIDIA H100 | NVIDIA H200 | NVIDIA L40S | Türkiye infrastructure |
|---|---|---|---|---|
| Amazon Web Services | Generally available EC2 P5 Single-GPU p5.4xlarge and 8-GPU p5.48xlarge sizes; availability varies by region. | Generally available EC2 P5e / P5en 8-GPU instances; availability varies by region. | Generally available EC2 G6e 1 to 8 L40S GPUs per instance. | Yes |
| Vultr | Generally available Cloud GPU — NVIDIA HGX H100 $2.300 / GPU-h 8× H100 80 GB SXM (640 GB GPU RAM, 216 vCPU, 1,914 GB RAM). | Unverified Not listed on the public pricing page H200 was not listed on the Vultr pricing page at the last review date. | Generally available Cloud GPU — NVIDIA L40S $1.671 / GPU-h 1, 2, 4 or 8× L40S 48 GB; 1× plan with 16 vCPU and 180 GB RAM. | No |
Prices are shown in the currency each provider publishes; no exchange-rate conversion is applied.
Benchmarks
Sources
- [1] Now Open — AWS Local Zones in Istanbul, Türkiye — AWS Official documentation accessed:
- [2] Introducing three new NVIDIA GPU-based Amazon EC2 instances (P5e, G6, G6e) — AWS Official documentation accessed:
- [3] Amazon EC2 On-Demand Pricing — AWS Official documentation accessed:
- [4] AWS CloudTrail User Guide — AWS Official documentation accessed:
- [5] Vultr pricing — Vultr Official documentation accessed:
- [6] How are GPU products billed differently? — Vultr Official documentation accessed:
- [7] NVIDIA HGX H100 on Vultr — Vultr 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.
Provider discovery
Cloud providers in Türkiye: regions, local zones and GPU availability
Which global and regional cloud providers operate infrastructure in Türkiye, what type it is, and which services and GPUs are available locally.