Skip to content
Two hands in dark suit sleeves with white shirt cuffs hold a small white cloud between them without touching it: the upper hand lies palm down above it, the lower hand open below it. The cloud glows from the inside and casts a purple glow on both palms. The background is a dark purple gradient that remains empty towards the right.

Private Cloud from data centres in Germany: dedicated hosts without other tenants, operated by ENTRONYX CLOUD up to the hypervisor — 5 host classes under 4 stacks at 2 locations. Billed per host and month, optionally 12 or 24 months in advance with a term discount; ordered here, the cluster is ready in 3 to 5 working days.

Per host from
€510.59$592.28
PC-S32 under ENTRONYX KVM Platform, net
Delivery
3–⁠5 working days
Handover with access credentials and operations manual
Host classes
5
16 to 384 cores, up to 1 TB RAM
Stacks
4
KVM, vSphere, HCI — SAP-certified on request

Contract, certificates and availability

Locations
2 in Germany
Frankfurt am Main (fra1) and Düsseldorf (dus1)
Location data
Certificates
ISO 27001 · EN 50600
ISO 27001 valid until 30 November 2027 · EN 50600 VK4 per location · BSI C5 without Private Cloud in scope
Scope and term
Contract
DPA according to Art. 28 GDPR
Data processing in the main contract · GDPR, BDSG, German law
Obligations from the DPA
Availability per host
99.90%
Class C of SLA 4.2, the class of dedicated servers · Credit 10% to 100% of the basic fee
Classes and service credits

Platform, host class, number of hosts in the cluster, storage, location and term — the amount is updated next to it after every decision, with the same rates as the configurator and checkout. One click adds the cluster to the cart; you add network and operations in the configurator.

vSphere cluster · ENTRONYX Managed vSphereDatastore NVMeStandard4 TBPC-M64PC-M64Düsseldorf DUS1

Initial situation optional

Or choose freely — each choice below recalculates immediately.

Platform Virtualisation and licence model

€475.20$551.23Licence per host / month

vCenter-managed cluster with HA, DRS and vMotion. Compute and storage are separated: the guests run on the hosts, their data on a shared datastore. vCenter is the management interface of the cluster; HA restarts the guests of a failed host on the remaining ones, DRS distributes the load, vMotion moves running guests. licence: €9.90$11.48 per core and month.

Host class Prices including licence

€1,498.20$1,737.91per host / month

Host class

Locked host classes state their reason. The fabric is the dedicated storage network between the hosts and their shared storage; a vCPU is a virtual processor that you assign to a guest.

Number of hosts 2 to 32

€2,996.40$3,475.82Hosts including licence / month

2 hosts32 hosts

If a host fails, the remaining host continues to carry the guests.

Storage

€294.91$342.10net / month

The standard case: NVMe backend via NFS or iSCSI, for mixed guest workloads. A datastore is the shared storage that all hosts see; IOPS are input and output operations per second, guaranteed per datastore.

Capacity

1 TB256 TB

Usable capacity is ordered. Triply replicated across two fire zones of the location — included, not deducted.

Location

A cluster is located entirely at one location; a second location is provided by the recovery tiers in the configurator. The milliseconds are the median latency from Frankfurt.

Term

− €164.57$190.90Discount / month

The discount applies to the monthly net amount; with a term, you pay for the booked months in advance with the first invoice.

Net per month after discount

Nobody looks for a Private Cloud just because it is one — but because an invoice has gone up, a room has run out of space, or an auditor asks a question. For three of these situations, here is a cluster with its price; a click loads it into the quick configurator above.

  • The vSphere invoice has increased after the licence change

    Since the switch to per-core subscriptions, you pay a multiple for the same hosts, the minimum purchase per socket hits small clusters in particular, and changing the hypervisor during operations is not an option.

    You keep vSphere, vCenter and your runbooks. The licence runs on our contract and is shown transparently on every invoice — per core, minimum 16 per socket, which does not apply with 48 cores per host, and with no minimum term. We patch the hypervisor, during the maintenance window, host by host.

    If you want to move away from the vSphere licence, you get the same hosts under the open KVM stack — €49.00$56.84 per socket instead of €9.90$11.48 per core.

    Proposal
    vSphere cluster · 3 × PC-M64
    144 cores · 696 GB allocatable · Düsseldorf
    Monthly net
    €5,199.11$6,030.97
    Load in quick configurator: vSphere cluster · 3 × PC-M64

    Open all five steps: vSphere cluster · 3 × PC-M64

  • Your own server room is at the end of its service life

    The hardware is depreciated, the maintenance contracts are expiring, the UPS is older than the applications it protects. Building a new facility is not worth it for two racks — but the data should stay in Germany, with an operator you can reach.

    A hyperconverged cluster replaces servers, storage systems and storage networks in one step: three hosts, a distributed NVMe pool, growth by individual hosts. We maintain firmware, hypervisor and fabric; your administrators keep the guests.

    With fewer than 6 hosts, the pool runs with two-way mirroring — 47% of the raw capacity is then usable instead of 62%. The nightly backup goes to Frankfurt am Main from Düsseldorf; if you want to specify the destination country, choose "Asynchronous replication" (same country).

    Proposal
    Hyperconverged · 3 × PC-L128
    192 cores · 1,416 GB allocatable · Düsseldorf
    Monthly net
    €8,632.88$10,014.14
    Load in quick configurator: Hyperconverged · 3 × PC-L128

    Open all five steps: Hyperconverged · 3 × PC-L128

  • The cloud bill is growing, and the auditor asks about the location

    The base load runs around the clock, but is billed by the hour like a peak. The next audit wants to know which data is on which device and who has access — an answer that a shared platform does not provide at the device level.

    Managed dedicated hosts under the open hypervisor: named devices in a named rack, management via API and Terraform, billing per host and month. Fluctuating loads stay in the Public Cloud — both are connected to the same vRack.

    A single host is enough to start; an automatic restart after a host failure is only available from the second one onwards.

    Proposal
    Managed dedicated hosts · 2 × PC-M64
    96 cores · 464 GB allocatable · Düsseldorf
    Monthly net
    €2,438.91$2,829.14
    Load in quick configurator: Managed dedicated hosts · 2 × PC-M64

    Open all five steps: Managed dedicated hosts · 2 × PC-M64

