Large Project: Campaigns With High, Sustained Traffic
For large campaigns with consistently high load, say during a multi-week sale period tied to an app or shop, a root server is worth considering. The key difference from a VPS is in CPU allocation, not RAM: both products guarantee the RAM you book.
A root server gives you dedicated CPU cores, while a VPS runs on vCores without guaranteed compute performance. For short spikes that barely matters, but under sustained high load over days or weeks, it becomes noticeable.
Root access comes with both products, by the way, so that's not a distinguishing factor. A root server makes sense if you:
- expect sustained high load
- want maximum control over your system
- plan to run your own caching or CDN setup directly on the server
Scaling During the Campaign
The biggest mistake in campaign hosting is waiting until the first signs of overload to react. Plan ahead for how you'll respond quickly if needed.
Upgrading to a larger VPS or root server plan can usually be done without rebuilding the environment from scratch. During the campaign, keep an eye on load times and server utilization too, ideally with simple monitoring in place.
After the Campaign: Don't Skip Maintenance
Once a campaign ends, the page often stays online but gets updated far less often. Set fixed dates for security updates anyway, since outdated systems are a common target for automated attacks.
If the landing page no longer needs its original capacity, switching to a smaller VPS or root server plan usually isn't possible directly. Since these products don't support an automatic downgrade, moving down typically means cancelling the existing product, ordering the smaller plan, and migrating the data manually, for example via snapshot or rescue system.
Matching products
- Web Hosting: for single landing pages with moderate, predictable traffic
- VPS: for several campaign pages, custom applications, and traffic spikes
- Root Server: for large campaigns with sustained high CPU load and demands for consistent compute performance