← All Services

HOSTING / CONTROL A SERVER

VPS Hosting Explained

A virtual private server (VPS) gives you a server environment inside a larger physical machine. It is useful when you need software, configuration or access that ordinary web hosting does not provide.

What You Are Buying

You rent virtual CPU, memory, storage and networking, usually with administrator access. The physical host is shared unless the product says otherwise. A vCPU is a scheduling allocation, not a universal measure of speed: processor generation, shared versus dedicated CPU, contention and burst rules all matter. A VPS can run several services, but you also combine their failure and maintenance risks.

When You Would Use It

  • Run an application with custom packages, containers or background workers.
  • Host several modest services when someone can maintain the operating system.
  • Create a development or test environment with reproducible configuration.

What You Still Manage

On an unmanaged plan, expect to own OS patching, firewall rules, application updates, monitoring, backup configuration and restores. The provider repairing the physical host does not repair your application. Never assume buying more RAM includes administration.

Privacy Considerations

Administrator control inside a VPS does not remove the infrastructure provider from the trust model. Privileged infrastructure access, snapshots and support procedures matter. Ask who can access disks or diagnostics, whether backups leave your chosen region, and who controls encryption keys. You are also responsible for privacy in the applications and logs you run.

Compare provider access, logs, retention and encryption →

Consumption, Allowances & “Unlimited”

Read the RAM allocation, sustained CPU rules, disk capacity and I/O limits, transfer allowance, port speed and extra-IP charges. Burstable products may use credits or charge for sustained use. A monthly server price may exclude backups and licenses. An “unmetered” network is not unlimited CPU or disk.

Read the plan’s resource limits and acceptable-use policy together. Ask what happens at the threshold: an extra charge, reduced speed, rejected requests or suspension. Understand the billing language →

Questions to Ask Before Buying

  • Are CPU resources shared, dedicated or credit-based?
  • Who patches the OS and responds to an application outage?
  • Do stopped servers, disks, snapshots or reserved addresses keep billing?
  • Can I restore a backup to a new server without provider assistance?

The takeaway: More control comes with more operational work. Include that work in the cost.

Technical reference: AWS: responsibilities for infrastructure services.

Linked for its explanation of the technology, not as a provider recommendation. Features and contract terms vary.

Build a complete buying checklist →