Español
English
Català
FrançaisThe practical difference between shared hosting and a VPS is who manages the server. With Sites, your provider maintains the web-hosting environment and you manage websites through a control panel. A VPS gives you root access and lets you choose what to install, while leaving more system administration to you.
Neither option is always faster or better. Choose based on the software you need to run, the control you need and the time you can spend maintaining it.
Sites and VPS compared
| Need | Sites, managed web hosting | VPS, virtual server |
|---|---|---|
| Administration | A control panel for each site; the provider maintains the hosting environment | root access; you configure the operating system and services |
| Applications | PHP and applications supported by the Sites catalogue | Packages and services you can install and maintain on Linux |
| Common uses | CMSs, shops and PHP websites with a database | Docker, Node.js processes, APIs, workers or custom setups |
| Backups | Weekly on Starter and daily from Pro; check the plan | Nightly external backup; restore it from the control panel |
| System access | No root; SSH is available on Agency |
root from the first boot |
| Maintenance | Fewer system tasks for you | You update, monitor and secure the services you install |
Check current scope on Sites, VPS and the pricing page: features depend on the product and plan.
Choose Sites when you want websites without running a server
Sites can fit a CMS, online shop or supported PHP application when you prefer a control panel for files, domains, databases and email. The provider maintains the service environment; you remain responsible for your content, application accounts and the permissions you configure.
Check how many websites, how much storage, how many databases and mailboxes, and what backup schedule you need. A shop with a catalogue and database still needs a data-recovery plan, even if the hosting plan includes backups.
Choose a VPS when you need root or your own services
A VPS gives you control of the system: install packages, run long-lived processes and build your own configuration. Hostbrid’s published sizes include root, specified resources, a console, snapshots and nightly external backups. The current VPS table shows the monthly total with its mandatory IPv4 already included.
For example, see this guide to hosting a Minecraft Java server 24/7 on a VPS: it is a persistent service you maintain yourself.
That control also brings work. Before ordering, decide who will update the operating system and containers, restrict SSH access, store secrets, monitor processes and test a restore. An automatic backup does not prove that you can recover the service.
What if AI created your website?
Look at the files and runtime, not just the name of the tool:
- Static HTML, CSS and JavaScript: if you have a folder of files to publish from Git, review Projects. Using AI does not mean you need a VPS.
- A CMS or catalogue-supported PHP app: Sites may fit if its resource, backup and access limits work for you.
- Docker, an API, Node.js processes or custom Linux services: consider a VPS if you can maintain the system and its services.
An app with sign-in, payments or forms may depend on an API, database or storage service. Moving the website does not automatically move those dependencies.
Compare total cost and operational work
Do not compare only the advertised starting prices. For Sites, check monthly versus prepaid annual billing, domain registration, email and the plan your websites need. For a VPS, check the size price including IPv4, storage, traffic and the services you will install. Add the time spent on maintenance; it does not appear on the server invoice.
For a migration, prepare a copy, export the database if there is one, review environment variables and test the domain before changing DNS. Start with Sites if you want fewer system tasks, or compare the available VPS sizes if you need root control.