PC-S
EntryOne host, local NVMe datastores, no shared storage. For development and acceptance environments where a maintenance window is not an incident.
Managed dedicated hosts from data centres in Germany: a physical host that belongs only to you, in 5 classes. Billed per host and month — bare metal and platform operations, plus the stack licence. We operate everything below your virtual machines: firmware, hypervisor, fabric and storage controllers; you operate everything in the guest. If the host fails, a human will respond in 30 minutes, around the clock. Configure where the boundary lies, how it shifts with the operations level, and what your cluster costs below.
All amounts net per month and host, plus 19% VAT., calculated for the Frankfurt location; the range goes up to €5,793.18$6,720.09. The host price covers bare metal and platform operations. Licence, datastore and disaster recovery are separate.
Twelve layers from the data centre to your data. Below the guest boundary we operate, from the guest onwards you operate, and in the layers in between both sides act in separate places. With the operations level, the operations boundary moves upwards. Choose the level, host class and quantity: the layer diagram shows who does what, and the balance calculates with the same code as the configurator.
Always in the host price
includedin the host price
Included in every managed host. We operate everything below the guest.
Your data at the top, the data centre at the bottom. The operations boundary moves with the level, the guest boundary remains fixed.
€1,023.00$1,186.68per host / month
48 Genoa cores with 12 memory channels — the most frequently booked production class.
€1,023.00$1,186.68net / month
1–16 hosts under ENTRONYX KVM Platform
Firmware maintenance requires a host evacuation. Without a second host in the cluster, this means downtime of up to 45 minutes per maintenance window.
You rent the same machine as under Bare Metal — plus the commitment that the hypervisor (the software that divides the host into virtual machines), firmware, fabric (the network between hosts and storage) and storage controllers are maintained by us. The surcharge is listed openly on the invoice because it is a service and not a margin.
One host, local NVMe datastores, no shared storage. For development and acceptance environments where a maintenance window is not an incident.
48 Genoa or Granite Rapids cores each, 10 Gbit fabric, no memory overcommit. The fit on which most productive clusters run — optionally AMD or Intel.
64 cores in one socket. Halves the licence costs per core in per-socket licence models compared to two smaller hosts.
384 cores and 1 TB RAM per host, connected in the cluster via a 25 Gbit fabric. For clusters that have to calculate per rack unit.

