Vultr cost guide
★★★★★ 4.5 CE

Vultr Add-on Fees, Discounts & Actual Costs: 2026 Guide

Vultr entry compute is $2.50 a month, but that price is IPv6-only, and a load balancer, DDoS shield or managed database each add real lines. This guide adds up the true cost of a running Vultr setup.

Typical monthly cost

$2.50-$120

Cloud Compute from $2.50 IPv6-only, High Frequency $6, Optimized $28, Bare Metal $120

Hidden fees

Yes

IPv4 adds about $1, a load balancer and DDoS are $10 each, managed databases from $18, backups billed as a percentage

Free tier

None

no free plan; a promotional signup credit only

Cost transparency

Medium

scores 4 of 6 on our transparency checklist

Vultr true cost: cheap instance, paid extras

High· Verified July 15, 2026

Vultr Cloud Compute starts at $2.50 a month as of July 15, 2026, but that price is IPv6-only, so an IPv4 brings it to about $3.50. High Frequency is $6, Optimized $28, and Bare Metal $120. The extras add up: a load balancer and DDoS protection are $10 each, a managed database starts at $18, and block storage from $1. There is no free plan, only a signup credit. Backups bill as a percentage of the instance and bandwidth overage bills separately.

  • Cloud Compute (IPv6)$2.50/mo
  • High Frequency$6/mo
  • Optimized Cloud$28/mo
  • Load balancer$10/mo
  • DDoS protection$10/mo
  • Managed database, from$18/mo
  • Block storage, from$1/mo
Running a larger deployment? The negotiation email generator below drafts a committed-capacity ask with live rival prices from our catalog.
Free tier
None
Hidden fees
IPv4 + add-ons
Cheapest config
IPv6-only
Negotiable
At scale

Vultr's $2.50 Cloud Compute sits far below the $11 median across the 24 cloud-hosting tools we track, though IPv4 and add-ons lift the real entry.

What a running Vultr setup really costs

Vultr's entry price is genuinely low, with a catch built into it. Cloud Compute starts at $2.50 a month, but that figure is IPv6-only; adding an IPv4 address brings it to about $3.50. High Frequency runs $6, Optimized $28, VX1 $43, and Bare Metal $120. Those are the instances. A real deployment is rarely just an instance.

The infrastructure around it adds up fast. A load balancer is $10 a month per instance, DDoS protection another $10, and neither is bundled into compute. Front a single $6 High Frequency node with both and the monthly cost roughly doubles to $26. Extra block storage starts at $1 for 10 GB, and object storage at $5.

Managed services are standalone bills. A managed PostgreSQL or MySQL node starts at $18 a month and climbs to $90 on the Optimized tier, parallel to your web instance rather than part of it. Backups are billed as a percentage of the instance cost, and bandwidth overage past each plan's quota bills separately, both documented in the FAQ rather than the main table. The instance rates and every add-on are on the Vultr plans page. Add the IPv4, storage and any load balancer before you treat the entry price as your bill.

The entry price is IPv6-only

Cloud Compute at $2.50 a month assumes IPv6-only. A routable IPv4 address adds roughly a dollar, bringing the real entry to about $3.50. For any service that needs to be reachable over IPv4, the sticker understates the true starting cost a little.

Load balancer and DDoS are $10 each

A load balancer is $10 a month per instance, or $10 per region for the global variant, and DDoS protection is another $10. Neither is folded into compute, so hardening a single $6 node with both takes its monthly cost to about $26.

Managed databases are a separate node

Managed PostgreSQL or MySQL starts at $18 a month for a 1 GB entry node and reaches $90 on the Optimized General Purpose tier. If your app needs a managed database, that is a standalone bill running parallel to the web instance, not a feature of it.

Backups and bandwidth bill quietly

Automated backups are charged as an added percentage of the instance cost rather than a flat fee, and transfer past each plan's included quota bills at an overage rate. Both live in the FAQ, not the pricing table, so they are easy to miss until the invoice.

Windows and Kubernetes nodes cost more

