Vultr High Performance AMD 4 GB / 2 vCPU: Billed Hourly

We earn commissions when you shop through the links below.

๐Ÿ”„ Last updated: Prices checked Oct 11, 2026

Disclosure: This page contains affiliate links. If you buy or sign up through them, we may earn a commission at no extra cost to you.

Vultr High Performance AMD 4 GB / 2 vCPU is a Cloud VPS plan from Vultr that lists 2 vCPU, 4 GB of memory, 100 GB NVMe SSD storage and 5 TB of bandwidth. Charges build up by the hour up to the monthly price shown in the price table, and the features list a flat monthly price (no intro discount). This page is written for a WordPress site owner who is leaving shared hosting and will manage the server personally. It covers what the official data confirms about the plan, how the hourly billing works, and what changes when installation, security updates and backups become the owner's responsibility rather than the host's.

Plan details (official data)

PlanVultr High Performance AMD 4 GB / 2 vCPU
HostVultr
CategoryCloud VPS
Price (monthly)$24.00
Billing cycle1 month
BillingUSD per month; billed hourly up to the monthly price
CPU2 vCPU
RAM4 GB
Storage100 GB NVMe SSD
Bandwidth5 TB

Inclusions and features (official data)

Prices were checked on Vultr's official pricing page on Oct 11, 2026. The renewal price listed there is the same as the sign-up price (no intro discount). Prices change, so confirm on the official site before you buy.

Compare plans in this category (official data)

PlanHostPrice (monthly)Term or billing cycleBillingCPURAMStorageBandwidth
Vultr High Performance AMD 4 GB / 2 vCPU (this plan)Vultr$24.001 monthUSD per month; billed hourly up to the monthly price2 vCPU4 GB100 GB NVMe SSD5 TB
DigitalOcean Basic 2 GiB / 2 vCPUDigitalOcean$18.001 monthUSD per month equivalent; billing term and prepayment depend on plan2 vCPU2 GiB60 GiB SSDNot listed
Vultr High Frequency 2 GB / 2 vCPUVultr$18.001 monthUSD per month; billed hourly up to the monthly price2 vCPU2 GB80 GB NVMe SSD3 TB
Vultr Cloud Compute 4 GB / 2 vCPUVultr$20.001 monthUSD per month; billed hourly up to the monthly price2 vCPU4 GB80 GB SSD3 TB
Vultr High Frequency 4 GB / 2 vCPUVultr$24.001 monthUSD per month; billed hourly up to the monthly price2 vCPU4 GB128 GB NVMe SSD3 TB

All values in this table come from each host's official pricing page. This plan was checked on Oct 11, 2026; every compared plan was checked within the last 60 days.

What the plan includes

The official pricing data lists four resources for this plan: 2 vCPU, 4 GB of memory, 100 GB NVMe SSD storage and 5 TB of bandwidth. The features describe the hardware tier as High Performance (AMD EPYC, NVMe SSD), which is the plan's own wording for its processor and storage type. No speed figures, uptime figures or benchmark results are part of the data, so none are given here.

The listed term is 1 month. Because the plan is billed hourly, that term is the billing cycle of the monthly cap, not a commitment of any kind. The plan is a self-managed server, which means the operating system, web server, PHP, database, WordPress, updates and backups are all set up and maintained by the owner.

How hourly billing works on this plan

The billing field reads: USD per month; billed hourly up to the monthly price. In practice, usage is metered by the hour and the total for a month stops rising once it reaches the monthly price shown in the price table. That monthly figure is a cap on what a full month of use can cost, not a fixed charge that is taken in advance.

The features also state a flat monthly price (no intro discount), and the renewal price is the same as the intro price. There is no promotional rate that ends after the first month, so the cap for later months is the same cap that applies at the start. The official data does not say what happens to charges when a server is powered off, stopped or destroyed, so anyone who plans to pause a server should confirm that behavior with Vultr before relying on it.

What changes when you leave shared hosting

On shared hosting, the host installs and patches the web server, PHP and the database, usually provides a control panel, and often handles SSL certificates and backups. On this plan the owner receives a server with an operating system and does the rest: choosing and installing a web server such as Nginx or Apache, PHP, MySQL or MariaDB, and then WordPress itself. Moving an existing site means exporting the files and database from the shared host and importing them on the new server before changing DNS.

Security updates become a routine the owner has to run. That includes operating system package updates, WordPress core, plugin and theme updates, a firewall that allows only SSH, HTTP and HTTPS, and keeping the SSH login locked down to key-based access. None of this happens on its own unless the owner configures it.

Backups are the biggest change for most people coming from shared hosting. A working backup routine on a self-managed server means regularly exporting the WordPress database, archiving the site files, copying both somewhere off the server, and testing a restore at least once so the procedure is known to work before it is needed in an emergency.

What the official data does not confirm