Processor, core count, clock speed, memory, drives and uplink come from the Bare Metal plan behind the class. They are not maintained twice in this table, but are derived from it — a hardware change takes effect here without any rework.
| Class | Processor | Cores / threads | Base / boost clock | Memory | Local NVMe | Uplink | Stock |
|---|---|---|---|---|---|---|---|
| PC-S32Entry point to your own virtualisation — datastores are local to the host. | EPYC 4584PX1 sockets · Zen 4 · 3D V-Cache · 5 nm | 16 / 3216 per socket | 4.2 GHz5.7 GHz | 128 GBDDR5-3600 (On-Die-ECC) | 2 × 960 GB NVMe Gen41.92 TB raw | 3 Gbit/s | In stock78% |
| PC-M6448 Genoa cores with 12 memory channels — the most frequently booked production class. | EPYC 9454P1 sockets · Zen 4 Genoa · 5 nm | 48 / 9648 per socket | 2.75 GHz3.8 GHz | 256 GBDDR5 ECC RDIMM | 2 × 1.92 TB NVMe (Datacenter Edition)3.84 TB raw | 1 Gbit/s | In stock61% |
| PC-M64iIntel counterpart with AMX — the class for SAP certification and inference on the CPU. | Xeon 6741P1 sockets · Granite Rapids · Intel 3 | 48 / 9648 per socket | 2.5 GHz3.8 GHz | 256 GBDDR5 ECC RDIMM | 4 × 1.92 TB NVMe (Datacenter Edition)7.68 TB raw | 1 Gbit/s | Limited stock44% |
| PC-L12864 cores in one socket — density without the detour via a second NUMA node. | EPYC 95541 sockets · Zen 4 Genoa · 5 nm | 64 / 12864 per socket | 3.1 GHz3.75 GHz | 512 GBDDR5-4800 ECC RDIMM | 2 × 3.84 TB NVMe7.68 TB raw | 5 Gbit/s | Limited stock33% |
| PC-X256Dual EPYC 9965, 1 TB RAM, 25 Gbit fabric. For clusters that do not wait. | 2× EPYC 99652 sockets · Zen 5c Turin Dense · 3 nm | 384 / 768192 per socket | 2.25 GHz3.7 GHz | 1 TBDDR5-5600 ECC RDIMM | 2 × 1.92 TB NVMe Gen5 (system)3.84 TB raw | 5 Gbit/s | Low stock21% |
The vCPU limit — the maximum number of virtual processor cores allocated per physical core — is an upper guarantee, not a target value: no placement occurs above this ratio, not even briefly. The monthly price is the sum of the bare metal price for the same configuration and platform operations. Licences for the virtualisation stack are deliberately not included — they are tied to the stack, not the host.
| Class | vCPU per core | Guaranteeable vCPUs | RAM for guests | RAM overcommit | Guests per host | Bare metal | Platform operations | Monthly net |
|---|---|---|---|---|---|---|---|---|
| PC-S32FORGE-32 | ≤ 8 : 1 | 128 | 112 GB16 GB hypervisor | 25%up to 140 GB | 120 | €220.16$255.39 | + €149.00$172.84 | €461.59$535.44 |
| PC-M64TITAN-96 (Genoa) | ≤ 6 : 1 | 288 | 232 GB24 GB hypervisor | 0% | 250 | €844.00$979.04 | + €179.00$207.64 | €1,023.00$1,186.68 |
| PC-M64iTITAN-96i | ≤ 6 : 1 | 288 | 232 GB24 GB hypervisor | 0% | 250 | €904.00$1,048.64 | + €189.00$219.24 | €1,093.00$1,267.88 |
| PC-L128TITAN-128 (Genoa) | ≤ 4 : 1 | 256 | 472 GB40 GB hypervisor | 0% | 400 | €660.50$766.18 | + €239.00$277.24 | €1,898.65$2,202.43 |
| PC-X256TITAN-768 | ≤ 4 : 1 | 1,536 | 960 GB64 GB hypervisor | 0% | 640 | €2,299.99$2,667.99 | + €389.00$451.24 | €5,793.18$6,720.09 |
Every class has a property that excludes it for certain projects. It is stated here in full and not in the small print, because it decides the selection.
Responsibility without access rights is a declaration of intent. The following division is enforced technically, not agreed organisationally: what one side is not entitled to is not unlocked for them.
Below the guest boundary, from a separate management network and fully logged.
From the management tier upwards, regardless of the operations level booked.

An operating model does not fail because of the technology, but because of the line nobody read. That is why the breakdown is provided here in full. In 2 out of 12 layers, the Private Cloud differs from the Public Cloud, and in 8 out of 12 from Bare Metal. The layer diagram in the operating model shows the Private Cloud per level; this table places it alongside the two neighbouring models.
We operate the layer and are liable for its outcome.
Both parties act in the same layer in separate areas.
You operate the layer; we have no access there.
| Layer | Public Cloud | Private Cloud | Bare Metal |
|---|---|---|---|
| Data centre, power, cooling | ENTRONYX CLOUD | ENTRONYX CLOUD | ENTRONYX CLOUD |
| Hardware and spare parts | ENTRONYX CLOUD | ENTRONYX CLOUD | ENTRONYX CLOUD |
| Firmware and BIOS | ENTRONYX CLOUD | ENTRONYX CLOUD | Customer |
| Hypervisor and cluster services | ENTRONYX CLOUD | ENTRONYX CLOUD | Customer |
| Storage fabric and datastores | ENTRONYX CLOUD | ENTRONYX CLOUD | Customer |
| Network segmentation and firewall rules | Shared | Shared | Customer |
| Capacity planning and placement | ENTRONYX CLOUD | Shared | Customer |
| Guest operating system | Customer | Shared | Customer |
| Middleware and application | Customer | Customer | Customer |
| Application data and classification | Customer | Customer | Customer |
| Access management and roles | Shared | Shared | Customer |
| Backup and recovery test | Shared | Shared | Customer |
The neighbouring models are for comparison, not as an offer on this page: Public Cloud takes capacity planning off your hands and gives you sole control of the guest system; Bare Metal gives you everything from the firmware upwards and takes nothing off your hands.
“Shared” is the only entry in the matrix that decides nothing on its own. Each of these layers has an edge — the sentence that decides who acts in the event of a fault.
We do not change any rules in your tenant, not even in the event of a fault. A rule that resolves an outage comes as a change request from you — otherwise no one would know why it is there afterwards.
The vCPU limit per class is a commitment, not a target value. We do not place above it — not even briefly and not even if a guest is waiting as a result.
A custom-built image is excluded from the availability commitment. This is not a penalty, but a consequence of the fact that we do not know its patch level.
We do not create or delete any accounts in your directory. A departed administrator retains their access until you revoke it.
A successful backup is no evidence of a successful recovery. The two only come together in the test, and the test requires your sign-off.