Choosing a Windows image over Linux adds a license charge to the hourly rate. On Kubernetes the control plane is free, but worker nodes and their storage bill as normal Cloud Compute, so a cluster costs whatever its nodes cost, with the managed layer on top.

Vultr savings that genuinely stick

Vultr has no coupon, and no education or charity pricing on compute. The July 2026 plans and terms put the savings in configuration first, and a sales conversation only at scale. New accounts get a promotional credit, but it expires, so it is a trial rather than a rate.

The everyday levers are structural: stay IPv6-only where you can, right-size the instance, and skip the load balancer until one server genuinely cannot cope. Above steady, larger deployments, Vultr's team can shape committed-capacity terms the console never shows. The negotiation tactics below cover that path, since below it the saving is how you configure the setup, not a published deal.

Promotional signup credit

New accounts get a promotional credit to try the platform for a limited window. It is a one-off, not a standing rate, so use it to validate an instance or a managed database before you commit, and expect billing at list once it runs out.

IPv6-only and right-sizing

The cheapest configuration is an IPv6-only instance sized to real load. Skipping the IPv4 and matching the tier to the workload keeps a node near its $2.50 floor, which is a standing saving you control at deploy time rather than a discount to request.

Committed capacity at scale

Larger, steady deployments can ask Vultr's sales team about committed-capacity terms. A meaningful monthly spend and a rival quote give the conversation a number, and that is where a heavy Vultr account finds pricing the self-serve console does not offer.

No compute coupon or student rate

Vultr publishes no student, nonprofit or promotional discount on compute as of July 2026. The savings are configuration and, at scale, committed capacity, so any site advertising a standing Vultr coupon is selling noise rather than a real rate.

How to keep a Vultr bill lean

There is little to negotiate on a single instance, so the first savings are configuration choices you make at deploy time. Skip the IPv4 where you can, right-size the tier, and add the load balancer and DDoS shield only when the workload truly needs them. All three stick without a conversation.

A sales discussion opens only on a larger, steady deployment, where committed capacity is on the table. A rival quote gives it a number. Four moves cover the ground from a padded Vultr bill to a lean one.

Stay IPv6-only and right-size

Target
Any compatible service
Argument
The $2.50 entry assumes IPv6-only, so services that do not need a routable IPv4 run cheaper without one. Match the instance to real load rather than over-provisioning, since the jump to the next tier is a real step up in cost.
Expected discountholds the floor

Add the balancer and shield only when needed

Target
Small deployments
Argument
A load balancer and DDoS protection are $10 each, so adding both to a $6 node roughly doubles its cost. A single right-sized instance often removes the need for a balancer, and DDoS is worth adding only when the threat is real.
Expected discountavoids $20/mo

Match storage and database tiers to the job

Target
Data-backed apps
Argument
Managed databases run $18 to $90 by tier, and block storage from $1. Pick the smallest that fits rather than the safest-looking size, and confirm a managed database is doing real work before you pay for a standalone node parallel to your instance.
Expected discountremoves over-provision

Ask about committed capacity at scale

Target
Large steady deployments
Argument
For a meaningful monthly spend, ask Vultr's sales team about committed-capacity terms. Bring a Hetzner or Linode figure and your steady usage, and treat the first number as a starting point rather than a fixed rate.
Expected discountnegotiated

When a Vultr choice or negotiation counts

For a single instance, timing is about your own configuration, since the rate is fixed and self-serve. Decide on IPv4, region and tier at deploy time, when they are cheapest to set. On a larger deployment the usual quarter-end pressure applies, so a committed-capacity conversation lands best in a quarter's final weeks.

Jan

 

Feb

 

Mar

Q-END

Apr

 

May

 

Jun

Q-END

Jul

 

Aug

 

Sep

Q-END

Oct

 

Nov

 

Dec

Q-END

Pro tip: Set the configuration deliberately at launch. The IPv4, the region and the instance line all cost more to change once a service is live, so the cheapest Vultr decision is usually the one you get right the first time.

Where you can save on Vultr, and where you cannot

On a single instance there is nothing to negotiate, so the levers are your configuration. What bends is the setup you choose; what holds is the published per-resource price.

