Four questions, then the cheapest plan that answers all of them.
No sales logic and no "recommended" badge. Every plan on this page is read from the same price list the checkout charges from, and the one we point at is simply the least expensive that meets every answer you gave.
the cheapest plan that satisfies every answer
The least expensive plans, on one scale
Answer the questions above and one of these gets marked. Until then, these are the least expensive monthly plans, on one log scale from the first price shown to the last.
If you already know what you run, start here
The finder above chooses by size. This list chooses by the kind of workload, using how each family of plans is described on its own page.
A company site or a busy blog on a shared account
A site with 90,000 or more page views a day
Root access for a small production app
Fast single-thread speed on shared cores
Software built for Arm64
Cores that no other customer shares
A load balancer in front of your app
A whole physical machine, or room for archives and backups
A Windows desktop over RDP
Someone else to watch the server
Six things to know before you answer
Each one changes which plans are allowed. Open a row to see how to find the number.
How many sites and domains
Count every domain and subdomain that must answer on its own address, including www and any shop or blog subdomain. The site-count question above filters the plans on exactly this number.
How much disk you use today
Measure the site folder and export the database to see its real size, then leave room to grow and for local copies. On a Linux shell, du -sh on the folder prints the total.
How much traffic you get
Use page views per day from your analytics, not visits or hits: a single page view can trigger dozens of file requests. The shared plans are described by daily page views, so that is the number to compare.
Whether the software needs root
An account without root cannot install system packages, run its own background services or listen on other ports. If your software needs any of these, you need a server of your own (cloud, VPS or dedicated), not shared hosting.
Which processor architecture your software is built for
Most software runs on x86-64. Arm64 servers need builds compiled for Arm, and a container image must offer an arm64 variant. Running uname -m on your current machine prints x86_64 or aarch64.
Who will run it
A server of your own has to be patched, monitored and backed up by someone. The last question in the finder adds our management line for that; decide who would answer if it stopped at night.
Still not sure? Say what you are moving.
Tell us what runs today and how much of it there is, and we will say which plan takes it — including when the answer is a smaller one than you expected.
