Compute Services

With "Compute Services," customers can obtain the required compute performance on demand based on different compute technologies and service models in Inventx's highly available data centers and align them according to the required SLA requirements.

Compute Services are used to deploy, host, and manage workloads. This section describes the different services and their options in relation to compute services in ix.Cloud.

Table: Compute Services

Service Name	Service Description
Virtual Machine	Virtual machine (VM) hosted in ix.Cloud, optionally also with management of the guest operating system via "Plus Services"

Virtual Machine

Through the ix.Cloud "Virtual Machine" service, a virtual computer (VM) can be provisioned within minutes in the geographic region that is suitable for the required workload.

Service Architecture

Figure: Virtual Machine Service Architecture

Service Scope

Table: Virtual Machine Service Scope

Feature	Feature Description
Definition, configuration, and provisioning of OS instances (VM with OS image)	Automatic provisioning of a server from image (see Service Options) Decommissioning of a server Automated deployment of storage including choice of storage class Change of SLA and change of location via "Standard Service Request"
Management and monitoring of computing systems and virtualization components	Monitoring and reporting via the web portal (monitoring includes a configuration and capacity overview per VM as well as a list of attached resources) Administrative rights at VM level (Start/Stop/Reconfigure) Administrative rights in guest OS with local accounts Authentication to customer AD via NTLM or Kerberos Authentication via SAML (e.g., customer AD) Access to the remote console of the VM, and depending on the selected operating system, access via Remote Desktop or SSH protocol OS operation by customer
Management and monitoring of storage subsystems and storage networks	Change of storage class Adding or removing additional data disks
Management and monitoring of backup systems	Backup of the virtual server monolithically at VM level (retention 14/40/90 days, daily) "No Backup" option Restoration of VM (monolithically at VM level) based on SLA Encryption of backups with separate key per customer
Configuration and provisioning of virtual networks	Configuration and use of virtual networks (SDN) Provisioning and operation of virtual networks (VLAN). Limited to three VLANs per subscription Additional VLANs are billed according to effort
Additional Services	Assurance of manufacturer support for all infrastructure components Ensuring capacity management of all infrastructure components (e.g., is there sufficient server hardware, storage hardware, or backup hardware?) OS licenses and necessary licenses for infrastructure components included (e.g., backup, OS monitoring) Automated reporting Automated billing Independent management and viewing via online portal ON / OFF capability available

IT Baseline Protection

This section describes the general definitions of IT baseline protection for the compute service (at host level).

Patch Management

• Systems are patched on a 4-week cycle following our wave concept.
• Exclusions are generally not provided as these are critical security updates. An exclusion would only be considered in the case of a faulty patch and can be configured accordingly.
• In emergency patching, an identified critical vulnerability is patched immediately.

Logging

• Systems are logged by our monitoring, including event logs, logins, and administrator account records.
• System logs are retained for at least 9 months.
• Monitoring ensures that logs are continuously recorded. In case of failure, a ticket is automatically sent to operations.

Malware Protection

• An always up-to-date antivirus is the foundation of our malware protection.
• Updates are performed monthly together with patching. For critical vulnerabilities, an extraordinary update is performed.

Hardening

• We follow the CIS standard, which has been approved by the ATSB.
• All recommended security settings are implemented as long as they do not create functional restrictions.
• CIS recommendations are reviewed at regular intervals and considered in new software release cycles.

Configuration Management

• Systems (assets) are registered in our central CMDB
• Configurations are documented in the BHB and are implemented in the golden image of the deployment

Service Options

A VM can be adapted to current requirements via ix.Cloud Portal/API and through service requests by means of a variety of configurations and options.

Hardware Profiles

Hardware profiles are distinguished between two types (Standard and Highclock). The Standard hardware type has processors with a low clock frequency and is suitable for use with multithreading-capable applications. With the Highclock hardware type, on the other hand, processors with increased clock frequency are used; they are particularly suitable for non-multithreading-capable applications.

The following tables provide an overview of the available hardware profiles per hardware type. Additional hardware profiles can be requested via "Generic Request". Any implementation and pricing will be reviewed and approved by Inventx on a case-by-case basis.

Hardware profiles with 256 GB RAM can only be ordered via "Generic Request".

Table: Virtual Machine Hardware Profiles Standard

Standard		RAM in GB
		4	8	16	24	32	64	96	128	256
Number of vCPU	2	◼	◼	◼	◼	◼	⁃	⁃	⁃	⁃
	4	⁃	◼	◼	⁃	◼	◼	⁃	◼	◼
	6	⁃	⁃	⁃	⁃	⁃	◼	⁃	◼	◼
	8	⁃	⁃	◼	⁃	◼	◼	◼	◼	◼
	12	⁃	⁃	⁃	⁃	⁃	⁃	⁃	◼	⁃
	16	⁃	⁃	⁃	⁃	◼	◼	⁃	◼	◼
	24	⁃	⁃	⁃	⁃	⁃	⁃	⁃	◼	◼
System Disk		Windows: 100 GB / Linux: 80 GB

Table: Virtual Machine Hardware Profiles Highclock

Highclock		RAM in GB
		4	8	16	24	32	64	96	128	256
