Vultr Cloud Compute 2 GB / 2 vCPU: Billed Hourly, 65 GB SSD
We earn commissions when you shop through the links below.
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 Cloud Compute 2 GB / 2 vCPU is a self-managed Cloud VPS from Vultr with 2 vCPU, 2 GB of RAM, 65 GB SSD storage and 3 TB of bandwidth. The official pricing page lists billing as USD per month; billed hourly up to the monthly price, and describes the price as a flat monthly price (no intro discount), so the price at renewal is the same as the initial price. This page looks at how the plan fits a web agency that keeps separate staging and client servers and wants access, backups and billing to stay organized per project.
Plan details (official data)
| Plan | Vultr Cloud Compute 2 GB / 2 vCPU |
|---|---|
| Host | Vultr |
| Category | Cloud VPS |
| Price (monthly) | $15.00 |
| Billing cycle | 1 month |
| Billing | USD per month; billed hourly up to the monthly price |
| CPU | 2 vCPU |
| RAM | 2 GB |
| Storage | 65 GB SSD |
| Bandwidth | 3 TB |
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)
| Plan | Host | Price (monthly) | Term or billing cycle | Billing | CPU | RAM | Storage | Bandwidth |
|---|---|---|---|---|---|---|---|---|
| Vultr Cloud Compute 2 GB / 2 vCPU (this plan) | Vultr | $15.00 | 1 month | USD per month; billed hourly up to the monthly price | 2 vCPU | 2 GB | 65 GB SSD | 3 TB |
| DigitalOcean Basic 2 GiB | DigitalOcean | $12.00 | 1 month | USD per month equivalent; billing term and prepayment depend on plan | Not listed | 2 GiB | 50 GiB SSD | Not listed |
| Vultr High Frequency 2 GB | Vultr | $12.00 | 1 month | USD per month; billed hourly up to the monthly price | 1 vCPU | 2 GB | 64 GB NVMe SSD | 2 TB |
| Vultr High Performance AMD 2 GB | Vultr | $12.00 | 1 month | USD per month; billed hourly up to the monthly price | 1 vCPU | 2 GB | 50 GB NVMe SSD | 3 TB |
| DigitalOcean Basic 2 GiB / 2 vCPU | DigitalOcean | $18.00 | 1 month | USD per month equivalent; billing term and prepayment depend on plan | 2 vCPU | 2 GiB | 60 GiB SSD | Not listed |
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 lists for this plan
The plan comes with 2 vCPU, 2 GB of RAM, 65 GB SSD storage and 3 TB of bandwidth. The pricing page places it in the Regular Performance line, described as previous-gen Intel, regular SSD. The other feature listed is a flat monthly price (no intro discount).
Billing is listed as USD per month; billed hourly up to the monthly price. The billing cycle for that monthly cap is 1 month. Because the data marks the renewal price as the same as the initial price, there is no intro discount that ends later; the amount in the price table is the monthly cap from the start.
Who this plan suits
For an agency, a self-managed server in this size range is a common choice for a staging environment or a single client site that needs its own isolated server rather than a shared account. Having 2 vCPU and 2 GB of RAM on a separate instance means one client's build process or plugin update does not compete with another client's production site, which keeps troubleshooting simpler when a ticket comes in.
The hourly model matters for agency workflows: charges build up by the hour up to the monthly price in the table, so a staging server that only exists for part of a month accrues hourly charges up to that cap. The official data does not say what stops, pauses or lowers charges for a server that is stopped or deleted, so confirm that behavior with Vultr before planning short-lived staging servers around it.
The Regular Performance (previous-gen Intel, regular SSD) description suits projects where consistent resources matter more than peak single-core speed, such as a staging copy, a brochure site, or an internal tool. Projects that lean on database-heavy or disk-heavy work may want to compare the NVMe SSD options covered later on this page.
How billing works per client project
The pricing page states USD per month; billed hourly up to the monthly price. In practice that means each server accrues hourly charges, and those charges stop increasing once they reach the monthly price for that server within the 1 month billing cycle. If each client runs on its own server, each server has its own monthly cap, which makes it straightforward to map a cost to a client.
Because the feature list says flat monthly price (no intro discount) and the renewal price is the same as the initial price, the figure an agency quotes to a client does not depend on whether the server is in its first month or a later one. The official data does not mention cost tags, project labels, sub-accounts or invoices split by server, so an agency that needs billing grouped by client should confirm how invoices are presented before moving multiple clients onto the account.
Keeping access and backups organized per client
As a self-managed server, this plan leaves the operating system, web server, updates and access control to the agency. A practical pattern is one server per client project, with a dedicated SSH key pair per project stored in the agency's secrets manager, and a separate deploy user on each server. That way offboarding a contractor or handing a server to a client means rotating one key, not touching every server.
The official data does not confirm whether snapshots, automatic backups, a firewall or team user management are included with this plan, so plan for backups as part of the server itself: a scheduled database export and a file archive written to a location outside the public web folder, then copied off the server to storage the agency controls. Confirm with Vultr which of these account-level tools exist and whether they add to the hourly charges before signing up.
The listed 65 GB SSD is shared between the operating system, site files, local backups and logs, so a per-client retention policy for on-server backups keeps the disk from filling. The 3 TB of bandwidth applies to this server, which is relevant when a staging server is also used to pull large media libraries from a client's existing host.
Alternatives in the same category
Vultr High Frequency 2 GB lists 1 vCPU, 2 GB of RAM, 64 GB NVMe SSD and 2 TB of bandwidth, with the High Frequency (3GHz+ Intel Xeon, NVMe SSD) description. It is billed the same way: USD per month; billed hourly up to the monthly price, with a flat monthly price (no intro discount). It fits a project where NVMe storage and a newer processor matter more than a second vCPU, such as a PHP site whose bottleneck is a single-threaded request path.
Vultr High Performance AMD 2 GB lists 1 vCPU, 2 GB of RAM, 50 GB NVMe SSD and 3 TB of bandwidth, described as High Performance (AMD EPYC, NVMe SSD), again with hourly billing up to the monthly price and a flat monthly price (no intro discount). It suits a client site that benefits from NVMe SSD and matches the 3 TB bandwidth of the Cloud Compute plan, at the cost of less storage and one vCPU.
DigitalOcean Basic 2 GiB lists 2 GiB of RAM and 50 GiB SSD, and DigitalOcean Basic 2 GiB / 2 vCPU lists 2 vCPU, 2 GiB of RAM and 60 GiB SSD. Both carry a Flat monthly price (no intro discount), and their billing is listed as USD per month equivalent, with how it is billed and whether prepayment applies depending on the plan. The official data for these two does not list bandwidth. Because DigitalOcean states memory and storage in GiB and Vultr in GB, this page does not rank those sizes against each other; agencies that already standardize tooling on one provider may find consistency across client servers more useful than small differences in listed resources.
What to check before signing up
Read the price table on this page for the monthly cap and keep in mind that charges accrue hourly toward it. Since there is no intro discount and the renewal price is the same, the table figure is the number to put in a client's hosting line item.
The official data does not list server locations, available operating system images, support options, uptime commitments or IPv6 details, so confirm whichever of these a client project depends on directly with Vultr. For agencies, the items most worth confirming are team or sub-account access, how deleted or stopped servers are charged, and whether backup or snapshot features are available and how they are priced.
Practical setup guide
STEP 1Create the server and record its details in the project file
After signing up, create the server for the client project, choose an operating system image from whatever Vultr offers at the time, and add the project's dedicated SSH public key when creating it. Note the server's public IP address, the client name and the monthly cap from the price table in the agency's project record so the server can always be matched to a client.
STEP 2Harden the server before anything else lives on it
Log in over SSH, apply pending security updates and enable automatic security updates for the operating system. Set up a host firewall that allows SSH, HTTP and HTTPS only, disable password logins for SSH, and create a separate deploy user for the project. The official data does not mention a provider-side firewall, so the host firewall is the one to rely on until that is confirmed.
STEP 3Install the stack and stage the site before touching DNS
Install the web server, PHP and the database, then deploy the client's site files and database to the new server. Test it with a hosts-file override or a temporary subdomain so the client can review it while the live site still runs on the old host. Only move DNS once the staged copy behaves correctly.
STEP 4Point the domain's A/AAAA records at the new server and issue a TLS certificate
Update the domain's A and AAAA records at the DNS provider to the new server's IP address, replacing example.com with the client's domain when checking propagation from a local machine: dig +short A example.com. Once the records resolve to the new server, issue a Let's Encrypt certificate on the server, again replacing the domain placeholders with the client's domain: sudo certbot --nginx -d example.com -d www.example.com. Confirm HTTPS loads and that HTTP redirects to it.
STEP 5Schedule backups and document billing per client
Set up a scheduled database export and a file archive written to a folder outside the public web folder, then copy them off the server to storage the agency controls, since the official data does not confirm provider backups for this plan. Record where the backups go, who holds the SSH keys and the monthly cap for this server in the client's project documentation, so the per-client cost and recovery path are clear to anyone on the team.
Frequently asked questions
Is there an intro discount on Vultr Cloud Compute 2 GB / 2 vCPU?
No. The features list a flat monthly price (no intro discount), and the renewal price is the same as the initial price. The price table on this page shows the monthly cap that hourly charges build toward.
How does hourly billing work for a staging server that only runs part of the month?
The plan is listed as USD per month; billed hourly up to the monthly price, so a server accrues hourly charges until they reach the monthly price within the 1 month billing cycle. The official data does not say what stops or lowers charges for a stopped or deleted server, so confirm that with Vultr before relying on short-lived staging servers to cost less.
Can an agency run several client sites on one of these servers?
Technically yes, since it is a self-managed server with 2 vCPU, 2 GB of RAM and 65 GB SSD, but separating clients onto their own servers keeps access keys, backups and billing tied to one project each. Nothing in the official data limits how many servers an account can run, but account-level limits are not described either, so check with Vultr if a large number of servers is planned.
Does the plan include backups or snapshots?
The official data does not confirm backups, snapshots or a firewall for this plan. Treat backups as the agency's responsibility on the server itself and confirm with Vultr whether account-level backup tools exist and what they cost.
What does Regular Performance mean for this plan?
The pricing page describes the line as Regular Performance (previous-gen Intel, regular SSD). The alternatives listed on this page, Vultr High Frequency 2 GB and Vultr High Performance AMD 2 GB, use NVMe SSD and a different processor description, which is the main distinction between the lines in the official data.
โ Back to the price table and plan link
Found this helpful? Share this article.