Which plan for a web application or an API: shared hosting, VPS or Cloud

Start with the simplest and move up only when the application asks for it. An application in Node.js, Python, Ruby or PHP runs on shared hosting, with the version picked in cPanel. A VPS becomes necessary when the application needs always-on services, ports of its own, programs the shared plan does not install, or root access. Cloud is for when the application already splits across several machines.

Where each thing runs

Your application Where it fits
A PHP site or API (Laravel, CodeIgniter) Shared hosting, with the PHP version picked per folder.
A Node.js, Python or Ruby application Shared hosting, through the cPanel tools “Setup Node.js App”, “Setup Python App” or “Setup Ruby App”. See Node.js in cPanel.
A background task that never stops (queue, bot, WebSocket) A VPS. A permanent process is not the shared hosting model.
Docker, databases the plan does not bring, software of your own A VPS or a dedicated server, with root access.
Several machines talking (application, database, queue) Cloud, with the private network between machines. See VPS vs Cloud.

How to decide, step by step

1 List what the application needs to run. Language version, database, background services, ports, memory. The list is in the application’s documentation.
2 Compare it with what shared hosting offers. The languages and the limits are in which technologies run here.
3 If it fits, start there. Getting the application running is the first step; see getting a Node.js application running.
4 If it does not fit, move to a VPS and choose the system. See which operating system to choose for your VPS and first steps with your VPS.

The question that settles more cases than you would think

Does the application need to be doing things all the time, or does it only answer when someone asks? Those that only answer when asked (a website, an API that receives calls) fit shared hosting. Those that must act on their own, listen, or work through a queue without stopping need a permanent process, and that means a VPS. For tasks at set times, a scheduled job does it on shared hosting: see cron jobs: what they are for and how to create one.

On a VPS the administration is yours. Updates, firewall, backups and installing the application’s software are on your side, and our support does not install or repair them. See how far our support goes and managed or unmanaged VPS.
Measure before you move up. A slow application may be a badly written query and not a lack of machine. The same slowness comes with you to a bigger server. See what to measure before you change plan.

Describe the application (language, database, services) and we will tell you whether it fits shared hosting or needs a VPS.

Open a support ticket

SEE ALSO

Shared hosting vs VPS: which one does your project need?

VPS, Cloud or Dedicated: how to choose

Which technologies run here: PHP, Node, Python, Perl, games and the limits

VPS servers

RECOMMENDED PRODUCT

VPS server with root access

Resources of your own, the OS you choose, reinstall whenever you like. from ₦12.600,00/mo (3-year plan, with coupon)

See plans
  • 0 Users Found This Useful
Was this answer helpful?