Usually negotiable

  • IPv4 versus IPv6-onlyHIGH
  • Instance tier sizingHIGH
  • Committed capacity on a large deploymentMEDIUM
  • Storage and database tier choiceMEDIUM
  • Support terms at scaleLOW

Rarely negotiable

  • The published Cloud Compute list prices
  • The $10 load balancer and DDoS fees
  • The managed database tier prices
  • The backup percentage on the instance

Vultr negotiation email generator

Enter your details and the tool writes a message you can send unchanged, each rival price sourced from the ComparEdge catalog. Give it your instances and monthly usage, then route the draft to Vultr's sales contact. Describe the deployment, name a cheaper cloud, ask about committed capacity, and set a date for the decision.

What you are buying

steady deployment at a negotiated rate

Team size
Decision deadline
Contract length
SubjectVultr Pricing Discussion - [Your company]
Hi Vultr team,

I lead tooling decisions at [Your company], and we are evaluating Vultr Team seats for a team of 10-50 people.

As part of this evaluation we are also looking at Hetzner, which comes in at $4.49/mo, and Linode at $5/mo. Can you help us understand the value difference at your current rates?

We are ready to commit to an annual term. What is the best rate you can offer on annual billing, and can you cap the renewal price in the contract?

We are aiming to sign before the end of this quarter, and budget sign-off is already in place.

Could you share a proposal covering the per-seat or per-credit rate, the renewal terms, and any programs we qualify for?

Best regards,
[Your name]
[Your company]

Send it Tuesday to Thursday, and follow up once after 3 business days.

Before you send

  • Total your instances, storage and add-ons first, so the ask reflects real spend.
  • Separate steady capacity from bursty usage, since only the steady part is worth committing.
  • Write to Vultr sales for a larger deployment, not the general support queue.
  • Bring one rival price so the ask has a number to anchor on.
  • Ask about committed capacity and support terms in a single message.
  • Follow up once after a few business days, then read the quiet as a no.

Vultr billing mistakes worth avoiding

Each of these comes from reading a Vultr instance price as the all-in cost. All of them are simple to avoid at deploy time.

Reading the $2.50 entry as final when it is IPv6-only and an IPv4 adds about a dollar..

Adding a $10 load balancer and $10 DDoS shield to a small node that does not need them..

Spinning up a managed database at $18 to $90 when the app could run its own on the instance..

Ignoring the backup percentage and bandwidth overage buried in the FAQ, not the price table..

Choosing a Windows image without noticing the license charge added to the hourly rate..

Assuming a Kubernetes cluster is cheap because the control plane is free, when nodes bill normally..

Vultr rivals that sharpen a comparison

A cheaper rival with a real figure gives a comparison teeth. The three here price near Vultr, each number from the ComparEdge catalog. They trade regions, included traffic or management, which is the axis you actually weigh. The wider set is on the Vultr alternatives page.

Is Vultr worth it? The honest read

Vultr is strong value for a global developer cloud, and the $2.50 entry is a real number for the right workload. The regional footprint is wide, and the instance line is competitive. What the sticker hides is that a production setup is instance plus IPv4 plus the balancer, shield, storage and database it needs, and each is a separate line.

So read the entry price as the compute, not the setup. Stay IPv6-only where you can, right-size the tier, and add the load balancer, DDoS shield and managed database only when the workload truly calls for them. Watch the backup percentage and bandwidth overage tucked into the FAQ.

Handled that way, Vultr is a cheap, flexible cloud with genuine global reach. Bolt on every add-on by default and a $2.50 instance quietly becomes $30. Vultr's per-resource rates sit on the Vultr plans page. This guide is about stopping the add-ons from padding a cheap instance.

Vultr pricing and discount FAQ

How much does a Vultr instance cost?

+

The entry Cloud Compute instance is $2.50 a month, but that price is IPv6-only, so adding a routable IPv4 brings it to about $3.50. High Frequency Cloud Compute is $6, Optimized $28, VX1 $43, and Bare Metal $120. Those are the instances alone. A real deployment usually adds a load balancer at $10, DDoS protection at $10, storage from $1, or a managed database from $18, each a separate line. So the true cost of a running Vultr setup is the instance plus whatever infrastructure it needs, not the $2.50 headline.

