Skip to content

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.

Initial response to failure
30 minutes
15 minutes from level Platform and guest operations
Host classes
5
from €461.59$535.44 per month, without stack licence
Operational levels
3
Platform operations in the host price, above that up to Full operations
Layers
12
each assigned to a site

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

  • Hypervisor, BIOS and firmware, fabric switches, storage controllerspatched and operated by us
  • Initial response 30 minutesin case of failure, around the clock
  • no setup feeon all host classes
  • 1 to 16 hosts per clusterunder ENTRONYX KVM Platform
  • Licence €49.00$56.84 per socket and monthadded to the host price

Operations level

includedin the host price

Operations level

Included in every managed host. We operate everything below the guest.

Who operates which layer

Your data at the top, the data centre at the bottom. The operations boundary moves with the level, the guest boundary remains fixed.

  1. Application data and classificationYou
  2. Middleware and applicationYou
  3. Guest operating systemYou
  4. Access management and rolesSharedWe do not create or delete any accounts in your directory.
  5. Backup and recovery testSharedA successful backup is no evidence of a successful recovery.
  6. Capacity planning and placementSharedThe vCPU limit per class is a commitment, not a target value.
  7. Network segmentation and firewall rulesSharedWe do not change any rules in your tenant, not even in the event of an incident.
  8. Operations boundary — Platform operations: from here upwards you operate
  9. Guest boundary — included in the host price up to here
  10. Storage fabric and datastoresENTRONYX CLOUD
  11. Hypervisor and cluster servicesENTRONYX CLOUD
  12. Firmware and BIOSENTRONYX CLOUD
  13. Hardware and spare partsENTRONYX CLOUD
  14. Data centre, power, coolingENTRONYX CLOUD

Host class

€1,023.00$1,186.68per host / month

Host class

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.

Net per month after discount€1,018.40$1,181.34€1,211.90$1,405.79 incl. VATSummary

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.

Classes
5
in 4 series
Locations
2
varies by class
Entry
€461.59$535.44
PC-S32, net per month
Setup
€0.00$0.00
on all classes

PC-S

Entry

One host, local NVMe datastores, no shared storage. For development and acceptance environments where a maintenance window is not an incident.

PC-M

Production

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.

PC-L

Density

64 cores in one socket. Halves the licence costs per core in per-socket licence models compared to two smaller hosts.

PC-X

Dual-socket

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.

Single-socket host vertically from above: a heatsink in the middle, six memory modules to the left, six to the right, the row of fans at the top, the power supply units at the bottom, the rack rails on the left and right.
One socket, 12 memory channels, 256 GB: PC-M64 is a single NUMA node, meaning a memory area that every core can access at the same speed. After the hypervisor's share, 232 GB remain for guests — no VM on this class will be larger. The other classes are listed in the table below.

Specifications per class

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.

Specifications per host class. Memory calculated in binary, drive capacity in decimal — just as the drives are specified.
ClassProcessorCores / threadsBase / boost clockMemoryLocal NVMeUplinkStock
PC-S32Entry point to your own virtualisation — datastores are local to the host.EPYC 4584PX1 sockets · Zen 4 · 3D V-Cache · 5 nm16 / 3216 per socket4.2 GHz5.7 GHz128 GBDDR5-3600 (On-Die-ECC)2 × 960 GB NVMe Gen41.92 TB raw3 Gbit/sIn stock78%
PC-M6448 Genoa cores with 12 memory channels — the most frequently booked production class.EPYC 9454P1 sockets · Zen 4 Genoa · 5 nm48 / 9648 per socket2.75 GHz3.8 GHz256 GBDDR5 ECC RDIMM2 × 1.92 TB NVMe (Datacenter Edition)3.84 TB raw1 Gbit/sIn stock61%
PC-M64iIntel counterpart with AMX — the class for SAP certification and inference on the CPU.Xeon 6741P1 sockets · Granite Rapids · Intel 348 / 9648 per socket2.5 GHz3.8 GHz256 GBDDR5 ECC RDIMM4 × 1.92 TB NVMe (Datacenter Edition)7.68 TB raw1 Gbit/sLimited stock44%
PC-L12864 cores in one socket — density without the detour via a second NUMA node.EPYC 95541 sockets · Zen 4 Genoa · 5 nm64 / 12864 per socket3.1 GHz3.75 GHz512 GBDDR5-4800 ECC RDIMM2 × 3.84 TB NVMe7.68 TB raw5 Gbit/sLimited 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 nm384 / 768192 per socket2.25 GHz3.7 GHz1 TBDDR5-5600 ECC RDIMM2 × 1.92 TB NVMe Gen5 (system)3.84 TB raw5 Gbit/sLow stock21%