All amounts net per month, location Düsseldorf, before term discount — 5% for twelve, 8% for twenty-four months. In the quick configurator, you can change the location, storage and term without starting from scratch.

Your situation doesn't fit? Call back within 4 hours during business hours, preferably in the selected time window — voluntary commitment, not part of the SLA. Arrange a callback

Low-angle view of the flank of a long block of server cabinets, whose perforated, purple-glowing doors recede into the depth to the left. The smooth dark flank fills the centre of the image; on it sits a large, almost white metal plate with rounded corners and four screws, reading ENTRONYX CLOUD. Below the block, a narrow light gap runs across the polished floor, to the right the hall remains dark purple.

The flank of the allocated block bears the ENTRONYX CLOUD brand: every managed host is a named device in a named rack, running exclusively your guests — the light gap in the floor is the boundary.

From order to delivered cluster

Order, hand over, grow — for each step, what you do and what we do.

  1. A block of five identical server cabinets, bolted side by side, seen closely from its right end: the smooth dark flank fills the right half of the image, the perforated doors recede to the left, behind each a stack of servers glows purple with small light green status lights. On the flank sits a long, light metal plate with six screws, reading ENTRONYX CLOUD. A narrow light gap in the floor frames the block as a rectangle; the floor reflects it, the surrounding hall lies in purple twilight.

    Ordered — with account from the checkout

    You configure your cluster on this page, add it to the cart and go to checkout. The account is created there — with account type, contact, email address and password; the billing address follows with the first order. There is no setup fee.

    • YouChoose term: monthly, 12 or 24 months
    • WeInvoice under “Account › Services” — commitments in advance with the first invoice
    • ScopeDiscount of 5% for 12, 8% for 24 months on the net amount

    Configure cluster

  2. Close-up of the upper third of an open server cabinet, seen from the front: the perforated metal door is swung open to the left, at the top sit three flat network switches with rows of small ports, below them a stack of flat servers, each with a light green status light. From the switches, bundled, combed cables run down in a neat curve on the right inside and into the servers. To the right stands the closed neighbouring cabinet; its purple-illuminated perforated metal door bears a landscape-format light metal plate with four screws, reading ENTRONYX CLOUD. Below, a strip of light floor.

    Handed over in 3 to 5 working days

    We equip the hosts, cable the fabric, the storage network, and accept the cluster. Handover includes an operations manual and access to the management plane: under vSphere to your own vCenter, under KVM to the Cloud Director, under HCI to the Web console of the cluster.

    • YouSet up guests — your layers: Guest operating system, Middleware, Application, Application data
    • WeMaintenance under vSphere: Wed 02:00–06:00 CET, rolling host by host, announcement 14 days in advance
    • Deadline3 to 5 working days from checkout to handover

    Operating model layer by layer

  3. A block of four server cabinets glowing purple from the inside, seen from the front; on the right, a fifth cabinet is attached, its door standing open: the upper half is equipped with glowing servers, the lower half still empty. The back wall behind it is illuminated in purple; above the block hangs a landscape-format light metal plate with four screws, reading ENTRONYX CLOUD. To the right, the wall opens to a passageway, behind which a second, smaller block of three cabinets glows; a light gap in the polished floor runs forward from the passageway.

    Grow and secure

    A shared datastore, the storage area of the virtual disks, grows separately from the hosts; in a hyperconverged cluster, the storage grows with each host. You decide on the recovery separately, per tier with a committed recovery point and recovery time.

    • YouAdd hosts: vSphere up to 32, HCI 24, KVM 16
    • WeIntegrate new hosts into maintenance and load balancing, test the recovery with an activity log
    • ScopeThree levels: nightly backup to a second region up to 15-minute replication to a second location

    Recovery tiers

Three recovery tiers at a glance

The summary of the third step: what each tier promises, where it replicates to, what it costs per month and how the promise is audited. The conditions under which a number applies are on the recovery page — where they are part of the promise.

Three tiers in a table

Recovery point, recovery time, target region, monthly fee and audit trail per tier
Recovery point (RPO), recovery time (RTO), target region, net monthly amount and audit path per tier; next target location from Düsseldorf
TierRecovery pointRecovery timeTarget regionMonthly amountVerification
Secured recoveryKVM Platform, Managed vSphere, HCI, SAP Certified24 h8 hSecond EU region, from 150 kmfrom dus1: Frankfurt am Main (fra1)€149.00$172.84per environment, plus €0.0074$0.0086 per GB1 Recovery test per yearwith report to you
Pilot LightKVM Platform, Managed vSphere, HCI4 h4 hRegion in the same jurisdiction, from 150 kmfrom dus1: Frankfurt am Main (fra1)€490.00$568.40per environment, plus €0.0190$0.0220 per GB2 Recovery tests per yearwith report to you
Asynchronous replicationKVM Platform, Managed vSphere, HCI, SAP Certified15 min2 hRegion in the same jurisdiction, from 150 kmfrom dus1: Frankfurt am Main (fra1)€990.00$1,148.40per environment, plus €0.0340$0.0394 per GB4 Recovery tests per yearwith report to you

Net amounts per month: a base fee per protected environment and a rate per protected gigabyte. A tier does not replace an availability promise — and the availability promise does not replace a tier.

Conditions, target locations and testing procedures

Three cuts through the same hardware

Public Cloud, Private Cloud and Bare Metal run in the same halls on the same device family. The difference is not the location or the form factor, but who a device is assigned to, how it is billed and from which layer you are responsible.

In the Public Cloud, capacity comes from a pool. A host carries guests of multiple customers. They are separated by the hypervisor, the software that divides a device into virtual machines. We operate and allocate the cluster behind it. Billing is based on term — from €0.0082$0.0095 per hour. If you switch off at night, you don't pay at night.

In the Private Cloud, the host is a named device. Only your guests run on it; placement is not decided by us based on utilisation, but by you according to your rules. Billing is per host and month, regardless of how many virtual machines are on it. We operate what lies below the guest — hypervisor, firmware, fabric.

On bare metal, our responsibility ends at the hardware. You get a device and the remote management card; you alone decide which operating system, which hypervisor and which firmware version run on it. This is the greatest freedom of the three cuts and at the same time the greatest operational burden.

What is the same in all three cuts

  • The same data centres, the same power supply, the same cooling.
  • The same device families — the Private Cloud is built on the metal of the Bare Metal series.
  • The same network connection via the vRack — our private Layer-2 network —, without transit costs between the areas.