A cluster under ENTRONYX KVM Platform grows from 1 up to 16 hosts. ENTRONYX CLOUD operates the same five layers below the guest in each of them; initial response for outages 30 minutes, around the clock.
Operations · Rolling maintenance host by host
Platform operations included in the host price end at the guest boundary. Everything above that is a separate level with its own price. The matrix shows each layer against each level; a tick means that we keep that layer current and answer for it.
| Layer | Platform operationsin the host price | Platform and guest operationsfrom €729.00$845.64 | Full operationsfrom €2,579.00$2,991.64 |
|---|---|---|---|
| Hypervisor | |||
| BIOS and firmware | |||
| Fabric switches | |||
| Storage controllers | |||
| Guest operating system | only ENTRONYX images | ||
| Databases and middleware in the operations manual |
Platform operations
Remains with you
Change lead time 48 hours
Platform and guest operations
Remains with you
Change lead time 24 hours
Full operations
Remains with you
Change lead time 8 hours
The maintenance window depends on the virtualisation stack, not the bare metal: a host is patched when the cluster it resides in has its window. Firmware and hypervisor work is done on a rolling basis, host by host. That is why there is a notice period in each row. And that is why a cluster with only one host requires planned downtime instead of an evacuation — moving running guests to another host.

| Stack | Maintenance window and announcement | Host classes | Hosts per cluster |
|---|---|---|---|
| ENTRONYX KVM PlatformOpen hypervisor on libvirt, licensed per socket instead of per core. | Tue and Thu 02:00–05:00 CET, announcement 10 calendar days in advance | 5 | 1 – 16 |
| ENTRONYX Managed vSpherevCenter-managed cluster with HA, DRS and vMotion — licence per core. | Wed 02:00–06:00 CET, rolling host by host, announcement 14 days in advance | 4 | 2 – 32 |
| ENTRONYX HCIHyperconverged: computing power and storage in the same host, licence per core. | Tue 02:00–06:00 CET, rolling with data redistribution before each restart | 4 | 3 – 24 |
| ENTRONYX SAP CertifiedCertified HANA nodes, licensed per host — without overcommitment. | By arrangement per environment, 21 days lead time, outside your closing periods | 4 | 1 – 8 |
The lowest level is already included in the host price — for PC-S32, that is the €149.00$172.84 surcharge on the bare metal. If you move operations further up, you pay a base amount per environment — a flat rate, regardless of the number of hosts — and a smaller rate per host.
Included in every managed host. We operate everything below the guest.
in the host price
Limit: Firmware maintenance requires a host evacuation. Without a second host in the cluster, this means downtime of up to 45 minutes per maintenance window.
Configure this level — Platform operationsPlus guest patches, backup verification and alert rules per system.
€690.00$800.40Base per environment, plus €39.00$45.24 per host and month
Limit: Guest patches are only applied to images delivered by ENTRONYX. Custom-built images remain your responsibility and are excluded from the availability commitment.
Configure this level — Platform and guest operationsOperations up to the application, with change management and capacity planning.
€2,490.00$2,888.40Base per environment, plus €89.00$103.24 per host and month
Limit: Application operations include the services listed in the operations manual. In-house developments not listed are monitored but not modified.
Configure this level — Full operationsThe base fee applies once per environment, the host rate for each system within it. For a single host, the base fee makes up the majority of the amount. The host rate does not make up the majority in any level before 18 hosts. The amounts are shown next to the host price, not included in it.
| Tier | 1 Host | 3 Hosts | 8 Hosts | 16 Hosts |
|---|---|---|---|---|
| Platform operationsincluded in the host price | €0.00$0.00 | €0.00$0.00 | €0.00$0.00 | €0.00$0.00 |
| Platform and guest operations€690.00$800.40 + €39.00$45.24 per host | €729.00$845.64 | €807.00$936.12 | €1,002.00$1,162.32 | €1,314.00$1,524.24 |
| Full operations€2,490.00$2,888.40 + €89.00$103.24 per host | €2,579.00$2,991.64 | €2,757.00$3,198.12 | €3,202.00$3,714.32 | €3,914.00$4,540.24 |
Every operations level has its own escalation path and initial response time. The fastest commitment in the catalogue is 15 minutes for an outage — around the clock, every day of the year.
A productive service is unreachable or a layer in our responsibility has failed: host, fabric, datastore. An impending data loss also counts here, regardless of whether something is already down.
The service is running, but restricted: a host dropped from the cluster, redundancy lost, latency permanently above the commitment. A second failure would lead to P1.
Everything without impact on operations: change requests, capacity questions, information from the logs. For changes, the lead time of the operations level applies, not the initial response time.
The initial response time is measured from the receipt of the report, not from the start of processing. The same team receives the report at night as during the day: the NOC, the 24/7 staffed network operations centre.
| Tier | Initial response P1 | Initial response P2 | Coverage | Change lead time |
|---|---|---|---|---|
| Platform operations | 30 minutes | 4 hours | P1 around the clock, P2 and P3 Mon–Fri 08:00–18:00 | 48 hours |
| Platform and guest operations | 15 minutes | 2 hours | P1 and P2 around the clock, P3 Mon–Sat 08:00–20:00 | 24 hours |
| Full operations | 15 minutes | 1 hour | Around the clock via fixed phone number, named technical contact | 8 hours |
Escalation here means: the next level is actively brought in, not the report passed on. Whoever has reached a level does not lose the previous one. With an increasing operations level, the path becomes longer because it ends further up — not because it gets slower.
9 questions that regularly come up before ordering. The answers use the same catalogue values as the sections above.
Can't find your question? In the operating model, you can set the level, class and quantity to see who operates which layer.
A managed dedicated host is a physical server that only carries your virtual machines; ENTRONYX CLOUD operates the firmware, hypervisor, fabric and storage controllers in data centres in Germany, you operate everything in the guest. The monthly price is the bare metal price of the same configuration plus platform operations; stack licence, datastore and disaster recovery are added.
Starting at PC-S32, per host and month, net, without stack licence€461.59$535.44
In data centres in Germany, at 2 locations; every class is available at each of them. A cluster is located entirely at one location, a second is only added by the recovery tiers.
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.
We operate everything below your virtual machines: Hypervisor, BIOS and firmware, Fabric switches and Storage controllers. Guest operating system, Middleware, Application and Application data remain with you as long as you do not book a higher operations tier. In the shared layers in between, such as network segmentation and access management, both sides act in separate places.
Five classes, from PC-S32 with 16 cores and 128 GB memory to PC-X256 with 384 cores and 1 TB. The monthly price is the bare metal price of the same configuration plus platform operations; stack licence, datastore and disaster recovery are added. There is no setup fee for any class.
Entry with PC-S32, per host and month, net€461.59$535.44
Three: “Platform operations” is included in the host price, “Platform and guest operations” additionally takes over guest patches on ENTRONYX images, backup verification and alert rules per system, “Full operations” reaches into the application. The levels above cost a base amount per environment plus a smaller rate per host.
“Platform and guest operations” for one host, net per month€729.00$845.64
In the maintenance window of the virtualisation stack, rolling host by host; under ENTRONYX KVM Platform this means: Tue and Thu 02:00–05:00 CET, announcement 10 calendar days in advance. Before any intervention in firmware or hypervisor, the guests are moved to other hosts in the cluster and continue running there. If there is only one host in the cluster, a firmware intervention means a downtime of up to 45 minutes per maintenance window.
In 30 minutes a human will respond, around the clock, even in the “Platform operations” level, which is included in the host price. From “Platform and guest operations” it is 15 minutes. Initial response means: The report has been accepted, classified and the processing status reported back; we do not guarantee a resolution time.
Yes: You have the guest console and full rights in the guest system, regardless of the booked operations level, as well as the management plane of the stack. The management processor, hypervisor shell, fabric and storage controller, on the other hand, can only be accessed by ENTRONYX CLOUD, from a separate management network and fully logged. The division is technically enforced: What one side is not entitled to, is not unlocked for it.
The configurator guides you through host class, virtualisation stack, datastore, network, operational level and term, and lists each item individually. If you need the breakdown in writing beforehand: the matrix above is the exact text that goes into the service description.