Guarantees and price breakdown

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.

Commitments per class and the breakdown of the monthly price. All amounts net per month and host, calculated for the Frankfurt location, plus 19% VAT. Excluding stack licence, excluding datastore.
ClassvCPU per coreGuaranteeable vCPUsRAM for guestsRAM overcommitGuests per hostBare metalPlatform operationsMonthly net
PC-S32FORGE-32≤ 8 : 1128112 GB16 GB hypervisor25%up to 140 GB120€220.16$255.39+ €149.00$172.84€461.59$535.44
PC-M64TITAN-96 (Genoa)≤ 6 : 1288232 GB24 GB hypervisor0%250€844.00$979.04+ €179.00$207.64€1,023.00$1,186.68
PC-M64iTITAN-96i≤ 6 : 1288232 GB24 GB hypervisor0%250€904.00$1,048.64+ €189.00$219.24€1,093.00$1,267.88
PC-L128TITAN-128 (Genoa)≤ 4 : 1256472 GB40 GB hypervisor0%400€660.50$766.18+ €239.00$277.24€1,898.65$2,202.43
PC-X256TITAN-768≤ 4 : 11,536960 GB64 GB hypervisor0%640€2,299.99$2,667.99+ €389.00$451.24€5,793.18$6,720.09

Limits per class

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.

PC-S32
3 Gbit uplink without a separate storage fabric. Shared NFS or iSCSI datastores are not permitted on this class so that replication and guest traffic do not share the same line. Without a shared datastore, there is no automatic HA restart.
Configure in the operating model — PC-S32
PC-M64
One socket, one NUMA node: VMs over 232 GB RAM no longer fit on this class. For wider single VMs, PC-L128 or PC-X256 is the right fit.
Configure in the operating model — PC-M64
PC-M64i
Live migration is only guaranteed between hosts of the same CPU generation. A mixed cluster of PC-M64 (AMD) and PC-M64i (Intel) does not migrate during operations.
Configure in the operating model — PC-M64i
PC-L128
The boost ends at 3.75 GHz — the class wins on width, not on clock speed. Loads that depend on single threads run faster on PC-S32 with 5.7 GHz.
Configure in the operating model — PC-L128
PC-X256
Two sockets mean two NUMA nodes. VMs over 480 GB RAM or over 192 vCPU exceed one node and lose around 12% memory bandwidth — with licences per core, this host also pays for 384 cores.
Configure in the operating model — PC-X256

Which access each side has

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.

Only ENTRONYX CLOUD

Below the guest boundary, from a separate management network and fully logged.

Management processor (BMC/IPMI)
From a separate management network that is not connected to any customer port. Firmware, boot order and remote console of the bare metal.
Hypervisor shell
Console and SSH of the hypervisor, for maintenance, evacuation and troubleshooting below the guest boundary.
Fabric and storage controllers
Switch configuration, zoning (the mapping of which host sees which storage) and the controllers of the datastores. Usage and latency are visible, not the content of the volumes.
Platform telemetry
Utilisation, temperature, drive error counters, packet loss on the uplink. Basis for alerts and capacity reports.

Only you

