Hourly use has a monthly ceiling
Vultr bills Cloud Compute and other non-GPU server types hourly up to 672 hours per month. The API exposes both an hourly and monthly price, so use the monthly figure as the maximum server charge for a full month.
Disclosure: We earn commissions from partner links. This doesn't affect our rankings. Learn more
See current Vultr VPS pricing, hourly and monthly billing rules, regional price differences, backup costs, and shared versus dedicated CPU choices.
Vultr VPS pricing looks simple until region, compute tier, backups, bandwidth, and server lifecycle enter the bill. The useful comparison is not one headline price. It is the total for the exact plan and location your workload needs.
Check current Vultr plans and regions →We queried Vultr's public Plans API on October 24, 2026. These are regular shared Cloud Compute examples with public IPv4 support. They are a dated buying snapshot, not a promise that every plan remains available in every region.
| Resources | Base hourly price | Base monthly price | Storage | Included outbound transfer |
|---|---|---|---|---|
| 1 vCPU, 1 GB RAM | $0.007 | $5 | 25 GB SSD | 1,024 GB |
| 1 vCPU, 2 GB RAM | $0.014 | $10 | 55 GB SSD | 2,048 GB |
| 2 vCPU, 4 GB RAM | $0.027 | $20 | 80 GB SSD | 3,072 GB |
Regional exception found in the same API response: São Paulo lists these three plans at $7.50, $15, and $30 per month. Vultr also lists smaller 512 MB plans, but their location and networking availability is limited. For a fair comparison, start with a plan that is actually deployable where your users are.
Vultr bills Cloud Compute and other non-GPU server types hourly up to 672 hours per month. The API exposes both an hourly and monthly price, so use the monthly figure as the maximum server charge for a full month.
A short-lived server still incurs at least one hour. Hourly billing is useful for tests and temporary capacity, but it should not be confused with per-second billing.
Stopping an instance does not release its compute, storage, or IP allocation. Vultr says billing stops only when the server is destroyed.
Backups, extra storage, load balancers, reserved IPs, optional DDoS protection, licenses, excess transfer, and tax can add to the compute price.
| Decision | Shared Cloud Compute | Optimized Cloud Compute |
|---|---|---|
| CPU model | Shared CPU virtual machine | Dedicated CPU virtual machine |
| Current categories | Cloud Compute, High Frequency, High Performance | VX1, General Purpose, CPU, Memory, and Storage Optimized |
| Good starting fit | Low-traffic sites, blogs, development, tests, and small databases | Production sites, CI, video processing, and resource-intensive databases |
| Main tradeoff | Lower entry price with variable access to CPU resources | Higher price for more predictable resource allocation |
A 4 GB shared plan and a 4 GB dedicated plan do not represent the same performance commitment. Choose by sustained CPU, memory, storage, and transfer needs before comparing the price.
Vultr's public Regions API returned 33 locations on October 24, 2026. Plan availability and price can still vary by location. The cheapest global headline is not automatically available in the region you need.
Automatic Backups currently add 20 percent to the instance price. They capture the active file system but exclude attached Block Storage volumes.
Vultr counts outbound internet transfer against the plan allowance. Inbound transfer is not metered. Review current overage terms if the workload serves large downloads, media, or backups.
DDoS protection and Reserved IPs are optional paid features, not universal free inclusions. Check the order summary for the selected region and instance.
The current platform is broader than the old page suggested. Vultr documents managed Kubernetes and managed database services for MySQL, PostgreSQL, Valkey, and Apache Kafka. It also offers load balancers, Block Storage, Object Storage, snapshots, firewalls, VPC networking, and a public API.
Vultr is a credible shortlist option when location choice and hourly capped billing matter. Its public API makes plan and regional differences unusually inspectable. The buying risk is focusing on one low headline price while ignoring region availability, backup cost, stopped-server billing, and the difference between shared and dedicated CPU.
For a small self-hosted service, begin with the smallest widely available shared plan that meets memory and storage needs. For a sustained database, build pipeline, transcoding job, or busy production application, compare Optimized Cloud Compute rather than assuming a larger shared plan is equivalent.
Facts checked on October 24, 2026 against Vultr's public Plans API and Regions API, plus its Cloud Compute overview, shared CPU provisioning guide, dedicated CPU provisioning guide, server billing rules, regional pricing note, backup pricing and scope, and managed database list.
API values are stored as a dated baseline in the maintenance record. Always confirm the final region, resources, optional services, tax, and total in the Vultr Console before deployment.
Confirm the exact plan, location, backup setting, transfer allowance, and monthly total before creating the server.
Open current Vultr options →In Vultr’s public Plans API snapshot checked on October 24, 2026, regular shared Cloud Compute starts at $3.50 per month for 512 MB in New Jersey. A more widely available 1 GB plan is listed at $0.007 per hour with a $5 monthly price. Prices and availability can differ by location, so confirm the selected region in the Vultr Console.
Yes. Vultr documents hourly server billing with a monthly cap. Cloud Compute and other non-GPU server types are billed up to 672 hours per month. The minimum billing unit is one hour.
No. A stopped server still reserves resources and continues to incur charges. Vultr says you must destroy the server to stop server billing.
Vultr currently prices Automatic Backups at 20 percent of the instance cost. They cover the instance’s active file system, not attached Block Storage volumes, so additional storage needs a separate backup plan.
Shared Cloud Compute suits websites, development environments, and workloads that can tolerate variable CPU access. Optimized Cloud Compute uses dedicated CPU resources and is the better starting point for sustained production, CI, video processing, and demanding databases.
Not always. Vultr says regional operating costs can change hourly and monthly rates. Its public API snapshot shows São Paulo price overrides on several shared plans, so compare the exact plan and region before deploying.