HANA S
PC-M64S/4HANA development, quality assurance, small secondary systems
- Memory
- 256 GB
- of which allocatable
- 232 GB
- vCPU 1:1
- 48
- Database up to
- 128 GB
€2,313.00$2,683.08
per month, net · host, platform operations and licence; datastore separate
SAP HANA Hosting from data centres in Germany: 4 size classes are approved — HANA S, HANA M, HANA L and HANA XL — on 4 of 5 host classes. Licensing is per host and month, not per core; the datastore is billed separately. Approved means: an audit report according to SAP HWCCT (Hardware Configuration Check Tool) is available for exactly this configuration — but not for any other combination.
Nodes from €2,313.00$2,683.08 net per month: host, platform operations and licence. The datastore — the storage cluster where the HANA volumes reside — is billed separately. Approval at 2 locations. A node failure (P1) receives an initial response in platform operations within 30 minutes, around the clock; questions and changes go via the ticket in the account to support according to the SLA, in the base tier with a response within 8 h to a critical case, available Mon–Fri 08:00–18:00.
The database size determines the class. The class determines the volume layout, datastore quantity and price — calculated using the same catalogue values as the data sheet below.
What your system currently occupies in the column store. SAP calculates the class at double this amount, because HANA needs the second half of the memory for the delta merge (incorporating new data into the column store) and for intermediate results.
Requirement: 160 GB — HANA L supports up to 256 GB.
How much the database can grow without you having to change the class. Changing the class requires a new certification.
Certified on Intel Xeon: HANA M, database up to 128 GB. AMX are matrix math units in the processor core, designed for inference on the CPU.
Only locations with a certified datastore — certification is only possible there. The location does not change the price.
EPYC 9554 · S/4HANA with connected BW, mixed OLTP and OLAP load
Volume layout
All amounts net, plus 19 % VAT. Excluding operations tier and recovery — both are listed below under operations.
The 4 classes form a ladder, each with its own protocol. Under the certification, a 1:1 ratio applies: one vCPU, i.e. one virtual processor core, per physical core — without overprovisioning.
S/4HANA development, quality assurance, small secondary systems
€2,313.00$2,683.08
per month, net · host, platform operations and licence; datastore separate
Productive S/4HANA in SMEs, Intel certification with AMX
€2,383.00$2,764.28
per month, net · host, platform operations and licence; datastore separate
S/4HANA with connected BW, mixed OLTP and OLAP load
€3,188.65$3,698.83
per month, net · host, platform operations and licence; datastore separate
BW/4HANA with large columnar storage, consolidated corporate systems
€7,083.18$8,216.49
per month, net · host, platform operations and licence; datastore separate
| Class | Host | Processor | Cores | Base clock | RAM | allocatable | vCPU | per month |
|---|---|---|---|---|---|---|---|---|
| HANA S | PC-M64 | EPYC 9454P | 48 | 2.75 GHz | 256 GB | 232 GB | 48 | €2,313.00$2,683.08 |
| HANA M | PC-M64i | Xeon 6741P | 48 | 2.50 GHz | 256 GB | 232 GB | 48 | €2,383.00$2,764.28 |
| HANA L | PC-L128 | EPYC 9554 | 64 | 3.10 GHz | 512 GB | 472 GB | 64 | €3,188.65$3,698.83 |
| HANA XL | PC-X256 | 2× EPYC 9965 | 384 | 2.25 GHz | 1 TB | 960 GB | 384 | €7,083.18$8,216.49 |
A NUMA node is a processor socket with the memory directly attached to it.
The hypervisor, the virtualisation layer of the host, requires memory itself: with PC-M64, 232 GB of 256 GB remain for the guest. SAP's volume rules still calculate using the physical configuration. The database itself may only occupy half, here 128 GB: HANA needs the other half for intermediate results and the delta merge, the incorporation of new write operations into the column store.
Certification possible in 2
The price per location shows HANA S with location factor, net and without datastore.
A node is considered accepted if an HWCCT report is available for exactly this configuration: host, memory, datastore and volume slice. You receive it upon handover and anew after every change.
You choose one of the 4 classes, one of the 2 locations and the certified Datastore NVMe Performance. All of this is listed in the catalogue on this page.
The node is delivered as defined and tested with the HWCCT. 4 storage metrics are measured against fixed limits — for example, ≤ 1000 µs for log write latency.
You receive the report upon handover. From then on, the storage metrics, or KPIs for short, are contractually guaranteed — not just measured.
If the memory, datastore, location or class changes, a new acceptance is required. Until the new report is available, the guarantee is suspended.
ENTRONYX SAP Certified
per host and monthCertified HANA nodes, licensed per host — without overcommitment.
The licence is tied to the host, not the number of cores. A node with 384 cores costs the same in terms of licensing as one with 48.