Number of vCPU	2	◼	◼	◼	◼	◼	⁃	⁃	⁃	⁃
	4	⁃	◼	◼	⁃	◼	◼	⁃	◼	◼
	6	⁃	⁃	⁃	⁃	⁃	◼	⁃	◼	◼
	8	⁃	⁃	◼	⁃	◼	◼	◼	◼	◼
	12	⁃	⁃	⁃	⁃	⁃	⁃	⁃	◼	⁃
	16	⁃	⁃	⁃	⁃	◼	◼	⁃	◼	◼
	24	⁃	⁃	⁃	⁃	⁃	⁃	⁃	◼	◼
System Disk		Windows: 100 GB / Linux: 80 GB

note

Highclock hardware profiles are offered exclusively in the "Rhodium" SLA.

Storage Profiles

Storage profiles are composed of the storage type (redundancy) and storage class (speed), with the storage type depending on the selected SLA. For each virtual computer, only one storage type and one storage class is possible for all drives.

The table "Storage Classes" shows in the column "max IOPS / vDisk" the number of IOPS as limited by the hypervisor. This is the technically maximum possible number of IOPS, which however cannot be guaranteed in every case.

For the storage type "SZRS" in connection with the storage classes "High Performance" and "Ultra Performance", the specified throughput cannot be achieved if the block size is smaller than 32 KB. For the storage class "Ultra Performance", Inventx reserves the right to temporarily reduce capacity in case of performance bottlenecks.

Table: Virtual Machine Storage Types

Storage Type	Redundancy	Latency (Measurement duration 2h)	SLA
LRS	locally redundant	< 1 ms	Bronze & Silver
AGRS	asynchronously geo-redundant	< 1 ms	Gold
SZRS	synchronously zone-redundant	n/a	Rhodium

Table: Virtual Machine Storage Classes

Storage Class	Throughput (MB/s)	max IOPS / vDisk
Standard	40	5'120
Premium	150	19'200
High Performance	300	38'400
Ultra Performance	500	64'000

Operating Systems

As the operating system, either an image prepared by Inventx or a "Custom Owned OS" can be used.

The images provided by Inventx are patched at regular intervals after release by Inventx to the level of Wave 3. This is to ensure that new orders can be offered in Wave 3 or newer. An update to Wave 2 or Wave 1 is possible immediately after the ordering process. The update is implemented as follows:

• Windows: Once per quarter
• Linux: Upon each new minor release (e.g., RHEL V. 7.1 ➞ 7.2)

After the staging process of a new VM, it is not patched directly to the desired wave. The first update process occurs after the "Customer Maintenance Window" defined by the customer, meaning after the selected wave and time choice. However, it is possible to patch a VM manually after deployment.

Among the images provided by Inventx are also license-free operating systems. For these operating systems, there is no manufacturer support. For this reason, Inventx can only guarantee the operation of these VMs on a "best effort" basis and reserves the right to suspend the recovery time according to SLA in the event of a malfunction (incident management) for errors beyond its control.

With customer-owned OS, the customer provides the image required for installation. The formats ISO and VHD are supported. In the case of ISO, the necessary settings for installation from the ISO file can be made directly in the self-service portal. If the VHD format is used, the settings for installation from the VHD file must be requested via "Generic Request". In both cases, manual work by Inventx is covered by the service request price.

Table: Virtual Machine Operating Systems

Operating System	Image	License	Plus Services
Windows Server 2022 Core	◼	◼	◻
Windows Server 2022 Desktop Experience (DX)	◼	◼	◻
Windows Server 2025 Core	◼	◼	◻
Windows Server 2025 Desktop Experience (DX)	◼	◼	◻
Red Hat Enterprise Linux 9	◼	◼	◻
Red Hat Enterprise Linux 10	◼	◼	◻
AlmaLinux 8	◼	⁃	◻
AlmaLinux 9	◼	⁃	◻
Customer Owned OS	◻	⁃	⁃

Backup Profiles

The customer can use different backup profiles to implement data protection of the virtual server in different and customizable ways. Data protection is always created monolithically across the entire virtual server.

Table: Virtual Machine Backup Profiles

Feature	Bronze	Silver	Gold	Rhodium
Monolithic backup of the virtual server	◼	◼	◼	◼
Encryption with customer-specific key	◼	◼	◼	◼
Interval daily	◼	◼	◼	◼
Location
At the same location as the VM (local)	◼	⁃	⁃	⁃
At a remote location (remote)	⁃	◼	◼	⁃
At two locations (local & remote)	⁃	⁃	⁃	◼
Retention period
No Backup	◼	◼	◼	◼
14 Days	◻	◻	◻	◻
40 Days	◻	◻	◻	◻
90 Days	◻	◻	◻	◻
On-Demand Backup	◼	◼	◼	◼

Restore

If virtual servers are backed up (see Backup Profiles), they can be restored based on available backup copies. The customer can perform monolithic restoration of the virtual server via self-service.

Partial restoration (e.g., a specific file or folder) can be requested via "Standard Service Request".

Availability Set

To increase the availability of an application, it is recommended to set up two or more VMs with the same application and group them in an Availability Set. When multiple VMs are assigned to an Availability Set, the hypervisor will place these VMs on different hosts whenever possible. This configuration ensures that during a planned or unplanned outage of a host, at least one VM with the application remains available. Each Availability Set guarantees 3 hosts, with a maximum of one in maintenance mode at any time.

Availability Sets must be managed via a "Standard Service Request" to subsequently be able to assign VMs to an Availability Set via the ix.Cloud self-service portal.