Shared price advantage vs workload-specific tradeoffs
Vultr vs Linode: Which Compute Model Fits?
Vultr and Linode both sell hourly cloud servers, but a useful decision starts with the CPU class, not a provider score. Current API snapshots favor Vultr on the compared small shared plans and Linode on one established dedicated plan. Billing exceptions, backups, transfer, and regional prices can reverse the final total.
Prices and provider rules checked on October 24, 2026.
Short answer
Choose the plan family before the provider
Start with Vultr when
You need a small shared CPU instance and the current default API price matters. The compared Vultr 2 GB and 4 GB Cloud Compute plans cost less than the equivalent Linode Shared CPU examples, while exposing hourly rates and monthly caps.
Start with Linode when
You need an established dedicated CPU plan and its resource mix fits. In the current snapshots, the Linode G6 Dedicated 4 GB example has a lower monthly cap, more disk, and a slightly lower hourly rate than the compared Vultr Optimized plan.
Do not generalize this into a universal winner. Availability and regional pricing differ, and Linode G8 Dedicated plans use hourly-only pricing with no included transfer. Confirm the exact region and plan generation before purchase.
These are commercial links. VPSchart may receive compensation if you use them, without changing your price. The comparison uses the cited provider APIs and documentation, not commission size.
Shared CPU price snapshot
The table uses the default values returned by both public APIs on October 24, 2026. Vultr identifies these as Cloud Compute plans. Akamai identifies the Linode examples as Shared CPU. The figures are a dated planning reference, not a promise that every region or account sees the same offer.
| API plan | vCPU and RAM | Storage | Included transfer | Hourly | Monthly cap |
|---|---|---|---|---|---|
| Vultr vc2-1c-2gb | 1 shared vCPU, 2 GB | 55 GB | 2,048 GB | $0.014 | $10 |
| Linode g6-standard-1 | 1 shared vCPU, 2 GB | 50 GB | 2,000 GB | $0.018 | $12 |
| Vultr vc2-2c-4gb | 2 shared vCPU, 4 GB | 80 GB | 3,072 GB | $0.027 | $20 |
| Linode g6-standard-2 | 2 shared vCPU, 4 GB | 80 GB | 4,000 GB | $0.036 | $24 |
Regional warning: The Linode API returned higher prices for these plans in Jakarta and São Paulo. Compare the actual deployment region rather than multiplying the default hourly rate yourself.
Dedicated CPU changes the comparison
A shared plan can experience contention because processor time is shared with other guests. A dedicated plan reserves the assigned cores. That distinction matters for sustained compilation, busy databases, game servers, media processing, and other CPU-sensitive work.
| API plan | vCPU and RAM | Storage | Included transfer | Hourly | Monthly cap |
|---|---|---|---|---|---|
| Vultr voc-c-2c-4gb-50s-amd | 2 dedicated vCPU, 4 GB | 50 GB | 5,120 GB | $0.055 | $40 |
| Linode g6-dedicated-2 | 2 dedicated vCPU, 4 GB | 80 GB | 4,000 GB | $0.054 | $36 |
| Linode g8-dedicated-4-2 | 2 dedicated vCPU, 4 GB | 41 GB | None | $0.070 | No monthly cap |
The G8 example is not a direct replacement for the G6 plan. Akamai states that G8 Dedicated services bill for actual hours without a monthly cap, and the API reports no included transfer. Treat the plan generation as a contract change, not a routine upgrade.
Billing rules that affect the real total
Vultr cost basket
- Selected Shared CPU or Optimized Cloud Compute instance
- Hourly billing with a 672-hour monthly cap for the compared non-GPU server classes
- Continued server billing while the instance exists, even when powered off
- Automatic backups at 20 percent of the instance base fee if enabled
- Outbound transfer beyond the selected plan allowance
Linode cost basket
- Selected Shared CPU or Dedicated CPU instance and its regional price
- Hourly billing up to a monthly cap for most plans, with documented exceptions
- Continued billing for allocated services while powered off
- Optional Linode Backups fee for the selected plan
- Transfer overages, regional pools, and G8 transfer charges where applicable
Deletion is the billing boundary. Powering off a server does not release its reserved resources. Before deletion, export any data you need and identify attached storage, IP addresses, snapshots, or other separately billed items.
Backup retention is not equivalent
Vultr automatic backups retain the two most recent backups and can run daily, every other day, weekly, or monthly. The service captures the active instance file system but excludes attached Block Storage. Vultr also warns that the capture resembles a non-graceful restart for consistency purposes.
Linode Backups stores automatic daily, weekly, and biweekly backups plus one manual snapshot. Akamai documents the service as a paid add-on and stores the backups in the same data center as the Linode. Block Storage volumes are not part of a Linode backup.
For either provider, use application-aware database dumps or replication where needed, keep an independent copy outside the provider account, and test a restore. A provider snapshot alone is not a disaster-recovery plan.
Transfer requires a region and plan check
Vultr meters outbound internet transfer against the plan allowance and leaves inbound traffic unmetered. Linode uses transfer pools and documents region-specific handling and overage rates. The G8 Dedicated example above has no included transfer, so traffic cost must be modeled separately.
Estimate outbound delivery from backups, media, package mirrors, downloads, replication, and user traffic. A plan with a lower compute price can cost more once its transfer contract is applied.
Match the server to the workload
Low-traffic sites and development environments
Start with shared CPU when the workload is bursty and can tolerate variable processor availability. The current small-plan snapshots give Vultr a lower default compute price, while the Linode 4 GB example includes more transfer. Deploy in the required region and observe CPU contention, memory pressure, disk use, and transfer before scaling.
Sustained CPU workloads
Price the dedicated families separately. The compared Linode G6 Dedicated plan is cheaper than the Vultr Optimized example, but Vultr includes more transfer while Linode includes more disk. Those differences matter more than a provider-wide score. Run the actual job on both if a few dollars are less important than predictable completion time.
Long-running public services
Add backup retention, outbound traffic, monitoring, security updates, public addressing, and recovery time to the monthly basket. Neither provider's infrastructure turns an unmanaged server into a managed application.
Migration checklist between Vultr and Linode
- Inventory the service. Record ports, DNS, certificates, databases, scheduled jobs, volumes, mail delivery, firewall rules, and external allow lists.
- Create the target independently. Choose the CPU class, region, storage, operating system, network settings, and backup option without assuming the old provider's plan maps directly.
- Move data safely. Use an application-aware database export or replication method, then copy persistent files and secrets through a secure channel.
- Test before cutover. Validate the site, background workers, outbound mail, TLS, monitoring, backups, and restore procedure against the new address.
- Switch with a rollback window. Lower DNS TTL in advance, perform the final sync, change traffic, and keep the source available until production checks pass.
- Remove old resources deliberately. Delete the old server and separately billed storage, addresses, snapshots, or backups only after the rollback period.
Make the decision in five questions
- Is the workload bursty enough for shared CPU, or does it need reserved cores?
- Which exact region serves users and meets legal or latency requirements?
- How much outbound transfer will the service and its backups generate?
- What backup retention, database consistency, and off-provider copy are required?
- Will this plan use a monthly cap, regional price, or hourly-only billing exception?
For a small shared instance, check Vultr first against the current Linode regional price. For sustained CPU, compare the dedicated families as separate products. Do not move production until the target has passed a workload test and restore check.
Frequently Asked Questions
Is Vultr or Linode cheaper?
It depends on the plan class. In the public API snapshots checked on October 24, 2026, Vultr had the lower default price for the compared 2 GB and 4 GB shared CPU plans. The compared Linode G6 Dedicated 4 GB plan cost less than the Vultr Optimized Cloud Compute 4 GB example. Region-specific prices, taxes, backups, transfer overages, and other resources can change the total.
Should I choose shared or dedicated CPU?
Shared CPU is the economical starting point for bursty websites, development environments, and services that do not need steady processor time. Choose a dedicated CPU class when sustained or latency-sensitive work justifies paying for reserved cores. Measure your own workload before moving production.
Does stopping a Vultr or Linode server stop billing?
No. Both providers state that an allocated service continues to incur charges when it is powered off. Delete the server and any separately billed resources when you no longer need them, after confirming that your backups and rollback plan are complete.
Are backups included with Vultr or Linode?
Treat backups as a paid add-on for the plans compared here. Vultr prices automatic backups at 20 percent of the instance base fee and keeps the two most recent backups. Linode Backups stores daily, weekly, and biweekly backups plus one manual snapshot. Both providers document exclusions, and neither service replaces an independent off-provider backup.
Can I migrate between Vultr and Linode?
Yes, but provider snapshots are not a portable migration format. Build the target server, move application data with an application-aware method, test services and TLS, switch DNS, and keep the old server until production checks and a rollback window are complete.
Official sources
Checked October 24, 2026. APIs, plans, regions, prices, and provider terms can change after this date.
- Vultr Plans API: current plan IDs, resources, transfer, hourly prices, and monthly caps.
- Linode Types API: current plan classes, resources, transfer, default prices, and regional prices.
- Vultr Cloud Compute provisioning: Shared CPU positioning, plan families, storage, and networking choices.
- Akamai Cloud shared and dedicated CPU guide: contention, sustained CPU use, and plan-selection guidance.
- Vultr server billing: hourly billing, 672-hour non-GPU cap, and stopped-server charges.
- Akamai Cloud billing: hourly billing, monthly caps, powered-off services, and G8 exceptions.
- Vultr automatic backups: 20 percent fee, two retained backups, schedules, and exclusions.
- Linode Backups: retention slots, same-data-center storage, snapshots, and exclusions.
- Vultr bandwidth calculation: metered outbound and unmetered inbound transfer.
- Akamai Cloud network transfer: transfer pools, allowances, regional treatment, and overages.