Every project gets its own environment
In mass hosting, hundreds of customers share one machine and the configuration is a compromise that suits none of them properly. We work differently: every project gets its own virtual environment — with as much CPU, memory and storage as the system actually needs, and with exactly the services that make it faster: Redis for caching, Elasticsearch for search, a staging environment for updates you can test without risk.
The environment is tuned to the system running in it. A Shopware shop with peak load before Christmas needs a different layout than a TYPO3 site with a busy editorial team, or a custom application with nightly imports. That tuning is not an extra here, it is the normal case — it is the reason we build environments individually.
Proxmox PVE as the foundation
Our systems run on powerful Proxmox PVE clusters on our own servers in Germany. Proxmox Virtual Environment is an open-source virtualisation platform at enterprise level: every customer environment is cleanly isolated from every other, can be moved to different hardware while running, and can be restored from backup in short order.
For you that means resources grow with the project, without a server move. Snapshots before every update keep changes low-risk, daily backups run automatically. And because the infrastructure is ours, a fault does not leave you waiting on someone else's support desk — these are our clusters, and we go in ourselves.
AWS infrastructure when the project calls for it
Not every project belongs in our own environment. International audiences, heavily fluctuating load or group-wide policies sometimes argue for AWS — then we build and run the infrastructure there: properly sized, documented, and with the same people to talk to as in our own operation.
Our advice on this is honest. In most cases our own Proxmox infrastructure is the more economical and more controllable answer. Sometimes AWS is the right one. The recommendation follows the project, not our convenience.
Domains: register, manage, move
The address is part of running a system. We register new domains, take over existing ones by changing the registrar, and manage DNS records, redirects and SSL certificates in one place — so a server change, a campaign subdomain or an email migration does not need coordinating between three suppliers.
That includes precautions. We register the obvious misspellings and the TLDs that matter — .de, .com, .eu — before somebody else does. Unspectacular, until the one time it was missed.
Operation means somebody is actually looking
Monitoring reports faults before your customers notice them. We apply security updates at system level regularly, and when something is stuck you reach the people who built your environment, Monday to Friday, 9:00 to 16:00 CET — not a ticket queue. Looking after the application itself is the job of our support team, under a maintenance contract for TYPO3, WordPress and Shopware.