VPSTabEvidence-first VPS decisions
Search2026.10.25-v7
Menu
Find a VPSProvidersPlansReviewsCompareUse casesGuidesMethodology
English
English简体中文日本語한국어DeutschFrançaisРусский
Guides

The pre-purchase VPS checklist

A practical checklist for specifications, IPv4/IPv6, backups, contracts and security before you pay for a VPS.

Last reviewedOct 24, 2026 · 1009 words

Before you compare prices

A VPS purchase is a small infrastructure contract. The price matters, but so do the specifications, the location, the recovery path and the terms you are accepting. Start with the workload profile and the hard requirements, then use price as a filter rather than the first sorting key.

Write down the exact plan, region, billing term and add-ons you intend to buy. A vague intention such as “a cheap 4 GB server” is hard to verify and easy to upsell. A precise line item is auditable.

Include the recovery objective in that line item. If the service must be back within an hour, a plan without a tested restore path fails the requirement even if every specification matches. If the data is disposable, spending on backups may be unnecessary. The purchase decision is incomplete until the failure model is explicit.

Specifications and virtualization

Confirm vCPU count, RAM, storage size and storage type, and whether the CPU is shared or dedicated. The same four vCPUs can mean very different things across providers. Check whether the provider publishes the virtualization technology; several plans in this dataset leave it unknown, which is acceptable only if you do not depend on a specific feature such as nested virtualization.

Look for limits that are not in the headline: CPU steal or burst policy, IOPS limits, snapshot count, number of IPv4 addresses, and whether the plan can be resized later. A plan that meets the RAM requirement but cannot be upgraded without a rebuild may still be a poor fit.

Networking and address families

IPv4 and IPv6 are separate facts. A provider may include IPv4 and support IPv6, include IPv4 only, or leave the assignment unknown. Mail servers, some VPNs and legacy clients may need confirmed IPv4; modern dual-stack services may require IPv6. Treat unknown as unknown and verify with the provider.

Check traffic allowance, port speed and what happens after the allowance is exhausted. A generous monthly transfer in one region can be much smaller in another. If your service is media-heavy, calculate the expected egress before choosing a plan, and confirm whether egress is included, metered or subject to a fair-use policy.

Storage, backups and recovery

Check whether storage is included in the plan or billed as a separate block volume. Confirm the storage type and whether snapshots count against the plan or are billed separately. A plan with a low instance price and an uncaptured storage bill is not a complete price.

For backups, ask three questions: what is backed up, how long is it retained, and how do you restore it? A provider backup is useful only if you can restore the whole service, not just a file. If recovery is critical, keep an independent copy outside the provider and test a restore before you need it.

Contract, tax and renewal

Read the billing term, promotion conditions, renewal price, cancellation window and refund policy. A twelve-month or two-year commitment can lower the monthly price but increases the cost of changing your mind. Check whether the promotional price applies to the whole term or only the first few months.

Confirm tax treatment. Some prices include VAT, some exclude it, and some leave it unstated. If you can reclaim tax, the comparison changes. If you cannot, an apparently cheaper price may be more expensive after tax. Record the currency and the exchange-rate date if you are comparing across currencies.

Security and operations

Before the first boot, decide how you will authenticate (SSH keys, not reused passwords), which ports will be exposed, how the firewall will be configured, and how operating-system updates will be applied. A cheap VPS with an open administrative port and no backup is an expensive incident waiting to happen.

Plan monitoring and recovery as part of the purchase. Know how you will detect downtime, how you will access the console if SSH fails, where logs will live and who will respond. A provider's snapshot is not a monitoring system, and a status page is not an incident report for your service.

A final verification pass

Before paying, repeat the check on the exact order form. Confirm the plan name, region, billing period, renewal price, tax display and add-ons. A pricing page can show a “from” price for a different term or configuration; the order form is the one that matters. If the order form contradicts the page, stop and resolve the difference.

Save a copy of the confirmed terms and the date. When the first invoice arrives, compare it with the worksheet. If the renewal or tax treatment differs from what you recorded, update the dataset and your budget rather than assuming the original number was right.

Evidence and red flags

Prefer official provider pricing pages, APIs, documentation and terms over affiliate summaries. Record the observation date and the exact source. If a provider does not state a fact, leave it unknown rather than filling the gap with a guess. Unknown fields are allowed; invented certainty is not.

Red flags include a renewal price that is not disclosed, “unlimited” traffic without a policy, unavailable IPv4/IPv6 details, a region catalog presented as guaranteed stock, and a price that cannot be reproduced on the official page. Any one of these is a reason to slow down and verify before paying.

Verification checklist

  • Write the exact plan, region, term and add-ons you intend to buy.
  • Confirm vCPU, RAM, storage size and storage type.
  • Check whether the CPU is shared or dedicated.
  • Verify IPv4 and IPv6 support separately.
  • Check transfer allowance, port speed and post-allowance behavior.
  • Confirm whether storage is included or separate.
  • Verify backup scope, retention and restore procedure.
  • Read the renewal price, cancellation window and refund policy.
  • Confirm tax treatment and currency.
  • Record the official source and observation date.
  • Prepare SSH keys, firewall rules and update policy before first boot.
  • Set up external monitoring and an independent backup copy.
  • Test a restore before production data depends on it.
  • Mark every unknown field and verify it with the provider.
  • Walk away if the renewal price or contract terms cannot be verified.

Sources