What only the Private Cloud provides

  • Dedicated hosts and a managed hypervisor on them — the Public Cloud does not provide the former, bare metal not the latter.
  • Management in your own tenant: your own vCenter under vSphere and SAP, your own tenant in Cloud Director under KVM, the Web console of the cluster under HCI.
  • Guaranteed upper limits for overbooking instead of a utilisation policy that we alone determine.
  • Public Cloud

    shared

    Instances on shared hosts, billed by the hour, created and removed in minutes.

    Billing
    per hour
    Smallest unit
    2 vCPU · 4 GB
    Entry
    €5.99$6.95 / month
    Neighbours on the host
    external guests
    View cloud instances
  • Private Cloud

    this area

    Dedicated hosts with managed hypervisor. You allocate the capacity, we keep everything below it in operation.

    Billing
    per host and month
    Smallest unit
    PC-S32 · 16 cores
    Entry
    €510.59$592.28 / month
    Neighbours on the host
    none

    The entry level applies to PC-S32 under ENTRONYX KVM Platform — a single host. ENTRONYX Managed vSphere starts at 2 hosts.

  • Bare Metal

    Dedicated

    One device, one remote management card, nothing else. Everything above the hardware belongs to you — including the operational burden.

    Billing
    per device and month
    Smallest unit
    CORE-R7 · 8 cores
    Entry
    €65.54$76.03 / month
    Neighbours on the host
    none
    View dedicated servers

Who is responsible for which layer

Twelve layers, three models — who operates, who shares, who is responsible

The line on which the decision usually turns is not the price, but the firmware: in the Public Cloud and in the Private Cloud it lies with us, on bare metal with you. Below that nothing changes, above that everything.

  • Data centre, power, cooling

    Public Cloud
    ENTRONYX
    Private Cloud
    ENTRONYX
    Bare Metal
    ENTRONYX
  • Hardware and spare parts

    Public Cloud
    ENTRONYX
    Private Cloud
    ENTRONYX
    Bare Metal
    ENTRONYX
  • Firmware and BIOS

    Public Cloud
    ENTRONYX
    Private Cloud
    ENTRONYX
    Bare Metal
    You
  • Hypervisor and cluster services

    Public Cloud
    ENTRONYX
    Private Cloud
    ENTRONYX
    Bare Metal
    You
  • Storage fabric and datastores

    Public Cloud
    ENTRONYX
    Private Cloud
    ENTRONYX
    Bare Metal
    You
  • Network segmentation and firewall rules

    Public Cloud
    shared
    Private Cloud
    shared
    Bare Metal
    You
  • Capacity planning and placement

    Public Cloud
    ENTRONYX
    Private Cloud
    shared
    Bare Metal
    You
  • Guest operating system

    Public Cloud
    You
    Private Cloud
    shared
    Bare Metal
    You
  • Middleware and application

    Public Cloud
    You
    Private Cloud
    You
    Bare Metal
    You
  • Application data and classification

    Public Cloud
    You
    Private Cloud
    You
    Bare Metal
    You
  • Access management and roles

    Public Cloud
    shared
    Private Cloud
    shared
    Bare Metal
    You
  • Backup and recovery test

    Public Cloud
    shared
    Private Cloud
    shared
    Bare Metal
    You
ENTRONYX
We keep the layer operational, patch it and are liable for its availability.
shared
We provide the tools, limits and policies; you make the decision in individual cases.
You
Access and responsibility lie with you; we only see the layer in monitoring.

Five criteria, three models, no judgement

The same comparison, condensed to the rows that are actually asked about in a procurement discussion. The table recommends nothing — it places side by side what each model guarantees and what it costs.

The comparison in five lines

Isolation, licence sovereignty, operational effort, price per core and elasticity — per model, with amount
Isolation, licence sovereignty, operational effort, price per core and elasticity in Public Cloud, Private Cloud and Bare Metal
FeaturePublic Cloudshared hostsPrivate Clouddedicated hostsBare Metalbare metal
IsolationWho shares the metal under your machine?Shared hosts. The separation is provided by the hypervisor; with dedicated flavours, the core is reserved for you, but the device is not.Dedicated hosts under your ID, no foreign guests on the same metal, management plane in your own tenant.Dedicated device without a virtualisation layer above it — neither foreign guests nor a hypervisor computing alongside.
Licence sovereigntyWhose contract does the software between metal and guest run on?No own licence. What the platform needs is included in the instance price and is not visible from the outside.On our contract, openly stated: €9.90$11.48 per core and month under vSphere, €13.90$16.12 under HCI.Your licences on your contract — including the audit obligation towards the vendor and the question of how many cores an audit counts.
Operational effortHow many layers below your application remain with us?6 with us, 3 shared, 3 with you — out of 12 layers.5 with us, 5 shared, 2 with you — out of 12 layers.2 with us, 0 shared, 10 with you — out of 12 layers.
Price per core and monthCalculated on the machine under PC-M64 — the same hardware in each column, as far as the model sells it that way.Cores are not the unit there. ND6 costs €16.69$19.36 per dedicated vCPU (virtual core) and month, hourly €0.0200$0.0232.€31.21$36.20 per physical core, licence included — PC-M64 under vSphere.€17.58$20.39 per physical core as hardware share of the same machine — without hypervisor, without licence, without operations above it. The catalogue does not currently list it as a separate Bare Metal model.
ElasticityIn what steps and at what pace does the environment grow?Billed hourly, capacity from a pool. A powered-off instance costs no compute time.Monthly price per host, expansion in host steps. A cluster starts at 2 hosts under vSphere and 3 under HCI — below that there is no automatic restart.Monthly price per device, expansion in device steps. No cluster requirement, but also no instance that absorbs the failure of a device.

What runs on it — one configuration per workload

