Vultr High Performance AMD 1 GB: Hourly Billing, NVMe SSD

Plan details (official data)

Inclusions and features (official data)

• High Performance (AMD EPYC, NVMe SSD)
• flat monthly price (no intro discount)

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)

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 11, 2026; every compared plan was checked within the last 60 days.

What the official data lists for this plan

The resources on the official pricing page are 1 vCPU, 1 GB of RAM, 25 GB NVMe SSD storage and 2 TB of bandwidth. The plan sits in Vultr's Cloud VPS category and carries the feature label High Performance (AMD EPYC, NVMe SSD), which is the hardware tier the provider lists for it.

The second feature in the data is flat monthly price (no intro discount). Combined with the billing field, USD per month; billed hourly up to the monthly price, this means the monthly figure in the table is a cap on hourly charges rather than a discounted first payment that later changes. The term is listed as 1 month, which is the billing cycle of that monthly cap.

Because this is a self-managed server, the operating system, web server, updates, firewall and backups are the responsibility of whoever runs it. The official data does not list operating system choices, server locations, IPv6 availability, a control panel or support channels, so a developer who depends on any of those should confirm them with Vultr before creating the server.

How hourly billing up to the monthly price works

The billing field reads USD per month; billed hourly up to the monthly price. In plain terms, charges build up hour by hour while the server exists in the account, and they stop growing once they reach the monthly price shown in the table. A server that exists for part of a month is charged for the hours it was there rather than for the full month.

The renewal price in the data is the same as the first-term price, so there is no introductory rate that ends and no step up after the first month. The flat monthly price (no intro discount) feature describes the cap, not a fixed charge taken on a set day; the hourly billing field is what determines how the amount is reached.

The official data does not state whether a powered-off server keeps accruing charges or what action, if any, ends them. Developers who plan to create and remove servers for short experiments should confirm that with Vultr rather than assume that stopping a server stops the meter.

Who this plan suits

The plan fits a developer who wants a small, self-managed server for a side project or a small API and who is comfortable administering a Linux box over SSH. With 1 vCPU and 1 GB of RAM, it is sized for a single lightweight application such as a Node, Go, Python or PHP service behind Nginx, a small database on the same machine, or a staging copy of a larger project.

The 25 GB NVMe SSD gives room for the operating system, application code, logs and a modest database, while 2 TB of bandwidth is generous for an API or a small site with moderate traffic. The hourly billing model also suits short-lived test servers, provided the reader confirms with Vultr how charges behave for servers that are stopped or destroyed.

It is a weaker fit for anyone who wants the provider to patch the operating system, manage backups or tune the web server for them. Nothing in the features mentions managed services, so a reader who wants hands-off hosting should look at a managed product rather than a Cloud VPS.

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

SSH is how a developer logs in to a Cloud VPS, deploys code and reads logs. After the server is created, a sensible first job is to add an SSH key, disable password logins and use a non-root user with sudo for day-to-day work, keeping root for recovery only.

Security updates are the developer's responsibility on a self-managed server. Most Linux distributions can apply security patches automatically, and turning that on early removes one recurring chore. Application dependencies and the runtime are separate and still need a manual update routine.

A host-based firewall should allow SSH, HTTP and HTTPS and block everything else by default, with the database and any internal services reachable only from localhost. The official data does not mention a provider-side firewall, so plan on configuring one on the server itself and confirm with Vultr whether a network-level option exists.

Backups are not listed in the features, so the official data does not confirm whether snapshots or automatic backups are included. A developer should assume they must set up their own routine, such as a nightly database dump copied off the server, and verify with Vultr what the platform offers before relying on it.

How it compares with the alternatives

Vultr Cloud Compute 1 GB lists the same 1 vCPU and 1 GB of RAM and the same billing field, USD per month; billed hourly up to the monthly price, with a renewal price that is the same as the intro price. Its feature label is Regular Performance (previous-gen Intel, regular SSD), it lists 25 GB SSD rather than NVMe, and its bandwidth is 1 TB instead of 2 TB. It suits a developer who wants a Vultr server with the same billing style but does not need the High Performance hardware tier or the higher transfer allowance.

Vultr High Frequency 1 GB also lists 1 vCPU, 1 GB of RAM and hourly billing up to the monthly price with the same renewal price. Its feature label is High Frequency (3GHz+ Intel Xeon, NVMe SSD), it lists 32 GB NVMe SSD and 1 TB of bandwidth. It fits a developer who values more local storage over the larger bandwidth of the High Performance AMD plan; the data does not say which processor tier is faster for a given workload.

DigitalOcean Basic 1 GiB lists 1 GiB of RAM and 25 GiB SSD with a flat monthly price (no intro discount) and a renewal price that is the same as the intro price. Its billing field reads USD per month equivalent; billing term and prepayment depend on plan, which is a different billing description from Vultr's hourly cap. The official data does not list CPU or bandwidth for it, and because its RAM and storage use GiB rather than GB, no size comparison is drawn here.

DigitalOcean Basic 512 MiB lists 512 MiB of RAM and 10 GiB SSD with the same flat monthly price (no intro discount) feature and the same billing description as the other DigitalOcean plan. It suits very small services where memory needs are low, while a developer running a database alongside an API is more likely to want one of the plans listing 1 GB or 1 GiB of RAM.

What to check before signing up

Read the billing field as written: USD per month; billed hourly up to the monthly price. The price in the table is the most that accrues within the 1 month billing cycle, and the renewal price is the same as the first-term price, so there is no later change to budget for.

Confirm with Vultr the items the official data does not cover: which operating systems and regions are available, whether IPv6 is included, whether snapshots or automatic backups exist and whether they cost extra, whether a network firewall is available, and how charges behave for a stopped server.

Check that 1 vCPU, 1 GB of RAM and 25 GB NVMe SSD match the application's needs, especially if a database and a web server will share the machine. The 2 TB bandwidth is plentiful for most side projects, but a developer serving large downloads or media should estimate monthly transfer before choosing.