Hünenberg
Swiss location for selected production services and our primary market.
Platform & locations
High-performance Proxmox platforms, fast NVMe systems, separate backup locations and a deliberately pragmatic architecture model for professional managed services.
Architecture principle
infrahost relies on high-performance, standardised systems and clearly defined recovery paths.
We operate Proxmox-based virtualisation platforms on AMD hardware with NVMe storage and RAID. Systems are monitored and protected across separate locations using Proxmox Backup Server.
For standard offerings, we deliberately avoid blanket cluster architectures that increase cost and complexity without delivering real value to every customer. Where a service requires higher availability, the additional architecture is explicitly designed and priced.
Locations
The right location depends on the service, data requirements, backup concept and required recovery strategy.
Swiss location for selected production services and our primary market.
German infrastructure and backup location through Hetzner.
Austrian infrastructure location through IPAX for regional services and backups.
French infrastructure location through OVHcloud for local and geographically separated services.
Italian infrastructure location through OVHcloud for regional services and backups.
Technical foundation
We choose technologies that remain manageable in day-to-day operations and fit the services we provide.
Transparent boundaries
We explain which protection measure addresses which risk — and where interruptions can still occur.
RAID protects against individual disk failures, but it does not replace backup. Backups enable recovery, but they do not provide interruption-free high availability. A cluster can reduce certain types of downtime, but requires additional systems, network paths, testing and ongoing maintenance.
Availability is therefore designed per customer service rather than sold as a buzzword.
Data location
Not every platform and every backup needs to be in the same location. At the same time, data-location decisions should never be made implicitly.
Before deployment, we clarify whether production data should remain in Switzerland, whether European backup locations are permitted and which customer or industry requirements apply. The binding setup is documented in the proposal and service description.
Frequently asked questions
The binding architecture always follows the requirements of the specific service.
Ask another questionNot automatically. Switzerland is our primary market, but the specific data location and backup locations are agreed for each service.
Clusters increase availability, but they also increase cost and complexity. For standard services, we rely on robust standalone platforms, RAID, monitoring, backups and prepared recovery. Higher availability is designed specifically where required.
Depending on the affected platform and service level, components are replaced or systems are recovered to available replacement resources. Priority and target times are defined contractually.
The selected locations and network providers provide DDoS protection mechanisms. The exact level of protection depends on the location and attack scenario; absolute protection against every attack cannot be guaranteed.
Architecture discussion
We design the technical foundation, backup and recovery to match the requirement.