Four workloads that typically run on managed hosts. Each card lists the line, the configuration with the amount the configurator calculates for it, and the rule by which it is measured. User numbers are not shown here: how many sessions or bookings a host handles depends on your application, not the hardware.

  1. ERP — database and application server

    Database and application server as separate guests. The database depends on write latency and single-core clock speed: PC-M64i clocks up to 3.8 GHz, the Datastore NVMe Performance guarantees 0.4 ms p99 latency.

    Sizing: Two hosts, and the entire environment fits on one of them: if one host fails, ENTRONYX Managed vSphere restarts the guests on the other. Sizing is therefore against one host — 232 GB memory and 288 vCPU allocatable —, not against the total.

    SAP HANA does not belong in this cluster, but on certified nodes with their own protocol. SAP nodes

    Configuration
    2 × PC-M64i
    96 cores · 464 GB allocatable · Düsseldorf
    Datastore NVMe Performance, 2 TB with snapshots

    Monthly net

    €3,402.64$3,947.06

    Open this configuration
  2. File server

    High capacity with low compute load. The capacity datastore places an NVMe cache in front of HDD capacity and keeps snapshots for 30 days — sufficient for file services and quiet volumes.

    Sizing: The decisive factor is the daily volume of data moved, not the total amount. The NVMe cache covers 8% of the datastore size. Working sets beyond this pass through to the HDD tier; the 4 ms latency guarantee then no longer applies.

    Two hosts: if one fails, the file server restarts on the other — with one host, this restart would not happen.

    Configuration
    2 × PC-M64
    96 cores · 464 GB allocatable · Düsseldorf
    Datastore capacity, 8 TB with snapshots

    Monthly net

    €2,430.72$2,819.64

    Open this configuration
  3. Backup target

    A target for your backup software, physically separated from the systems it backs up. Capacity is the main requirement; PC-M64 is the most affordable class that supports a shared datastore in Frankfurt am Main.

    Sizing: Frankfurt am Main is located around 180 km as the crow flies from Düsseldorf — further than the minimum distance of 150 km required by the “Secured recovery” tier. Upper size limit: data volume times the number of retained full backups; the datastore scales up to 512 TB in the configurator.

    One host is sufficient for a backup target; automatic restart after a host failure is only available from the second host onwards. If the Private Cloud itself is to be backed up, the “Secured recovery” tier is the shorter route. Recovery tiers

    Configuration
    1 × PC-M64
    48 cores · 232 GB allocatable · Frankfurt am Main
    Datastore Capacity, 8 TB

    Monthly net

    €1,309.57$1,519.10

    Open this configuration
  4. Terminal server

    Many concurrent sessions: here, the number of cores counts more than their clock speed, and maintenance must not interrupt logins. PC-L128 provides 64 cores in one socket; ENTRONYX Managed vSphere evacuates the hosts one after the other before maintenance.

    Sizing: How many sessions a vCPU can handle depends on your application — which is why there is no user count here. The upper limits per host are fixed: 472 GB memory and 256 vCPU allocatable. With two hosts, the load of one must fit on the other, even during maintenance.

    Configuration
    2 × PC-L128
    128 cores · 944 GB allocatable · Düsseldorf
    Datastore NVMe Standard, 1 TB

    Monthly net

    €5,138.23$5,960.35

    Open this configuration

Net amounts per month, before term discount, excluding disaster recovery and without an operations level above platform operations. Every configuration can be further adjusted in the configurator — capacity, location and number of hosts, without starting from scratch.

Where the Private Cloud is the wrong fit

Four cases where another part of our catalogue gives the better answer. They are listed here because an offering that only names its strengths becomes expensive in operation — and because otherwise the decision is only made in the third conversation.

  • Load that fluctuates daily

    A managed host is billed per month, not by runtime. If you size for the peak, you pay for the peak at night and on weekends too. There is no shutdown that lowers the host price — the hardware sits in the rack under your name, whether it computes or not.

    The right choice here is the Public Cloud: it is billed hourly and capacity comes from a pool instead of a booked device.

    Shared instance from €0.0082$0.0095 per hour versus a host that is billed monthly.

    To Public Cloud
  • A system that needs no virtualisation

    Platform operations are fixed in the host price. If you do not use the hypervisor, you still pay for its operations, its maintenance window and — depending on the stack — its licence. For a single database on bare metal, this is a surcharge with no equivalent value.

    The right choice here is a dedicated server: the same bare metal, without the virtualisation layer and without its operations surcharge.

    FORGE-32 with 64 GB: €220.16$255.39. As PC-S32 with 128 GB, the same machine costs €241.43$280.06 more: storage expansion €92.43$107.22, platform operations €149.00$172.84.

    To Bare Metal
  • Full control down to the firmware

    In the Private Cloud, we operate everything below the guest. This is the core of the offering — and also its limit: you cannot set your own hypervisor build, your own kernel below the guest, or a custom firmware version here.

    If you need to fill these layers yourself, you need dedicated hardware without an operations contract on top.

    5 of the 12 layers are non-negotiably our responsibility: Data centre, power, cooling; Hardware and spare parts; Firmware and BIOS; Hypervisor and cluster services; Storage fabric and datastores.

    View shared responsibility
  • Environments below the minimum cluster

    An automatic restart after a host failure requires a second host and a shared datastore. If you can only afford one host, you do not get high availability — not even on a small scale. For the same reason, the smallest host class is explicitly not approved for shared datastores.

    The right choice then is a single instance with a backup, not half a cluster with the promise of a whole one.

    ENTRONYX Managed vSphere requires 2 hosts, ENTRONYX HCI 3. A dedicated server starts at €65.54$76.03.

    To VPS

0105Allocation

The host bears your name

A managed host is a named device in a named rack. It runs exclusively your guests, and placement follows your rules, not our utilisation. That is why the price is tied to the host and not to the number of virtual machines you run on it.

5 host classes · 16 to 384 physical cores per host · up to 1 TB memory

0205Access boundary

We operate everything below the guest

Platform operations are included in the host price and are not billed separately: we keep the hypervisor, BIOS and firmware, fabric switches and storage controllers up to date. Above this begins your side — guest system, middleware, application, data. If you want to move the boundary upwards, you book an operations level above it; it does not replace platform operations, but builds on top of them.

Platform operations included in the host price · initial response P1 30 minutes · P1 around the clock, P2 and P3 Mon–Fri 08:00–18:00

0305Oversubscription

The commitment is an upper limit, not a target value

How many virtual cores can be placed on a physical core is fixed per host class. Placement does not exceed this value, not even briefly and not even if a neighbouring host is currently quiet. Memory is not oversubscribed at all in the production classes: ballooning — the subsequent withdrawal of memory from running guests — costs more latency under load than the gained memory is worth.

PC-M64: 6 vCPU per core, 0% memory overcommit · PC-X256: 4 vCPU per core

0405Separation

Storage and guests run on two paths

