What do you like best about Vultr?
Performance: The Raw Power Advantage
The first thing I noticed was the sheer speed. With many providers we’ve used in the past, performance often felt throttled or tied to older hardware; Vultr, by contrast, feels built for high-stakes environments.
Our Experience: We moved our database-heavy applications to their High-Frequency Compute nodes (utilizing 3GHz+ AMD EPYC™ processors).
The Result: We saw an immediate 30% reduction in page load times. The NVMe storage they provide isn’t just a marketing buzzword—it delivers the IOPS we need for real-time data processing, without the “noisy neighbor” lag we ran into on other platforms.
AI / Intelligence: Fueling Our Growth
As our company started integrating more machine learning models, I was concerned about the costs of GPU instances skyrocketing.
What I Like: Vultr makes high-end hardware like the NVIDIA B200 accessible.
The Benefit to Us: We don’t have to commit to massive three-year contracts just to get a seat at the table. Their Kubernetes (VKE) integration with GPU nodes let our team spin up training environments in minutes, and that has been a game-changer for our internal AI development.
UI / UX: Clean and Efficient
I’ve spent far too many hours of my life lost in the “maze” of the AWS Management Console.
Our Take: Vultr’s UI is a breath of fresh air—remarkably flat and intuitive. I can hand the dashboard to a junior engineer, and they can have a global load balancer configured in ten minutes without needing a certification.
Global Footprint: With 32+ locations, we’ve been able to deploy our services physically closer to our clients in London, Tokyo, and Sydney, all through one unified, simple interface.
Pricing / ROI: No More “Bill Shock”
The biggest win for our bottom line has been predictability.
The Problem: In the past, our monthly cloud bill felt like a guessing game because of complex “egress” and “API request” fees.
The Solution: Vultr’s flat pricing model is transparent. We now save roughly 40% monthly compared to our previous hyperscaler setup. The ROI isn’t only in the lower price point; it’s also in the hours our finance team saves by not having to audit a 50-page invoice every month.
Integrations: Developer-First Architecture
We’re an “Infrastructure-as-Code” shop, so integrations are vital to our workflow.
Our Workflow: We use the Vultr Terraform provider to automate our entire stack, and it works flawlessly.
What’s Missing: If you’re looking for a “one-click” marketplace for every obscure business app, you won’t find it here. Vultr provides the “bricks,” but we still had to do a bit more of the “building” ourselves.
Support / Onboarding: The High-Skill Barrier
If I have one major “dislike,” it’s the support model.
The Reality: This is a self-service platform. During onboarding, I realized there’s no “account manager” to call, and support is strictly ticket-based.
The Risk: Their technical team is knowledgeable, but the lack of immediate phone support means our own team has to be the first line of defense. If you don’t have a solid internal technical lead, the onboarding process may feel a bit “sink or swim.” Review collected by and hosted on G2.com.
What do you dislike about Vultr?
1. The “Guilty by Association” Risk (Account Linking)
This is probably my biggest gripe when doing agency work: Vultr’s fraud detection feels incredibly aggressive.
The problem is that if you’re invited to manage a client’s account and that client later has a payment failure or a TOS violation, Vultr’s automated systems can end up flagging every account linked to that user.
My concern is that I’ve seen situations where a consultant’s personal account was suspended simply because one of their clients’ credit cards expired. It comes across as a “scorched earth” approach to security, and it can put our entire operation at risk because of a third party’s mistake.
2. Rigid “Ticket-Only” Support
When you’re running a mission-critical B2B service, live chat or a phone number isn’t a luxury—it’s a necessity.
The reality is that Vultr sticks strictly to an email-based ticketing system. They’re usually responsive (often within 1–2 hours), but it still lacks the immediacy you need during a production emergency.
There’s also a “script” issue: the first response can sometimes read like a canned template. With complex networking problems, it may take two or three back-and-forth exchanges before you finally reach a senior engineer who truly understands what’s going on.
3. Throttling for “Noisy” Workloads
Vultr is a shared environment (unless you pay for Bare Metal), and they seem very protective of their host nodes.
The issue is that if one of our instances sits at 100% CPU for an extended period—during a heavy data migration, for example, or because of an unoptimized script—Vultr’s automated systems may throttle performance or even suspend the instance to “protect” other users on the same hardware.
For a business, the impact is that it can feel like you’re being punished for using the resources you’re paying for.
4. No Refunds on Credit Balances
Their billing system feels like a “one-way street” when it comes to cash.
What I dislike is that if you deposit $500 into your account and then decide to move the project elsewhere, that money is effectively gone. Vultr generally does not offer refunds on “Account Credit.” It’s an old-school policy that feels a bit “anti-consumer” in an era where flexible cloud billing is the norm.
5. Lack of “Managed” Guardrails
Vultr provides the “raw metal,” but offers almost no help with securing it.
The reality is that, unlike managed providers, Vultr won’t warn you if your firewall is misconfigured or if your OS is out of date. If you get hacked due to a simple oversight, the solution is often just to null-route your IP (take you offline) until you fix it yourself. For a small business without a dedicated sysadmin, that’s a lot of weight to carry. Review collected by and hosted on G2.com.
