Amazon Web Services vs Vultr

Amazon Web Services and Vultr sell the same thing at the bottom of their menus: a virtual machine with root access, a transfer allowance and nobody else responsible for what runs on it. The choice between them is a billing unit and a growth path, not a service. For a small site or PHP application the comparison that matters is Lightsail, the AWS bundle menu, against Vultr's Cloud Compute tiers: the two ladders such a project climbs.

The units differ before the prices do, and the units are the story: monthly bundles on one side, hourly rates on the other. The audit table holds the numbers; the argument here is shape and fit.

Two menus priced in different units

Every Lightsail bundle is a monthly number: $5 buys 0.5 GB of memory, 2 vCPUs, 20 GB of SSD and 1 TB of transfer, and the Linux line climbs to a published $1,764 a month at 256 GB. The captured pricing page states no hourly rate for any bundle. Vultr runs the opposite convention, pairing each tier with an hourly figure down to $0.004 and billing only for the hours an instance is active.

VX1 sharpens the contrast: its 2 vCPU, 8 GB entry tier is published at $0.060 an hour with no monthly price on the pricing page, the product page separately calls $43.80 a month the starting point, and the line is billed on actual hours used, uncapped at 672. AWS's own hourly product, EC2, bills by the hour or second, but its captured page renders no per-instance prices. On hourly billing, Lightsail omits and Vultr commits.

The floor sits lower at Vultr

Vultr's entry tiers are $2.50 and $3.50 a month (checked November 2026): the first is published as IPv6 only, the second carries a public IPv4 address, and both hold 1 vCPU, 0.5 GB of memory, 10 GB of disk and 0.50 TB of transfer. Lightsail's IPv4 bundles start at $5, doubling the disk and transfer of Vultr's floor and folding in a static IP address, DNS management and monitoring. Lightsail also publishes an IPv6-only line from $3.50, which produces the tidiest fact on the page: at $3.50, Vultr's tier includes IPv4 and AWS's does not.

Two footnotes keep that honest. Vultr's product page calls $5 the starting price while its own pricing page lists two cheaper tiers beneath it. And at an equal $5 the lead swaps: Vultr carries 1 GB of memory and 25 GB of disk, Lightsail 0.5 GB and 20 GB on two vCPUs. The cheaper floor depends on which specification runs out first.

Add-on economics at both ends of the bill

Vultr prices its protection as percentages and flat fees: automatic backups raise an instance's base fee by 20%, DDoS protection adds 10Gbps of mitigation capacity per instance at $10 a month on top of baseline layer 3 and 4 shielding stated as included, and the CDN starts at $1 a month. Snapshots cost $0.05 per GB per month, the one identical number in this pairing; Lightsail's snapshots carry exactly the same rate.

Lightsail prices attachments as products instead: a load balancer at $18 a month with certificates managed, managed MySQL or PostgreSQL from $15, CDN from $2.50, object storage from $1. The philosophies invert at the top of the bill: AWS prices support itself, from Basic included to Unified Operations at a $50,000 a month minimum. Vultr publishes no priced support tier at all.

Transfer overage is where similar bills cross: Vultr charges $0.01 per GB beyond the quota, while Lightsail's worked example charges $0.09 per GB in US East (Ohio), and six regions grant half the stated allowances. A workload that regularly exceeds its allowance should treat that gap as the decision.

Support: one tier against a ladder

Vultr's support is a single included tier: tickets through the account portal, chat and ticket cover around the clock from what the product page calls a global team of certified engineers. No response times are stated, no phone channel appears in the captures, and enterprise support is a contact-sales line with nothing itemised. AWS sells the same function in slices: Basic is included, Business Support+ starts at $29 a month or tiered percentages of the bill, Enterprise at $5,000, Unified Operations at $50,000. Neither capture itemises channels per tier; only AWS's paid Incident Detection service commits to anything as specific as a 5-minute response.

Region counts neither side reconciles

Vultr's own pages give three answers: 33 cloud data centre regions on the product page list, 36 in the site navigation, 20 countries and 34 cities in the pricing metadata, London and Manchester among them. AWS's captures name 19 regions in a single overage table, including a priced London region, but state no figure for the Lightsail footprint itself. This article asserts neither count, because the sources disagree on one side and fall short on the other.

What neither of them manages

Above the hypervisor, both platforms are equally your job, and the captured pages say so differently. Vultr's FAQ states that customers are responsible for most aspects of server management, including software installation, configuration and maintenance. Lightsail simply omits the question: WordPress appears as a click-to-launch blueprint rather than a managed service, with no automatic updates, no patching and no statement of where AWS's responsibility ends. Vultr's WordPress is one of 100+ Marketplace apps, no more managed.

The shared gaps stack up symmetrically: no staging environment in either capture, no migration service, no stated backup retention on either side, though both sell the backups, Vultr at 20% of the instance fee and AWS at $0.05 per GB. Vultr publishes a 99.99% uptime figure, vendor-stated with no compensation terms captured; AWS publishes none. Growth paths diverge: Vultr states instances can be resized after deployment, while Lightsail's only stated route upward is a snapshot exported to EC2, which doubles as the door to the 90+ AWS services behind VPC peering.

Where each one wins

Vultr for machines that live briefly or unpredictably: hourly billing from $0.004, a $2.50 floor for an IPv6-reachable experiment, and a stated resize path. Lightsail for the always-on site that wants one flat monthly number with the address, DNS and monitoring inside it, and for projects whose growth ends somewhere in the wider AWS catalogue. Neither is for the buyer who wanted managed WordPress hosting; that buyer is a shelf away, and Cloudways vs AWS and Cloudways vs Vultr cover the managed alternative to each. The hosting comparison tool puts both against the rest of the audited field on identical citation rules.