Datastores are attached to a dedicated storage fabric, guests to the vRack. Separate paths are the reason why a nightly replication does not shift the response times of a database — and at the same time the reason why a class without a separate fabric must not run shared datastores.

PC-S32: 3 Gbit/s uplink without separate storage fabric — shared datastores are not permitted on this class, and without a shared datastore there is no automatic restart after a host failure.

0505Maintenance

Announced, rolling, host by host

Firmware and hypervisor maintenance requires a host to be emptied beforehand. In a cluster, the guests migrate away and no one notices the window. On a single host, the same window means downtime — this is the second reason for the minimum cluster size, alongside automatic restart.

ENTRONYX Managed vSphere: Wed 02:00–06:00 CET, rolling host by host, announcement 14 days in advance · lead time for changes 48 hours, in the “Platform and guest operations” level 24 hours

Patch boundaryPlatform operations

We keep up to date

  • Hypervisor
  • BIOS and firmware
  • Fabric switches
  • Storage controllers

You keep up to date

  • Guest operating system
  • Middleware
  • Application
  • Application data

Firmware maintenance requires a host evacuation. Without a second host in the cluster, this means downtime of up to 45 minutes per maintenance window.

Escalation: NOC › Platform engineer on duty › Infrastructure on-call management

What a four-tier cluster does

Management, hosts, storage, vRack — this is the order in which a Private Cloud is built, and the order in which it falls apart in the event of a fault. The circuit diagram shows case ENTRONYX Managed vSphere; the other 3 stacks differ in the minimum number of hosts the second tier carries.

Diagram of the four layers under ENTRONYX Managed vSphere

Management, hosts, storage and vRack with the guaranteed limits and restrictions

Topology

Schematic, not to scale · 2–32 hosts

Architecture of a cluster under ENTRONYX Managed vSphere

01 · MANAGEMENT02 · HOSTS03 · STORAGE04 · VRACKENTRONYX Managed vSphereDedicated vCenter per customer, API access, SSO against yourDirectoryLICENCE€9.90 per core and month$11.48 per core and monthMinimum 16 cores per socketControl pathCluster: 2 to 32 hostsHost 1Guest VMsHypervisorLocal NVMeHost 2Guest VMsHypervisorLocal NVMeHost 32Guest VMsHypervisorLocal NVMeStorage fabric — separated from guest trafficNVMe Performance120,000 IOPS0.4 ms p99€0.1090 / GB$0.1264 / GBfrom 2 TBNVMe Standard45,000 IOPS0.9 ms p99€0.0720 / GB$0.0835 / GBfrom 1 TBCapacity9,000 IOPS4.0 ms p99€0.0290 / GB$0.0336 / GBfrom 8 TBArchive900 IOPS25.0 ms p99€0.0068 / GB$0.0079 / GBfrom 20 TBvRack1 Gbit/s · included10 Gbit/s · €39.0010 Gbit/s · $45.2425 Gbit/s · €119.0025 Gbit/s · $138.0450 Gbit/s · €219.8350 Gbit/s · $255.00100 Gbit/s · €421.49100 Gbit/s · $488.93Public Cloud & Bare MetalInstances, dedicated serverswithout transit costs
  • Guest layer — VMs, vRack traffic
  • Platform layer — Hypervisor, local NVMe
  • vRack — Layer 2, no transit costs
  • Storage fabric — separated from guest traffic

Storage and guest traffic deliberately run on separate paths: datastores are attached to the fabric, guests to the vRack. Classes without a separate fabric — such as PC-S32 with a 2 Gbit/s uplink — are therefore not approved for shared datastores.

Cluster layers under ENTRONYX Managed vSphere with the limits guaranteed in the catalogue. All amounts net.

Cluster layers under ENTRONYX Managed vSphere
LayerComponentGuarantee and limit
01 · ManagementENTRONYX Managed vSphereDedicated vCenter per customer, API access, SSO against your directory
Maintenance windowsWed 02:00–06:00 CET, rolling host by host, announcement 14 days in advance
Licensing€9.90$11.48 per core and month, minimum purchase 16 cores per socket
02 · hostsCluster sizeminimum 2, maximum 32 hosts
Permitted classesPC-M64 · PC-M64i · PC-L128 · PC-X256
vCPU commitmentUpper limit of the respective host class, never more generous
03 · StorageDatastore NVMe Performance120,000 IOPS · 0.4 ms p99 · €0.1090$0.1264 per GB and month · from 2 TB · Triply replicated across two fire zones of the location
Datastore NVMe Standard45,000 IOPS · 0.9 ms p99 · €0.0720$0.0835 per GB and month · from 1 TB · Triply replicated across two fire zones of the location
Datastore Capacity9,000 IOPS · 4.0 ms p99 · €0.0290$0.0336 per GB and month · from 8 TB · Erasure coding 8+2 in the location, cache triply mirrored
Datastore Archive900 IOPS · 25.0 ms p99 · €0.0068$0.0079 per GB and month · from 20 TB · Erasure coding 8+2, second copy in another EU region
04 · vRackvRack 1 Gbit/sincluded in the host price — Isolated Layer 2 network across all locations.
vRack 10 Gbit/s€39.00$45.24 per month — For storage replication and database clusters.
vRack 25 Gbit/s€119.00$138.04 per month — Dedicated fabric for HPC and hypervisor clusters.
vRack 50 Gbit/s€219.83$255.00 per month — For distributed storage pools whose write path runs over the private network.
vRack 100 Gbit/s€421.49$488.93 per month — Highest expansion stage for clusters with synchronous replication between fire compartments.

Limitations

ENTRONYX Managed vSphere
HA requires a shared datastore. Without a booked datastore class, nothing restarts automatically — it remains a manual recovery from the backup.

Where the tenant boundary lies

In the Public Cloud, the boundary between two customers runs in the hypervisor of a host that both occupy. This is a robust boundary — it is certified, tested and supports regular operations. However, it is a boundary in software.

In the Private Cloud, it lies one tier lower: a host does not carry any third-party guests because none are assigned to it. How you isolate virtual machines from each other on it is up to you — via separate network segments, roles and, for stacks with their own management tier, via a management instance that belongs exclusively to you.

As far as network separation is concerned, responsibility remains shared: we provide the segmentation and rule framework, you set the specific rules. This row is therefore further up in the matrix under “shared” and not under our name.

Six pages, six decisions