From the management tier upwards, regardless of the operations level booked.

Management plane of the stack
vCenter, web console or REST API in your own tenant, with authentication against your directory.
Guest console and guest root
Screen access to every VM and full rights in the guest system, regardless of the booked operations level.
Segmentation in the tenant
VLAN tailoring, rule sets and address allocation within the ranges assigned to you.
Snapshots, clones and templates
Creation and restoration via interface or API, without a change request and without a maintenance window.
Rear of a host in the rack: two power supply units with plugged-in cables, the fan grilles, a network card with two fibres, next to it the dedicated management port with a light grey cable going upwards.
The light grey cable is the management network: the management processor (BMC) is connected to it and not to any customer port. Firmware, boot order and remote console run over it — ENTRONYX CLOUD reaches them, you do not. Your uplinks are the two dark fibres.

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.

  • ENTRONYX CLOUD

    We operate the layer and are liable for its outcome.

  • Shared

    Both parties act in the same layer in separate areas.

  • Customer

    You operate the layer; we have no access there.

Division of responsibility per layer, compared across the three product lines. “Shared” means: both sides act in the same layer in separate places — what that means for each layer is explained below the table.
LayerPublic CloudPrivate CloudBare Metal
Data centre, power, coolingENTRONYX CLOUDENTRONYX CLOUDENTRONYX CLOUD
Hardware and spare partsENTRONYX CLOUDENTRONYX CLOUDENTRONYX CLOUD
Firmware and BIOSENTRONYX CLOUDENTRONYX CLOUDCustomer
Hypervisor and cluster servicesENTRONYX CLOUDENTRONYX CLOUDCustomer
Storage fabric and datastoresENTRONYX CLOUDENTRONYX CLOUDCustomer
Network segmentation and firewall rulesSharedSharedCustomer
Capacity planning and placementENTRONYX CLOUDSharedCustomer
Guest operating systemCustomerSharedCustomer
Middleware and applicationCustomerCustomerCustomer
Application data and classificationCustomerCustomerCustomer
Access management and rolesSharedSharedCustomer
Backup and recovery testSharedSharedCustomer

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.

The 5 shared layers, spelt out

“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.

Network segmentation and firewall rules

We
We operate the fabric, the uplinks and the edge filters of the location and separate your VLANs — the virtual network segments — from those of other tenants.
You
You tailor the segments within your tenant and maintain the rule sets between them.

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.

Capacity planning and placement

We
We provision the capacity of the location, place guests according to the agreed rules and report before a class runs short.
You
You decide on the number and size of the guests and when a host is added.

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.

Guest operating system

We
On our images, we apply kernel and security patches in the maintenance window, provided an operations level with guest operations is booked.
You
You are responsible for custom-built images, installed agents and any configuration above the package management.

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.

Access management and roles

We
We manage the roles of the management plane, connect your directory and log every administrative access on our side.
You
You assign the roles within your tenant and revoke them when people leave.

We do not create or delete any accounts in your directory. A departed administrator retains their access until you revoke it.

Backup and recovery test

We
We run the backups, monitor their results and provide the environment for the recovery test.
You
You identify the systems requiring protection, approve the recovery point and sign off on the test.

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.

Three racks from the front: every rack unit occupied by a server, all status lights green.

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

Who patches which layer — and when

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.

Patch responsibility per layer and operations tier. Tick: maintained by ENTRONYX CLOUD. Minus: your responsibility.
LayerPlatform operationsin the host pricePlatform and guest operationsfrom €729.00$845.64Full operationsfrom €2,579.00$2,991.64
Hypervisor
BIOS and firmware
Fabric switches
Storage controllers
Guest operating systemonly ENTRONYX images
Databases and middleware in the operations manual

Platform operations

Remains with you

  • Guest operating system
  • Middleware
  • Application
  • Application data

Change lead time 48 hours

Platform and guest operations

Remains with you

  • Middleware
  • Application
  • Application data