Does Vultr charge extra for IPv4?

+

Yes. The cheapest Cloud Compute price of $2.50 a month assumes an IPv6-only instance. A public IPv4 address is a small additional charge, roughly a dollar a month, that brings the real entry cost to about $3.50. IPv4 addresses are scarce, so Vultr, like several budget clouds, prices them separately rather than folding them into the base rate. For any service that must be reachable over IPv4, budget the extra. Internal nodes, or services reached through an IPv6-capable proxy, do not need one, so leaving it off holds the instance at its cheapest rate.

What add-ons drive up a Vultr bill?

+

The infrastructure around the instance. A load balancer is $10 a month and DDoS protection another $10, so hardening a small node with both roughly doubles its cost. A managed PostgreSQL or MySQL database runs $18 to $90 by tier, parallel to your web instance. Block storage starts at $1 and object storage at $5. Backups are billed as a percentage of the instance cost, and bandwidth past each plan's quota bills as overage. None of these are folded into compute, so a cheap instance with real infrastructure behind it lands well above the entry price.

What do Vultr managed databases cost?

+

A managed database on Vultr starts at $18 a month for a 1 GB entry node and climbs to $90 on the Optimized General Purpose tier, supporting PostgreSQL and MySQL. It is billed as a standalone node running alongside your compute. An app with a web server and a managed database therefore pays for both separately, not as one line. If cost matters more than convenience, running your own database on the compute instance avoids the managed line, at the price of handling backups, updates and failover yourself. Pick the smallest managed tier that meets your needs.

Does Vultr include any free plan?

+

No. Vultr has no free tier; billing starts when you deploy a resource. New accounts sometimes receive a promotional signup credit to trial the platform, but that is a one-off with an expiry date rather than a standing free plan. Because entry compute is only $2.50 a month, the smallest instance is an inexpensive way to trial Vultr, though billing begins immediately. To prototype at no cost, a platform that offers a real free tier is the better fit. Vultr competes on low prices, not a free option.

How does Vultr bill bandwidth and backups?

+

Both sit in the FAQ rather than the main pricing table, which is why they surprise people. Each plan includes a monthly transfer quota, and traffic past it bills at an overage rate per GB. Automated backups are charged as an added percentage of the instance cost rather than a flat fee, so a larger instance pays more to back up. Neither is folded into the headline compute price. The practical move is to check your plan's included transfer, cache and offload heavy assets to stay inside it, and weigh whether automated backups or your own routine is cheaper.

Can you get a discount from Vultr?

+

On a single instance, not really; the per-resource prices are fixed and self-serve. New accounts get a promotional signup credit, but it expires. The genuine savings are configuration: stay IPv6-only, right-size the tier, and skip add-ons you do not need. At a larger, steady scale, Vultr's sales team can discuss committed-capacity terms, which is where a meaningful monthly spend and a rival quote give you leverage. There is no published coupon or education rate, so below the sales threshold the way to pay less is how you build the setup, not a discount code.

What keeps a Vultr bill lowest?

+

Run IPv6-only wherever a routable IPv4 is not needed, and right-size the instance to real load rather than buying headroom. Add a load balancer or DDoS protection only when the workload genuinely requires them, since each is $10 a month. Pick the smallest managed database tier that fits, or run your own on the instance. Watch the backup percentage and stay inside your transfer quota to avoid overage. For a large deployment, ask sales about committed capacity. Stacked, those choices keep a Vultr setup near its genuine floor rather than padded by extras.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs and official pages
SourceWhat was checkedLast checked
Vultr official pricingVerified plan prices, renewal rates and credit allowancesJuly 15, 2026
Vultr websiteOfficial vendor websiteJuly 15, 2026
Vultr pricing on ComparEdgeCurrent prices for every plan, with the cost calculatorJuly 15, 2026

Every fact on this Vultr pricing page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.