This overview answers whether the Private Cloud is the right fit. What needs to be decided next — stack, size class, storage, recovery tier — is detailed on its own page with the complete limits. The metric on each card tells you whether the journey there is worth it.

  • Managed vSphere

    What HA (automatic restart), DRS (load balancing) and vMotion (moving running machines) actually do in operations — and what licensing per core costs compared to licensing per socket.

    Licence rate
    €9.90$11.48
    per core and month · cluster from 2 hosts, per host from €1,498.20$1,737.91
    View Managed vSphere
  • Hyperconverged

    How much raw capacity remains after mirroring or erasure coding (distribution with parity blocks instead of a full copy) and from which cluster size the protection mode changes.

    Usable from three hosts
    47%
    Two-way mirroring (RF2) with 3 to 5 hosts · up to 76% from 18 hosts · per host from €1,690.20$1,960.63
    View Hyperconverged
  • Certified SAP nodes

    Which HANA size class fits which dataset, how the volume layout is created and what an acceptance report objects to.

    Log write latency
    310 µs
    measured during acceptance run · guaranteed ≤ 1000 µs · licence per host and month
    View Certified SAP nodes
  • Managed dedicated hosts

    Who patches which layer, when escalation happens and what lead time a change needs — level by level.

    Initial response P1
    15 minutes
    in the “Platform and guest operations” tier · P1 and P2 around the clock, P3 Mon–Sat 08:00–20:00
    View Managed dedicated hosts
  • Datastores

    Which IOPS and latency commitment applies per class, under which condition it applies and from what quantity it is billed.

    IOPS per datastore
    120,000
    Datastore NVMe Performance · 0.4 ms latency p99 · commitment per datastore, not per virtual machine
    View Datastores
  • Disaster recovery

    Which recovery point (RPO) and recovery time (RTO) each level guarantees, how far away the target region must be and what the recovery test includes.

    Best recovery point
    15 minutes
    Asynchronous replication · Recovery in 120 minutes · 3 levels from nightly backup to 15-minute replication
    View Disaster recovery

ENTRONYX HCI and ENTRONYX Managed vSphere share the same host classes and the same network connection; they differ in where the storage is located: the hyperconverged infrastructure places it in the nodes themselves, managed vSphere attaches a shared datastore alongside. If you haven't decided yet, you will find the calculation on both pages — they list the same classes with a different licence rate.

The price applies per host, the minimum size per stack

The price of a managed host is made up of the bare metal, platform operations and the licence for the chosen stack. How many virtual machines run on it does not change this — the limit is set by the host's cores and memory, not by a count of the guests.

The range spans from €510.59$592.28 to €11,130.78$12,911.70 per host and month: at the bottom PC-S32 under ENTRONYX KVM Platform, at the top PC-X256 under ENTRONYX HCI. Between both ends lie 16 versus 384 physical cores and two licence models that handle cores differently.

Both amounts apply per host. ENTRONYX Managed vSphere requires 2 hosts, ENTRONYX HCI 3 — not as a sales rule, but because an automatic restart needs a second host and the distributed storage pool needs a quorum, i.e. a majority of reachable hosts that decides on the valid data state. The table therefore lists both for each stack.

Not included in the host price are datastores (from €0.0068$0.0079 per GB and month, up to €0.1090$0.1264), disaster recovery and the operations levels above platform operations. Platform operations itself costs nothing extra — it is already included in the host price.

All amounts net. The entry level corresponds to €607.60$704.81 incl. 19% VAT.

The licence depends on the stack, not the host: with licensing by cores, a consolidation host pays the same as two smaller ones with the same number of cores; with licensing by sockets, it halves the licence costs. Which model is cheaper for your setup therefore depends on the class — the calculation for this is on the two stack pages.

The complete calculation including datastore, recovery level and term is in the configurator. It calculates with the same rates as this table.

Four stacks in a table

Licence, hosts per cluster, smallest host class, price per host and minimum cluster — each row opens the configurator
Entry price per host and smallest permitted cluster, net and without datastore — per virtualisation stack
StackLicenceHostsSmallest host classPer host fromMinimum cluster fromConfigurator or request
ENTRONYX KVM PlatformOpen hypervisor on libvirt, licensed per socket instead of per core.€49.00$56.84per socket and month1 – 16PC-S3216 cores · 5 classes approved€510.59$592.28€510.59$592.281 × PC-S32Open
ENTRONYX Managed vSpherevCenter-managed cluster with HA, DRS and vMotion — licence per core.€9.90$11.48per core and month2 – 32PC-M6448 cores · 4 classes approved€1,498.20$1,737.91€2,996.40$3,475.822 × PC-M64Open
ENTRONYX HCIHyperconverged: computing power and storage in the same host, licence per core.€13.90$16.12per core and month3 – 24PC-M6448 cores · 4 classes approved€1,690.20$1,960.63€5,070.60$5,881.903 × PC-M64Open
ENTRONYX SAP CertifiedCertified HANA nodes, licensed per host — without overcommitment.€1,290.00$1,496.40per host and month1 – 8PC-M6448 cores · 4 classes approved€2,313.00$2,683.08€2,313.00$2,683.081 × PC-M64Request

The host price, item by item

A managed host costs more than a server you operate yourself. The difference is not a markup on the hardware: it consists of platform operations and licence. The box breaks down PC-M64 under ENTRONYX Managed vSphere into these items — using the amounts from the same catalogue that the configurator uses.

What follows from the pricing structure

Four points with evidence from the catalogue: hardware, host and licence, fees, billing
  • The hardware is a separate item

    In the host price of PC-M64, the machine itself is listed at €844.00$979.04 net per month — Base configuration, without hypervisor, licence and updates. The surcharge for the managed host is not a markup on the hardware, but platform operations and licence.

    Proof: Catalogue: hardware item PC-M64, €844.00$979.04 net

  • Host and licence are two lines, not a package price

    The host is on the balance sheet at €1,023.00$1,186.68, the licence next to it at €9.90$11.48 per core and month — you see what the operations cost, and you see what the licence costs. What is included in the host price is broken down by the box “What our amount consists of” into bare metal and platform operations.

    Proof: Licence per core and month openly disclosed

  • No management fee, no setup fee

    Neither a fee per cluster nor a one-off setup fee. The host price is the price; the initial response for P1 in 30 minutes is included.

    Proof: Catalogue: setupNet 0, platform operations 0 €$ additional

  • Billing per month, not per hour

    We only bill managed hosts per month. If you need computing power for a few days, the Public Cloud is the right choice: an hourly rate applies there.

    Proof: Catalogue: host classes with monthly amount

