Vultr Cloud Compute 4 GB / 2 vCPU: Hourly Billing, 3 TB

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 official data confirms about this plan

The official pricing page lists four resources for Vultr Cloud Compute 4 GB / 2 vCPU: 2 vCPU, 4 GB of RAM, 80 GB SSD storage and 3 TB of bandwidth. The features describe the line as Regular Performance (previous-gen Intel, regular SSD), which is Vultr's own label for this family of servers, and note a flat monthly price (no intro discount).

Billing is listed as USD per month; billed hourly up to the monthly price. In plain words, charges build up hour by hour and stop climbing once they reach the monthly price in the table. The 1 month shown next to the plan is the cycle that this cap applies to; it is not a commitment you sign up for.

Because there is no intro discount, the renewal price is the same as the price for the first month. There is no promotional rate that ends later, so the figure in the price table is the figure to plan around.

The official data does not include benchmark results, uptime figures or performance numbers for this line. Any difference between Regular Performance and the other Vultr lines mentioned on this page can only be described by the hardware labels Vultr uses, not by measured speed.

Who this plan suits

This plan fits a developer who wants one server with enough memory to run an application runtime and a small database side by side. With 4 GB of RAM and 2 vCPU, a typical side project stack such as a web framework, a reverse proxy and a database can share the machine without the memory pressure that a smaller plan would bring. The 80 GB SSD leaves room for code, logs, uploads and database files, and 3 TB of bandwidth covers a small API that serves JSON responses to a modest number of clients.

It also fits someone who prefers to pay for a server by the hour while experimenting. Because charges build up hourly up to the monthly price, a short test deployment does not automatically cost a full month, which suits spinning up a staging copy or trying a new stack.

It is a less obvious fit if your workload is disk-heavy or you specifically want newer hardware. The features for this plan say previous-gen Intel and regular SSD, while the Vultr High Frequency and High Performance AMD lines list NVMe SSD. The official data gives no speed figures for either, so the choice comes down to whether the hardware label matters for your project and how the resources and price compare in the table.

Finally, this is a self-managed server. Vultr provides the machine; you install and maintain the operating system, the web server, the application and everything around it. If you want a provider to handle updates, security and backups for you, a managed hosting plan is a different category from this one.

How hourly billing up to a monthly price works

The billing line reads USD per month; billed hourly up to the monthly price. Each hour the server exists adds a charge, and the total for the cycle cannot exceed the monthly price shown in the table. A server that runs for the whole cycle reaches that cap; a server that exists for a shorter time accumulates less.

The feature list also mentions a flat monthly price (no intro discount). Read together with the billing line, that means the monthly amount is a ceiling on hourly charges, not a fixed charge taken in full each cycle regardless of use.

The official data does not say what happens to charges when a server is stopped, powered off or left idle, so do not assume that stopping a server reduces or ends charges. Confirm that behavior with Vultr before relying on it, especially for a side project you plan to switch on and off.

What a self-managed server needs: SSH, updates, firewall and backups

SSH access is how you will do everything on this server, from installing packages to deploying your API. Plan to add an SSH key when you create the server, disable password logins once key access works, and create a non-root user with sudo rights for day-to-day work. The official data does not list which operating system images are offered, so check that the distribution you want is available before signing up.

Updates are your responsibility on a self-managed server. After the first login, apply all pending package updates, then enable your distribution's automatic security update mechanism so patches are installed without you remembering to run them. For an API that may sit untouched for weeks, this matters more than it does for a project you deploy to daily.

A firewall should allow only the services you expose, typically SSH, HTTP and HTTPS, and reject everything else. The official data does not mention a provider-side firewall feature for this plan, so plan on configuring a host firewall inside the operating system and confirm with Vultr whether a network-level firewall is also available.

Backups are the piece most side projects skip and most regret. The official data does not confirm a backup or snapshot feature for this plan, so build your own routine: export the database on a schedule, archive the application files, and copy both off the server to object storage or another machine. Test a restore at least once; a backup you have never restored is a guess, not a safeguard.

How it compares with similar Cloud VPS plans

DigitalOcean Basic 4 GiB is the closest match on paper, with 2 vCPU, 4 GiB of RAM, 80 GiB SSD and 4,000 GiB of bandwidth. Its billing is USD per month; billed per second up to the monthly price (capped at 672 hours a month), and like the Vultr plan it has a flat monthly price (no intro discount) with the renewal price the same as the first month. Note that DigitalOcean lists memory, storage and bandwidth in GiB while Vultr lists GB and TB; these are different units and are not converted on this page, so compare them with that in mind.

DigitalOcean Basic 2 GiB / 2 vCPU keeps the same 2 vCPU but lists 2 GiB of RAM, 60 GiB SSD and 3,000 GiB of bandwidth, billed per second up to the monthly price (capped at 672 hours a month). It suits a lighter API or a static project that does not need a database living on the same machine.

Within Vultr, High Frequency 2 GB / 2 vCPU lists High Frequency (3GHz+ Intel Xeon, NVMe SSD), 2 vCPU, 2 GB of RAM, 80 GB NVMe SSD and 3 TB of bandwidth. High Performance AMD 2 GB / 2 vCPU lists High Performance (AMD EPYC, NVMe SSD), 2 vCPU, 2 GB of RAM, 60 GB NVMe SSD and 4 TB of bandwidth. Both are billed hourly up to the monthly price with a flat monthly price (no intro discount). Compared with the Regular Performance plan on this page, each has less RAM (2 GB rather than 4 GB) but lists NVMe SSD instead of regular SSD, and the AMD option lists more bandwidth (4 TB rather than 3 TB) with less storage (60 GB rather than 80 GB).

Which fits which situation: if your project needs memory for a database and an application runtime together, the two plans with 4 GB or 4 GiB of RAM are the ones to weigh against each other in the price table. If memory is less important than newer hardware labels or NVMe storage, the High Frequency and High Performance AMD lines are the ones to compare. If you expect very light traffic and a small footprint, the DigitalOcean 2 GiB plan is worth checking. None of this is a ranking; the official data has no performance figures, so the decision rests on the listed resources, the billing method and the prices in the table.

What to check before signing up

Read the billing line carefully: USD per month; billed hourly up to the monthly price. Decide whether an hourly model suits how you will use the server, and remember that the monthly price in the table is a cap on hourly charges, not a promotional rate that changes later. The renewal price is the same as the price for the first month.

The official data does not list data center locations or support details for this plan. If latency to a particular region matters for your API, or if you expect to need help from Vultr beyond documentation, confirm both before paying.

Check that the resources match your project: 2 vCPU, 4 GB of RAM, 80 GB SSD and 3 TB of bandwidth. Estimate your database size and growth, your log volume and the response sizes your API returns, and compare those against the listed figures rather than guessing.

Keep in mind what you are taking on. Operating system choice, updates, firewall rules, TLS certificates and backups are all yours to handle on this plan. The setup guide below walks through them in an order that works for a first deployment.