What we use Proxmox for
Proxmox VE is open-source virtualisation at enterprise level — and for us the basis of every hosted project. The clusters carry Shopware shops, TYPO3 and WordPress sites, Symfony applications, along with databases, search indexes and interface services. Each project gets its own virtual machine, cut to fit its system: memory, CPU and storage are allocated according to actual need, not according to a package name.
The difference from shared hosting shows on the bad day. If a neighbouring project generates load, yours notices nothing, because it does not share the resources. If a PHP version has to be updated, that affects your system and no other. And if an update goes wrong, there is a snapshot from before. These are unspectacular advantages — they count precisely when things get uncomfortable.
How we run the clusters
The clusters stand on our own servers in Germany. We run them as a group so that environments can move to other hardware while in operation — for maintenance, when hardware is replaced, or when a project has grown. Storage is redundant, backups run through Proxmox Backup Server with versioned states. Restoring is rehearsed, not assumed: a backup nobody has ever restored is a guess.
Operations covers everything around it: operating system and PHP updates, database maintenance, monitoring, certificates, DNS and domains. New environments are set up from a template so that test and production systems look the same. On request, individual services run in containers inside the virtual machine. We are available Monday to Friday, 9:00 to 16:00 CET; cover beyond that is set out in individual service level agreements.
Limits and alternatives
Our own infrastructure has one clear limit: capacity does not grow without end at the click of a mouse. If you expect many times the load overnight and only on a few days a year, you are better off with AWS or Google Cloud. The same goes for worldwide delivery with low latency across several continents, and for managed services you could only run yourself with considerable effort.
The price is no automatic win either. Your own environment costs more than a slot in mass hosting — in return you get resources that belong to you and someone who knows the system. For a small business-card website with no particular demands that is oversized; there are cheaper routes for that, and we say so. It becomes worthwhile as soon as a system carries revenue or maps a process.