Start small, on regular terms

A trial here is not a separate offer but the smallest contract: one host, a one-month term, the same rates as in production. What applies is set out in four lines — with the section cited wherever it comes from the Terms and Conditions.

What applies to the trial period

Billing, Setup, Term, First invoice — with reference in the Terms and Conditions
Billing
Per host and month, not per hour. A managed host is an allocated device; switching it off does not reduce the amount.
Setup
No setup fee: €0.00$0.00 per host, in all 5 host classes.
Term
One month, after which the contract is renewed for one month at a time. You can cancel with one day's notice to the end of the term, including via the function in the customer panel. Section 11 of the Terms and Conditions
First invoice
The monthly amount is pro-rated from the day of provisioning. Billing is monthly at the end of the month. Section 9 para. 1 Terms and Conditions
  • One host with shared datastore

    1 × PC-M64 · Managed dedicated hosts

    48 cores · 232 GB allocatable · Düsseldorf

    Datastore NVMe Standard, 1 TB

    Monthly net

    €1,145.73$1,329.05

    An automatic restart after a host failure only takes effect from the second host. The shared datastore, which it also requires, is already included in this entry-level option.

  • The smallest class with local datastores

    1 × PC-S32 · Managed dedicated hosts

    16 cores · 140 GB allocatable · Düsseldorf

    Local datastores in the host, included in the host price

    Monthly net

    €510.59$592.28

    PC-S32 has no separate storage fabric and therefore does not support a shared datastore — an automatic restart after a host failure is not available in this class, even with a second host.

End of contract and price guarantee

How a contract ends and how long a price holds are governed by the Terms and Conditions in the same way for all product lines — including the Private Cloud. Here are four sentences on each, with the section where the binding wording can be found.

End of contract

Four sentences with matches — § 11 and § 12
  1. Unless otherwise agreed, a contract runs for one month and renews for a further month. § 11 para. 1
  2. You can cancel monthly contracts with one day's notice to the end of the term, contracts for 12 or 24 months with 30 calendar days' notice — otherwise they renew for twelve months. § 11 para. 2
  3. Cancellation requires text form; the designated function in the customer panel meets this requirement. § 11 para. 4
  4. After the contract ends, your data remains accessible for 30 calendar days; after that, it is irretrievably deleted. § 12 para. 2 and 4

Exact wording: § 11 Term and termination · § 12 Backup and data return

Price guarantee

Four sentences with matches — § 8
  1. The agreed price applies for the entire current contract period; an increase within the period is excluded. § 8 para. 2
  2. A price change takes effect at the beginning of the next period at the earliest and is announced in text form at least 90 calendar days in advance. § 8 para. 3
  3. If you object within 30 calendar days, the contract ends at the expiry of the current period without the need for cancellation. § 8 para. 4
  4. Term discounts — 5% for 12, 8% for 24 months — apply to the monthly net fees; if the contract ends early for reasons attributable to you, the discount for the months used will be billed retroactively. § 8 para. 6

Exact wording: § 8 Prices and price changes

Summarised. The wording of the Terms and Conditions is authoritative.

What this setup delivers

What distinguishes the Private Cloud from the Public Cloud and bare metal — each with the value by which it can be verified, and the condition under which it applies.

  • Fixed allocation instead of quota

    Upper limit vCPU per core, PC-M646

    A managed host carries exclusively your guests. The upper limit for vCPU per physical core is an upper limit and not a target value — nothing is placed above it, not even briefly.

  • Memory is not overcommitted

    Memory overcommitment, PC-M640%

    Ballooning is excluded in the production classes: what is allocated to a guest is physically available. The gained memory would not be worth the latency it costs under load.

  • The hypervisor is our layer

    Initial response P1, around the clock30 minutes

    Firmware, BIOS, hypervisor, fabric switches and storage controllers are part of platform operations, and this is included in every managed host — not bookable as an additional tier.

  • Latency as a commitment, not as a measured value

    Latency p99, Datastore NVMe Performance0.4 ms

    Each datastore class carries an upper limit for the p99 latency — the response time that 99 out of 100 accesses fall below — and the condition under which it applies. Where the condition does not apply, the worse value is shown next to it.

  • Recovery with guaranteed state

    Recovery point, Asynchronous replication15 minutes

    Asynchronous replication transfers every 15 minutes to a second location in the same country. Logical errors are transferred as well — the tier does not replace a backup.

  • Certification with measurement report

    Log write latency, 4 KB, measured310 µs

    For certified SAP nodes, an acceptance protocol is available per node. Limit value and measured value stand side by side; any change to RAM or datastore suspends the commitment until the new protocol.

Three cases from operations

No names, no quotes, no logos. Each case states the initial situation, the chosen setup — including the question of why it did not belong in the Public Cloud — and a verifiable metric.

  • Manufacturing

    ERP with acceptance requirement

    Initial situation

    A HANA production system must run against an acceptance protocol. In the Public Cloud, this commitment cannot be made: the certification depends on a named configuration, and shared capacity changes it with every placement.

    Decision

    ENTRONYX SAP Certified on a dedicated node, vCPU one-to-one with the physical core, separate volumes for data, log and shared. The price of this specification is included in the contract: any change to memory or datastore suspends the commitment until a new acceptance protocol is issued.

    Result

    310 µs

    Log write latency, 4 KB in the acceptance run, limit ≤ 1000 µs

    How it's built — ERP with acceptance requirement

  • Public administration

    Business application with a second domestic location

    Initial situation

    In the event of a location failure, an application may lose a maximum of 15 minutes of work. The Public Cloud was ruled out here because the storage of individual blocks cannot be guaranteed to a specific location.

    Decision

    ENTRONYX Managed vSphere with the tier “Asynchronous replication” to a second location in the same country. Logical errors are replicated as well — the tier complements the daily backup, it does not replace it.

    Result

    15 minutes

    Guaranteed recovery point, Asynchronous replication

    How it's built — Business application with a second domestic location

  • Software and services

    Platform with predictable base load

    Initial situation

    An application platform runs around the clock at approximately the same load and grows in steps. In the Public Cloud, this base load is paid per allocated vCPU (€16.69$19.36 per vCPU and month), in the Private Cloud per physical core (€31.21$36.20) — and the cluster grows in hosts, not in instance sizes.

    Decision

    ENTRONYX HCI from 6 nodes: computing and storage are in the same device, the cluster grows by individual nodes. Below this size, the pool runs mirrored instead of encoded — this costs usable capacity.

    Result

    62%

    Usable share of raw capacity from 6 nodes, erasure coding 4+2

    How it's built — Platform with predictable base load