Exactly 4 combinations are accepted:
Another combination is not prohibited, just not documented. The ENTRONYX CLOUD guarantee does not apply to it.
The delivered configuration is always approved, not a single metric. That is why the justification is per class.
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.
SAP dictates the layout, not us. The three file systems follow from the memory of the class — and thus the quantity ordered on the datastore.
HANA S
640 GBbilled 2,048 GB
/hana/data 256 · /hana/log 128 · /hana/shared 256
HANA M
640 GBbilled 2,048 GB
/hana/data 256 · /hana/log 128 · /hana/shared 256
HANA L
1,280 GBbilled 2,048 GB
/hana/data 512 · /hana/log 256 · /hana/shared 512
HANA XL
2,560 GBbilled 2,560 GB
/hana/data 1,024 · /hana/log 512 · /hana/shared 1,024
3 of the 4 classes are below the minimum commitment and pay the same amount. Only HANA XL exceeds it.
| Class | RAM | /hana/data | /hana/log | /hana/shared | Total | billed | per month | with snapshots |
|---|---|---|---|---|---|---|---|---|
| HANA S | 256 GB | 256 GB1 × 256 | 128 GBmin(128; 512) | 256 GBmin(256; 1,024) | 640 GB | 2,048 GBMinimum commitment | €223.23$258.95 | €266.24$308.84 |
| HANA M | 256 GB | 256 GB1 × 256 | 128 GBmin(128; 512) | 256 GBmin(256; 1,024) | 640 GB | 2,048 GBMinimum commitment | €223.23$258.95 | €266.24$308.84 |
| HANA L | 512 GB | 512 GB1 × 512 | 256 GBmin(256; 512) | 512 GBmin(512; 1,024) | 1,280 GB | 2,048 GBMinimum commitment | €223.23$258.95 | €266.24$308.84 |
| HANA XL | 1,024 GB | 1,024 GB1 × 1,024 | 512 GBmin(512; 512) | 1,024 GBmin(1,024; 1,024) | 2,560 GB | 2,560 GB | €279.04$323.69 | €332.80$386.05 |

SAP checks 4 storage metrics in the HWCCT run. The limit value is guaranteed; the measured value comes from the certification run and proves it. A new measurement is taken after every change to the configuration or datastore.

All 4 classes can be created under the SAP stack. This is useful for templates, exports and powered-off secondary systems. The three volumes of a productive instance, however, belong on the Datastore NVMe Performance.
| Feature | NVMe PerformanceNVMe/TCP · NFS 4.1 | NVMe StandardNFS 4.1 · iSCSI | CapacityiSCSI · NFS 4.1 | ArchiveNFS 4.1 |
|---|---|---|---|---|
| SAP acceptanceHWCCT log per node | − | − | − | |
| IOPS per datastoreAccesses per second: 4 KB random, 70/30 read/write | 120,000 | 45,000 | 9,000 | 900 |
| Throughput | 6,000 MB/s | 2,400 MB/s | 1,100 MB/s | 350 MB/s |
| Latency p9999% of all accesses are faster than this value | 0.4 ms | 0.9 ms | 4.0 ms | 25.0 ms |
| Price per GB and month | €0.1090$0.1264 | €0.0720$0.0835 | €0.0290$0.0336 | €0.0068$0.0079 |
| Minimum commitment | 2,048 GB | 1,024 GB | 8,192 GB | 20,480 GB |
Backup windows, redundancy and snapshots of all classes can be found under Private Cloud storage.

An environment comprises 1 to 8 nodes. Each node is accepted individually and receives its own report. Acceptance in Frankfurt am Main (fra1) and Düsseldorf (dus1).
An approved node is not maintained in the fixed weekly window. Every change to firmware, hypervisor or datastore affects the approval. Therefore, it is agreed individually.
Maintenance windows
By arrangement per environment, 21 days lead time, outside your closing periods
The maintenance window is the agreed period during which work may be performed on a node. The lead time depends on the booked operations level. You define closing periods, inventories and payment runs once; no window will be scheduled during these times.
| Tier | Initial response P1 | Initial response P2 | Availability | Lead time | per environment | per host |
|---|---|---|---|---|---|---|
| Platform operations | 30 min | 4 h | P1 around the clock, P2 and P3 Mon–Fri 08:00–18:00 | 48 h | included | included |
| Platform and guest operations | 15 min | 2 h | P1 and P2 around the clock, P3 Mon–Sat 08:00–20:00 | 24 h | €690.00$800.40 | €39.00$45.24 |
| Full operations | 15 min | 1 h | Around the clock via fixed phone number, named technical contact | 8 h | €2,490.00$2,888.40 | €89.00$103.24 |
Prices apply per environment, plus a rate per host. Operations effort grows with the number of systems, not just with the number of nodes. The complete model can be found under Managed dedicated hosts.
9 questions that regularly come up before an enquiry. The answers use the same catalogue values as the sections above.
Can't find your question? Send us your configuration.
Yes: The approved host classes and the certified datastore are located in data centres in Germany, across 2 locations. Acceptance testing is performed on exactly this equipment on site; location, host class and datastore are stated in the report.
An outage (P1) is covered by the 'Platform operations' tier, which is included with every node: initial response in 30 minutes, around the clock. Questions and change requests are handled via a ticket in the account to support according to the SLA; the basic tier is included in the price, responds to a critical case within 8 h and is available Mon–Fri 08:00–18:00. Initial response means: acknowledged, classified, status reported — not a promise of resolution.
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.
An SAP HWCCT test report is available for exactly this configuration — host, memory, datastore and volume layout. From handover, the storage metrics are contractually guaranteed, not just measured.
Yes, it is not forbidden. However, there is no report for such a combination, and the guarantee of the storage metrics does not apply to it.
The certified Datastore NVMe Performance charges at least 2,048 GB. The three volumes of these classes add up to 640 to 1,280 GB and are therefore below this. Only HANA XL exceeds the minimum allocation.
Any such change requires a new acceptance test on the modified configuration. Until the new report is available, the guarantee of the storage metrics is suspended.
In Frankfurt am Main (fra1) and Düsseldorf (dus1): The approved host classes and the certified datastore are located there.
Per host, not per core: A host with 384 cores costs the same in terms of licences as one with 48. An environment comprises 1 to 8 nodes, and each node carries its own licence.
Licence per host and month, net€1,290.00$1,496.40
The class determines the volume layout, datastore and price. The report is generated on the delivered configuration and is provided to you upon handover. A change to the class, location or datastore requires a new acceptance.