Vultr Cloud Compute 1 GB: Hourly Billing, 1 vCPU, 25 GB SSD

Plan details (official data)

Inclusions and features (official data)

• Regular Performance (previous-gen Intel, regular SSD)
• flat monthly price (no intro discount)

Prices were checked on Vultr's official pricing page on Oct 8, 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)

Swipe the table to see more →

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

What the plan includes

The official pricing page lists four resources for this plan: 1 vCPU, 1 GB of RAM, 25 GB SSD storage and 1 TB of bandwidth. The listed features are Regular Performance (previous-gen Intel, regular SSD) and flat monthly price (no intro discount). That is the full extent of what the data confirms about the hardware and the inclusions.

For a WordPress site, those numbers describe the whole box: the operating system, the web server, PHP, the database, WordPress itself and the backups you keep locally all share the 1 GB of RAM and the 25 GB SSD. On shared hosting the database and mail usually lived on separate systems that the host maintained; here, anything you want running has to fit inside these resources and be installed by you.

The plan is a self-managed server. The data does not mention a control panel such as cPanel, a one-click WordPress installer, managed backups, snapshots, a managed firewall, server locations or support channels, so none of those should be assumed to be included. If any of them matter to your decision, confirm them with Vultr before paying.

How billing works on this plan

The billing field reads USD per month; billed hourly up to the monthly price. In practice this means charges accumulate hour by hour and are capped at the monthly price in the table. The 1 month listed as the term is the billing cycle of that cap, not a commitment: there is nothing in the data that describes a longer period or a prepayment.

Because the price after the first month is listed as the same as the price in the first month, there is no intro discount to lose later. The features call this a flat monthly price, but the hourly billing field is the governing description: treat the monthly figure as the most a running server costs in a cycle rather than as an identical charge every month.

The data does not say what happens to charges when a server is stopped, idle or deleted. Do not assume that powering a server off reduces the bill; ask Vultr how charges are calculated for stopped or deleted servers before relying on that behavior.

What changes when you leave shared hosting

On shared hosting, the host installs and patches the operating system, PHP and the database, runs a firewall, keeps backups and usually offers a control panel. On Vultr Cloud Compute 1 GB, every one of those tasks moves to you. The first day is spent installing a web server such as Nginx or Apache, PHP, MySQL or MariaDB and WordPress, and the following months are spent keeping them updated.

Security updates are the biggest ongoing change. A shared host applies operating system patches without telling you; on a self-managed server, unattended security updates have to be enabled and checked, and the WordPress core, themes and plugins still need updating from the dashboard or with WP-CLI. A server that nobody patches is the most common way a migrated WordPress site ends up compromised.

Backups are the second change. The official data does not list a backup or snapshot feature for this plan, so plan your own routine: export the database on a schedule, archive the WordPress files, and copy both somewhere off the server. A good habit on the new server is a regular database export with WP-CLI from the WordPress folder: wp db export ~/backup.sql. Replace the file path with your own backup location and move the file off the server afterward, because a backup stored only on the 25 GB SSD disappears with the server.

The third change is the firewall. Shared hosts block unwanted traffic for you; here you should configure a host firewall that allows only SSH, HTTP and HTTPS, and consider limiting SSH to key-based logins. None of this is complicated, but it is work that did not exist on shared hosting.

Who this plan suits

This plan fits a WordPress owner who runs a single modest site, is comfortable with a terminal, and wants to learn server administration without paying for resources that a small site will not use. With 1 vCPU and 1 GB of RAM it can run a lightweight WordPress stack, and the hourly billing makes it reasonable to create a server, practice the migration, and keep it only once the site is working.

It fits less well for an owner who wants someone else to apply patches, restore backups or answer tickets about a broken plugin. Nothing in the data describes managed services, and the Regular Performance (previous-gen Intel, regular SSD) feature indicates this is the baseline tier rather than the faster tiers compared below. A site with heavy page builders, large WooCommerce catalogs or several high-traffic sites on one server may outgrow 1 GB of RAM quickly.

What to check before signing up

Read the price table for the monthly cap and keep in mind that charges build up by the hour toward it. Check with Vultr which operating system images are available, which locations the server can be created in, whether automatic backups or snapshots can be added, and how support works, because the listing supplied for this page does not cover those points.

Confirm that your current shared host lets you export the WordPress database and download the files, and that you can change nameservers or DNS records at your registrar. Also verify how Vultr charges for a server that is stopped or deleted, since the data only describes charges for the running monthly cap.

Finally, be honest about time. A self-managed server needs a few minutes of attention most weeks for updates and backup checks. If that is not realistic, a managed WordPress host may be the better fit even though it costs more in resources per dollar.

How it compares with the alternatives

Vultr High Frequency 1 GB lists the same 1 vCPU, 1 GB of RAM and 1 TB of bandwidth, with 32 GB NVMe SSD storage and the feature High Frequency (3GHz+ Intel Xeon, NVMe SSD). Vultr High Performance AMD 1 GB also lists 1 vCPU and 1 GB of RAM, with 25 GB NVMe SSD storage, 2 TB of bandwidth and the feature High Performance (AMD EPYC, NVMe SSD). Both share this plan's billing of USD per month; billed hourly up to the monthly price, a 1 month cycle and the same price after the first month. For a WordPress site whose database reads and writes are noticeable, the NVMe tiers are the ones to compare in the table; for a small blog where the RAM is the limiting factor, all three Vultr tiers offer the same 1 GB.

DigitalOcean Basic 512 MiB lists 512 MiB of RAM and 10 GiB SSD storage, and DigitalOcean Basic 1 GiB lists 1 GiB of RAM and 25 GiB SSD storage. Both carry the feature Flat monthly price (no intro discount), a 1 month cycle and the same price after the first month. Their billing field reads USD per month equivalent; billing term and prepayment depend on plan, which is a different description from Vultr's hourly cap, so read each provider's own billing page before comparing costs. Neither DigitalOcean listing includes a CPU count or bandwidth figure, and the storage units differ (GiB versus GB), so do not rank the disks by the numbers alone.

Which fits which situation: the DigitalOcean Basic 512 MiB is the smallest listing here and suits an experiment or a static placeholder rather than a production WordPress site; the DigitalOcean Basic 1 GiB and Vultr Cloud Compute 1 GB are the baseline options with comparable RAM; the two faster Vultr tiers suit a site that already feels slow on shared hosting and wants NVMe storage, with the AMD tier adding 2 TB of bandwidth for sites that serve many images or downloads.

Common migration problems and how to approach them

The site shows the old host after switching DNS. Lower the TTL on your DNS records before the move, then wait for caches to expire; check which IP the domain resolves to from an outside network rather than trusting your own browser cache.

WordPress loads but media is missing. The uploads folder was probably not copied completely, or file permissions prevent the web server from reading it. Re-copy wp-content/uploads and make sure the web server user owns or can read the files.

Mixed-content warnings after enabling HTTPS. The database still contains links beginning with http. Update the Site Address and WordPress Address settings to https and run a search-and-replace on the database with WP-CLI rather than editing rows by hand.

The server runs out of memory under load. With 1 GB of RAM, a page cache plugin or server-level caching, a lean PHP-FPM worker count and a small swap file usually stabilize a modest site. If memory pressure continues, that is the signal that the plan is too small for the workload.

Email stops arriving. Shared hosting often included mailboxes; a self-managed server does not, and nothing in this plan's data mentions mail. Use a separate mail provider and keep MX records pointing there rather than at the new server.