Questions before ordering

Questions that are actually asked in sales and operations. Where a commitment has a condition, the condition is in the same answer.

What is a Private Cloud, and how much does it cost per month?

A Private Cloud is a cloud on dedicated hosts that carry only your virtual machines; the underlying hypervisor is operated by ENTRONYX CLOUD in data centres in Germany. It differs from the Public Cloud through the fixed allocation of hardware, and from Bare Metal through operations up to the guest boundary.

Billing is per host and month: hardware, platform operations and stack licence, plus datastore and network. The range per host is from PC-S32 under ENTRONYX KVM Platform to PC-X256 under ENTRONYX HCI; the amounts are shown in the metric “Per host from” in the hero section, in the pricing table under “Pricing structure” and in the quick configurator.

How quickly does support respond if a host fails?

An outage (P1) receives an initial response in 30 minutes, around the clock, in the Platform operations, which is included in every managed host; from the “Platform and guest operations” level it is 15 minutes. Initial response means: a human has accepted the report, classified it and reported back the processing status — we do not guarantee a resolution time. Reports are made via the ticket in the account; a change without an outage requires the lead time of the operations level, in the Platform operations 48 hours.

What is the term, and how do I cancel?

Without a term agreement, the contract runs for one month and renews for another; terms of 12 or 24 months are paid in advance and you receive a 5% or 8% term discount respectively. You can cancel monthly contracts with one day's notice to the end of the term, contracts for 12 or 24 months with 30 calendar days' notice — otherwise they renew for twelve months. After the contract ends, your data remains accessible for 30 calendar days; after that, it is irretrievably deleted.

Do I need an account to order?

Not for prices, the configurator and the cart — all three are open without signing in. The account is created at checkout with account type, contact, email address and password; the billing address follows with the first order.

An account with ENTRONYX CLOUD is free of charge, and there is no setup fee for a cluster. The items on the statement are billed — monthly or in advance for the selected term.

What happens after the order?

After checkout, we equip the hosts, cable the fabric and sign off the cluster services; this takes 3 to 5 working days. Handover includes the access data for the management plane and the operations manual.

The cluster will then appear in your account under “Account › Services”, and the invoice is also located there.

How many hosts do I need as a minimum?

The stack decides this, not the size of your environment. ENTRONYX KVM Platform runs from 1 host, ENTRONYX Managed vSphere requires 2, ENTRONYX HCI 3.

For vSphere and HCI, the reason is the same: an automatic restart after a host failure requires a second host to take it over, and a datastore that both can see; the hyperconverged pool requires a majority of reachable hosts for this. Below this limit, there is no high availability — not even on a small scale.

Under KVM, one host is enough; automatic restart is only available from the second.

Is a host billed by the hour?

No. A managed host is billed monthly because it is assigned as a device and does not come from a pool. Switching it off does not reduce the amount. You pay for a term of 12 or 24 months in advance, with the first invoice.

If you size for the daily peak, you therefore pay for it at night and at the weekend too. For daily fluctuating loads, the Public Cloud is the right fit; the “Cross-check” section on this page explains the case in plain text.

How is the virtualisation licensed?

Varies per stack. ENTRONYX KVM Platform bills per socket and month, ENTRONYX Managed vSphere per core and month, ENTRONYX HCI also per core.

When licensing by cores, a minimum purchase per socket applies: below 16 cores, this number is still charged. Small sockets are therefore not worthwhile under such a model.

How many virtual machines you run on a host does not change the licence. The limit is set by the cores and memory of the host.

Do I get my own vCenter?

Yes. ENTRONYX Managed vSphere provisions a vCenter instance in your tenant, not a shared one. Access includes the API and authentication against your directory.

What is not possible with this: a custom-built hypervisor state, your own kernel below the guest, or a firmware of your choice. These layers are our responsibility — that is the core of the offering and at the same time its limit.

Who patches which layer?

In platform operations, which is included in every managed host, we patch Hypervisor, BIOS and firmware, fabric switches, storage controllers. Guest system, middleware and application remain with you.

If you want to push the limit further up, book one of the two operating levels above it. Guest patches are only applied to the images we deliver — custom-built images remain your responsibility.

Is memory overcommitted?

Not in the production classes. For PC-M64 and all larger classes, the permitted memory overbooking is 0%: what is allocated is physically available.

An upper limit per physical core applies to vCPUs — for PC-M64 it is 6. It is an upper limit and not a target value: nothing is placed above it, not even briefly.

The entry-level class is exempt from this; it is intended for development and staging environments and explicitly allows overbooking.

How do maintenance windows work?

Announced and rolling. For ENTRONYX Managed vSphere: Wed 02:00–06:00 CET, rolling host by host, announcement 14 days in advance. The hosts are evacuated one after the other, not together.

Firmware maintenance requires that a host can be emptied. Without a second host in the cluster, this means downtime per maintenance window — this is the second reason for the minimum cluster, alongside the automatic restart.

What happens if an entire location fails?

That depends on the booked tier. The strictest, Asynchronous replication, replicates every 15 minutes to a second location and guarantees a recovery point of 15 minutes and a recovery time of 120 minutes.

Every tier requires a target location at a minimum distance; which tier has a target for your location is stated on the recovery page. No tier replaces the backup, each complements it.

At which locations is the Private Cloud available?

At 2 locations in Germany, every host class is available.

Datastore classes and recovery tiers have their own location lists. A recovery tier needs a target location at a minimum distance and is therefore not available at every location.

Per host from · per month, net€510.59$592.28

Configure

Configure cluster or discuss sizing

The quick configurator adds your cluster to the cart with one click; the ENTRONYX CLOUD account is created at checkout. You add network, operations level and recovery in the flow, which adopts your selection with all values. If you prefer to discuss the sizing, write to us — we will call you back upon request.

Per host from
€510.59$592.28
Per host up to
€11,130.78$12,911.70
Host classes
5
Locations
2