Change lead time 24 hours

Full operations

Remains with you

  • In-house developed applications
  • Application data

Change lead time 8 hours

When patching happens

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.

A host on telescopic rails pulled two-thirds out of the rack, the cover removed; the neighbours above and below sit flush, their status lights glowing green.
Any intervention in the firmware or hypervisor requires an empty host: while this host is open, the neighbours in the cluster carry its guests. Without a second host in the cluster, this means a downtime of up to 45 minutes per maintenance window.
Maintenance window per stack. All times in CET or CEST, announced by email to the registered technical contacts and in the customer area.
StackMaintenance window and announcementHost classesHosts 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 advance51 – 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 advance42 – 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 restart43 – 24
ENTRONYX SAP CertifiedCertified HANA nodes, licensed per host — without overcommitment.By arrangement per environment, 21 days lead time, outside your closing periods41 – 8

Operations scale with the number of systems, not their size

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.

Platform operations

Included

Included in every managed host. We operate everything below the guest.

in the host price

Initial response P1
30 minutes
Initial response P2
4 hours
Change lead time
48 hours
Coverage
P1 around the clock, P2 and P3 Mon–Fri 08:00–18:00

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 operations

Platform and guest operations

Plus guest patches, backup verification and alert rules per system.

€690.00$800.40Base per environment, plus €39.00$45.24 per host and month

Initial response P1
15 minutes
Initial response P2
2 hours
Change lead time
24 hours
Coverage
P1 and P2 around the clock, P3 Mon–Sat 08:00–20:00

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 operations

Full operations

Operations 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

Initial response P1
15 minutes
Initial response P2
1 hour
Change lead time
8 hours
Coverage
Around the clock via fixed phone number, named technical contact

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 operations

Operations costs by host count

The 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.

Monthly operations costs per level, net plus 19% VAT., excluding hosts, licences and datastores. Calculated as base per environment plus rate per host.
Tier1 Host3 Hosts8 Hosts16 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

Who you reach when something is down

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.

P1

Outage

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.

P2

Significant impairment

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.

P3

Request and change

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.

Initial response times per operations level. Measured from receipt of the report via the channel agreed for the level.
TierInitial response P1Initial response P2CoverageChange lead time
Platform operations30 minutes4 hoursP1 around the clock, P2 and P3 Mon–Fri 08:00–18:0048 hours
Platform and guest operations15 minutes2 hoursP1 and P2 around the clock, P3 Mon–Sat 08:00–20:0024 hours
Full operations15 minutes1 hourAround the clock via fixed phone number, named technical contact8 hours

The way up

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.

Platform operations

3 levels
  1. 01NOC
  2. 02Platform engineer on duty
  3. 03Infrastructure on-call management

Platform and guest operations

4 levels
  1. 01NOC
  2. 02Systems engineer on duty
  3. 03Named Service Manager
  4. 04Infrastructure on-call management

Full operations

4 levels
  1. 01Fixed phone number
  2. 02Technical Account Manager
  3. 03Operations management
  4. 04Technical management

Common questions before getting a managed host

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.

What are managed dedicated hosts, and how much does a host cost per month?

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

Set operations model and price

Where are the hosts located?

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.

Host classes and specifications

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.

What do you operate, and what remains with me?

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.

The boundary per operations level in the layer diagram

Which host classes are there, and how much does a host cost?

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

Specifications and price breakdown per class

Which operations levels are there?

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

Operations levels and costs per number of hosts

When are patches applied, and is my host down during this time?

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.

Who patches which layer, and when

How quickly do you react in the event of a failure?

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.

Response times and escalation paths per level

Do I have full access to my VMs, and what do you access?

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.

Which access each side has

from, per host net, without stack licence€461.59$535.44

Configure operations model

Clarify responsibilities first, then choose the host

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.

Host classes
5
from, without stack licence
€461.59$535.44
Layers
12
Operational levels
3 to Full operations