The data for this plan does not list backups, snapshots, a control panel, a one-click WordPress installer, email hosting, available operating system images, server locations or support options. A WordPress owner who relied on any of those on shared hosting should check Vultr's own documentation or ask the provider before signing up, and should plan to arrange backups and monitoring independently if they are not included. This page does not describe menus or buttons in the Vultr account because the data does not cover them.

How it compares with the alternatives

Vultr High Frequency 4 GB / 2 vCPU lists the same 2 vCPU and 4 GB of memory, with 128 GB NVMe SSD storage and 3 TB of bandwidth, and describes its hardware as High Frequency (3GHz+ Intel Xeon, NVMe SSD). Compared with the plan on this page, it lists more storage and less bandwidth. Billing and term are identical: billed hourly up to the monthly price, 1 month, flat monthly price (no intro discount). A site with a large media library may care more about the storage figure; a site that serves a lot of downloads or traffic may care more about the bandwidth figure.

Vultr Cloud Compute 4 GB / 2 vCPU also lists 2 vCPU and 4 GB of memory, with 80 GB SSD storage and 3 TB of bandwidth, and is described as Regular Performance (previous-gen Intel, regular SSD). It shares the same hourly billing, 1 month cycle and flat monthly price (no intro discount). It suits an owner who wants the same memory and CPU count on the regular tier rather than the High Performance (AMD EPYC, NVMe SSD) tier; the data gives no speed figures for either, so the price table is the place to weigh the difference.

Vultr High Frequency 2 GB / 2 vCPU lists 2 vCPU, 2 GB of memory, 80 GB NVMe SSD storage and 3 TB of bandwidth, with the same billing and term as the other Vultr plans. It fits a smaller WordPress site that needs less memory. DigitalOcean Basic 2 GiB / 2 vCPU lists 2 vCPU, 2 GiB of memory and 60 GiB SSD storage; no bandwidth figure is in its data, its storage and memory are written in GiB rather than GB so they are not ranked against the Vultr figures here, and its billing field reads: USD per month equivalent; billing term and prepayment depend on plan. It also lists a Flat monthly price (no intro discount). An owner comparing providers rather than tiers should read that billing wording carefully, because it differs from the hourly model on this page.

Who this plan suits

This plan suits a WordPress owner who is comfortable working over SSH, wants to control the full stack, and accepts responsibility for updates, security and backups in exchange for a server that is not shared with other customers' sites. The 4 GB of memory and 2 vCPU are the listed resources; whether they are enough for a given site depends on traffic, plugins and caching, and the data includes no benchmark to answer that.

It is a weaker fit for someone who expects a control panel, managed updates, included backups or email hosting, since none of those appear in the official data. Before signing up, read the monthly price in the table as the cap for hourly charges, confirm with Vultr how stopped or destroyed servers are charged, and make sure a backup routine is planned before the live site is moved.

Practical setup guide

  1. STEP 1Deploy the server and note its IP address

    Create the server from the Vultr account, choose an operating system that the planned WordPress stack supports, and write down the IP address once the server is running. Log in over SSH, create a non-root user for daily work, and switch SSH to key-based login so password guessing is not possible. Keep the IP address handy, because the DNS step depends on it.

  2. STEP 2Install the stack and copy the site over

    Install a web server such as Nginx, PHP, and MySQL or MariaDB, then place the WordPress files from the shared host export into the web root and import the exported database. Update the WordPress configuration with the new database credentials and confirm the site loads on the new server before touching DNS, for example by testing with a temporary hosts-file entry on a local computer. Fix any missing PHP extensions or file permission errors at this stage, while the old shared host still serves visitors.

  3. STEP 3Point the domain at the new server

    At the domain's DNS provider, change the A record, and the AAAA record if the server has one, to the new server's IP address, and remove old records that still point at the shared host. From a local computer, confirm the change has taken effect by running this command, replacing example.com with the real domain: dig +short A example.com. Wait until that command returns the new IP address before moving on to the certificate.

  4. STEP 4Issue a TLS certificate once DNS resolves

    After the domain resolves to the new server, use Certbot with the Nginx plugin to request a Let's Encrypt certificate for the domain and its www name, and let Certbot configure HTTPS and the redirect from HTTP. Open the site in a browser to confirm the padlock appears and that WordPress addresses in the settings use https. Test the automatic renewal that Certbot sets up so the certificate does not lapse later.

  5. STEP 5Set up security updates, a firewall and backups

    Enable automatic security updates for the operating system, keep WordPress core, plugins and themes current, and configure a firewall that allows only SSH, HTTP and HTTPS. Export the database on a schedule, for example with WP-CLI if it is installed: wp db export ~/backup.sql, then archive the site files and copy both off the server, and test a restore once so the process is proven. Note that charges build up hourly up to the monthly price in the price table, and confirm with Vultr how stopped or destroyed servers are charged before relying on that to control cost.

Frequently asked questions

โ†‘ Back to the price table and plan link

Found this helpful? Share this article.