Skip to content

GPU servers, available to rent by the hour, from data centres in Germany and Finland: 6 card types in 10 configurations, from the inference card that lets a pre-trained model answer, to the 8-GPU node with 1,128 GB graphics memory. Billing is per second at the hourly rate, capped at the monthly price — you will never be charged for more than 730 hours a month. Tell us below what you want to compute and how large your model is: the page names the smallest card it fits into, and calculates the hour, run and monthly cap — using the same code as the configurator.

Drivers, CUDA toolchain (NVIDIA's programming platform for the GPU) and container runtime are pre-installed. The local NVMe, the fast flash storage of the instance, is in the same chassis as the card — datasets are not read over the network.

Entry
€214.00$248.24
NG-RTX4000, net per month · €0.2932$0.3401 per hour
Configurations
10
6 card types, RTX PRO 4000 to H200
VRAM in the node
1,128 GB
8 × H200 via NVLink
Locations
3
with GPU capacity

Which card fits your model?

Purpose, model size and numerical precision — from this, the page calculates the GPU memory your model needs and shows the smallest configuration it fits into. Add location and term, and on the right you will see what the run costs: calculated with the same code as in the configurator. Exactly this node goes into the cart; you choose the image and dataset storage there or in the configurator.

Calculation basis

Reply (Inference)
Parameters × bytes per parameter, plus 20 % for response buffer (KV cache)
Adapt (Fine-tuning with LoRA)
Parameters × bytes, plus 40 % for adapters, optimizers and activations
Train (Full training, mixed precision)
16 bytes per parameter, plus 25 % for activations
Bytes per parameter
FP16/BF16 2 · INT8 1 · INT4 0.5

LoRA leaves the model weights unchanged and only learns small additional weights, the adapters. Mixed precision calculates in half precision and additionally keeps weights and optimizer state in full — hence the 16 bytes per parameter.

What do you want to compute?

A model with 8 billion parameters runs inference in FP16 on a 24 GB card; from 13 billion it needs 48 GB or a lower numerical precision.

Model size

8 billion parameters

1 bn670 bn

The size is usually in the model name — “B” stands for billion parameters.

Numerical precision

This is how many bytes each parameter occupies. INT8 and INT4 are quantised, meaning rounded to fewer bits: they require less memory and compute slightly less accurately.

Configuration

€214.00$248.24net / month

Your model needs around 19.2 GB of graphics memory

8 billion parameters × 2 bytes + 20% = 19.2 GB

Memory ladder: all 10 configurations, ascending by graphics memory per node
  1. Your requirement: 19.2 GB

Location

Reference location — the catalogue price applies without a factor. The milliseconds are the median latency from Frankfurt.

Term

1 h730 h

72 hours · 3 days

Nodes

1 card · 24 GB graphics memoryAlongside your model, around 4.8 GB remain free.

All configurations in the data sheet

The GPU never stands alone. Every row brings dedicated processor cores, memory and local NVMe — otherwise the data path becomes a bottleneck before the card is fully utilised. 6 card types thus result in 10 configurations.

GPU configurations with graphics card, computing power, processor, memory, local NVMe, traffic, hourly rate and monthly cap

  • NG-RTX4000Entry1 × RTX PRO 4000 · 24 GB GDDR7

    €0.2932$0.3401per hour

    Intel Core i5-13500 (14 cores, 20 threads)

    TFLOPS
    24
    vCPU
    20
    Memory
    64 GB DDR4
    Local NVMe
    2 × 512 GB NVMe
    Traffic
    unlimited
    Cap per month
    €214.00$248.24
  • NG-L4Inference1 × L4 · 24 GB GDDR6

    €0.7397$0.8581per hour

    AMD EPYC (dedicated)

    TFLOPS
    121
    vCPU
    8
    Memory
    48 GB
    Local NVMe
    400 GB
    Traffic
    40 TB
    Cap per month
    €540.00$626.40
  • NG-L40S1 × L40S · 48 GB GDDR6

    €1.3808$1.6017per hour

    AMD EPYC (dedicated)

    TFLOPS
    362
    vCPU
    16
    Memory
    96 GB
    Local NVMe
    800 GB
    Traffic
    50 TB
    Cap per month
    €1,008.00$1,169.28
  • NG-RTX60001 × RTX PRO 6000 · 96 GB GDDR7

    €1.6425$1.9053per hour

    Intel Xeon Gold 5412U (24 cores, 48 threads)

    TFLOPS
    110
    vCPU
    48
    Memory
    256 GB DDR5 ECC
    Local NVMe
    2 × 960 GB NVMe
    Traffic
    unlimited
    Cap per month
    €1,199.00$1,390.84
  • NG-RTX6000-5121 × RTX PRO 6000 · 96 GB GDDR7

    €2.4644$2.8587per hour

    Intel Xeon Gold 5412U (24 cores, 48 threads)

    TFLOPS
    110
    vCPU
    48
    Memory
    512 GB DDR5 ECC
    Local NVMe
    2 × 1.92 TB NVMe
    Traffic
    unlimited
    Cap per month
    €1,799.00$2,086.84
  • NG-RTX6000-7681 × RTX PRO 6000 · 96 GB GDDR7

    €3.1493$3.6532per hour

    Intel Xeon Gold 5412U (24 cores, 48 threads)

    TFLOPS
    110
    vCPU
    48
    Memory
    768 GB DDR5 ECC
    Local NVMe
    4 × 3.84 TB NVMe
    Traffic
    unlimited
    Cap per month
    €2,299.00$2,666.84
  • NG-H100Training1 × H100 · 80 GB HBM

    €2.6575$3.0827per hour

    AMD EPYC (dedicated)

    TFLOPS
    989
    vCPU
    32
    Memory
    256 GB
    Local NVMe
    3.2 TB
    Traffic
    80 TB
    Cap per month
    €1,940.00$2,250.40
  • NG-H100×22 × H100 · 160 GB HBM

    €5.3151$6.1655per hour

    2× AMD EPYC (dedicated)

    TFLOPS
    1,978
    vCPU
    64
    Memory
    512 GB
    Local NVMe
    6.4 TB
    Traffic
    100 TB
    Cap per month
    €3,880.00$4,500.80
  • NG-H100×44 × H100 · 320 GB HBM

    €10.6438$12.3468per hour

    2× AMD EPYC (dedicated)

    TFLOPS
    3,956
    vCPU
    128
    Memory
    1 TB
    Local NVMe
    12.8 TB
    Traffic
    140 TB
    Cap per month
    €7,770.00$9,013.20
  • NG-H200×8Cluster8 × H200 · 1,128 GB HBM

    €42.0000$48.7200per hour

    2× AMD EPYC (dedicated)

    TFLOPS
    7,912
    vCPU
    128
    Memory
    2 TB
    Local NVMe
    30.72 TB
    Traffic
    200 TB
    Cap per month
    €30,660.00$35,565.60

TFLOPS are manufacturer specifications with different measurement bases and therefore not directly comparable between cards. The graphics memory is the primary factor for selection.

Net amounts, location Frankfurt am Main. The hourly rate is the monthly price divided by 730 hours. Billing is per second at the hourly rate, capped at the monthly price — you will never be charged for more than 730 hours a month.

A horizontal, passively cooled data centre card with a black finned heatsink along the entire length, gold-plated contact strip and a metal bracket without text.
A card occupies its own full-bandwidth slot and belongs entirely to your node — no vGPU sharing. 24 to 141 GB graphics memory per card; what doesn't fit, won't run.
Identical GPU nodes stacked in an open rack, their fan fronts facing forward; on the right, a bundle of orange fibre optic cables tied with Velcro straps.

Within a node, NVLink connects the 8 cards at 900 GB/s per GPU. Between two nodes, only the network carries the load. ENTRONYX CLOUD sets up a dedicated RDMA fabric in the vRack for this — a private network where a card writes directly to the memory of the other side. Gradients therefore do not run over standard TCP.

NG-H200×8 · NVLink in the chassis, RDMA in between

Which card for which task

The most expensive card is rarely the right one. What matters is whether your model fits into memory, whether you are training or responding, and whether multiple GPUs need to talk to each other.

NG-L4

Inference and transcoding

The L4 is a single-slot card with 72 watts and a seventh-generation encoder. Its home is constantly running services: responses from quantised language models up to around 13 billion parameters, image generation, embedding calculation, and video transcoding including AV1.

VRAM
24 GB
TFLOPS (manufacturer specification)
121
Price / hour
€0.7397$0.8581

Not for training. If you fine-tune here, you will be waiting on memory bandwidth.

NG-L40S

Fine-tuning and rendering

48 GB of graphics memory is enough for LoRA and QLoRA adaptations on models up to around 30 billion parameters, without the detour of offloading to main memory. The RT cores make the same card the best choice for render farms and simulation previews.

VRAM
48 GB
TFLOPS (manufacturer specification)
362
Price per 100 TFLOPS/h
€0.38$0.44

No NVLink bridge: multiple L40S communicate via PCIe. This is the bottleneck for communication-heavy multi-GPU training.

NG-RTX6000

Inference and fine-tuning of medium-sized models

96 GB GDDR7 with ECC — the largest graphics memory among the single cards in the catalogue. The RTX PRO 6000 Blackwell holds 8-bit quantised models up to the mid-double-digit billion range including KV cache on a single card and handles LoRA and QLoRA adaptations without offloading. The H100 class with HBM remains responsible for bandwidth-bound training.

VRAM
96 GB
Local NVMe
1.92 TB
72-hour run
€118.26$137.18
NG-H100

Large-scale training

Hopper with 80 GB HBM3, 3.35 TB/s bandwidth, and Transformer Engine. The FP8 path doubles the throughput compared to BF16, provided the training script uses it. For models that fit into one GPU but would take weeks instead of days, this is the most economical single card in the catalogue.

VRAM
80 GB
TFLOPS (manufacturer specification)
989
72-hour run
€191.34$221.95
NG-H200×8

Distributed cluster training

Eight H200s in one node, connected via NVLink with 900 GB/s per GPU — not via Ethernet. A total of 1,128 GB graphics memory, enough for models that could not even be loaded on a single card. Tensor and pipeline parallelism run within the chassis, without a network hop.

Total VRAM
1,128 GB
Main memory
2 TB
Local NVMe
30.72 TB

Only bookable after a capacity check. We link multiple nodes via a dedicated RDMA fabric in the vRack.

What a training run costs

A run of 72 hours per configuration, fully calculated — net, in Frankfurt am Main, including instance, local NVMe and traffic. The finder above calculates your own run with location, hours and nodes using the same rates; here is the breakdown.

Three days is a realistic window for fine-tuning with subsequent evaluation. Calculate your own run in the finder

Cost of a 72-hour run per configuration, plus the price per individual GPU hour and per 100 TFLOPS
ConfigurationGPUsTotal VRAMPrice / hourper GPU hourper 100 TFLOPS/h (manufacturer specification, see note below the table)72 hours
NG-RTX4000NVIDIA RTX PRO 4000 Blackwell SFF124 GB€0.2932$0.3401€0.2932$0.3401€1.22$1.42€21.11$24.49
NG-L4NVIDIA L4124 GB€0.7397$0.8581€0.7397$0.8581€0.61$0.71€53.26$61.78
NG-L40SNVIDIA L40S148 GB€1.3808$1.6017€1.3808$1.6017€0.38$0.44€99.42$115.33
NG-RTX6000NVIDIA RTX PRO 6000 Blackwell Max-Q196 GB€1.6425$1.9053€1.6425$1.9053€1.49$1.73€118.26$137.18
NG-RTX6000-512NVIDIA RTX PRO 6000 Blackwell Max-Q196 GB€2.4644$2.8587€2.4644$2.8587€2.24$2.60€177.44$205.83
NG-RTX6000-768NVIDIA RTX PRO 6000 Blackwell Max-Q196 GB€3.1493$3.6532€3.1493$3.6532€2.86$3.32€226.75$263.03
NG-H100NVIDIA H100 SXM180 GB€2.6575$3.0827€2.6575$3.0827€0.27$0.31€191.34$221.95
NG-H100×2NVIDIA H100 SXM2160 GB€5.3151$6.1655€2.6576$3.0828€0.27$0.31€382.69$443.92
NG-H100×4NVIDIA H100 SXM4320 GB€10.6438$12.3468€2.6610$3.0868€0.27$0.31€766.35$888.97
NG-H200×8NVIDIA H200 SXM81,128 GB€42.0000$48.7200€5.2500$6.0900€0.53$0.61€3,024.00$3,507.84
TFLOPS are manufacturer specifications with different measurement bases and therefore not directly comparable between cards — the column per 100 TFLOPS provides context, it does not decide.

Two columns deserve a second look. The first is per GPU hour. The eight-GPU node costs €5.2500$6.0900 per card there and is thus only slightly above a single H100 with €2.6575$3.0827. It provides 76% more graphics memory per card and NVLink between all eight.

The second is per 100 TFLOPS. Measured against the manufacturer's specification for computing power, the H100 is the cheapest row in the table at €0.27$0.31. The L40S is the best compromise without HBM at €0.38$0.44 — the stacked high-performance memory that only the H100 class carries. The RTX PRO 6000, on the other hand, buys graphics memory, not throughput at €1.49$1.73: 96 GB for models that would otherwise require two cards. If you need computing power instead of memory, you should know this order before reaching for the largest number.

The path remains the same in both cases. First check whether the model fits into the memory. Then compare the price per computing power. And only then select the card by name.

Calculation basis

Term in the example
72 h
Billing cycle
per second
Location
Frankfurt am Main (fra1)
Price factor
1.00
Cap per month
730 h
Included
Instance, local NVMe, traffic

Billing is per second at the hourly rate, capped at the monthly price — you will never be charged for more than 730 hours a month. The hourly rate is calculated on 730 hours, the average month. A month with 31 days has 744 — we do not charge for the additional hours.

Select pricing unit

Monthly price is also the cap for hourly billing

GPU configurations with graphics memory, computing power and price optionally per hour or per month
ConfigurationGPUsTotal VRAMTotal TFLOPS72 hPrice / month
NG-RTX4000NVIDIA RTX PRO 4000 Blackwell SFF124 GB24€21.11$24.49€214.00$248.24
NG-L4NVIDIA L4124 GB121€53.26$61.78€540.00$626.40
NG-L40SNVIDIA L40S148 GB362€99.42$115.33€1,008.00$1,169.28
NG-RTX6000NVIDIA RTX PRO 6000 Blackwell Max-Q196 GB110€118.26$137.18€1,199.00$1,390.84
NG-RTX6000-512NVIDIA RTX PRO 6000 Blackwell Max-Q196 GB110€177.44$205.83€1,799.00$2,086.84
NG-RTX6000-768NVIDIA RTX PRO 6000 Blackwell Max-Q196 GB110€226.75$263.03€2,299.00$2,666.84
NG-H100NVIDIA H100 SXM180 GB989€191.34$221.95€1,940.00$2,250.40
NG-H100×2NVIDIA H100 SXM2160 GB1,978€382.69$443.92€3,880.00$4,500.80
NG-H100×4NVIDIA H100 SXM4320 GB3,956€766.35$888.97€7,770.00$9,013.20
NG-H200×8NVIDIA H200 SXM81,128 GB7,912€3,024.00$3,507.84€30,660.00$35,565.60

The column for 72 hours remains unchanged — it always shows the amount actually incurred for a three-day run.

Hourly, monthly or with a fixed term

Three ways to the same card. Which one is the cheapest depends solely on utilisation — not on the model and not on the location.

Monthly price per configuration by term, plus the savings of one year with a 24-month commitment
Configurationmonthly12 months −5%24 months −8%Savings / year
NG-RTX4000€214.00$248.24€203.30$235.83€196.88$228.38€205.44$238.32
NG-L4€540.00$626.40€513.00$595.08€496.80$576.29€518.40$601.32
NG-L40S€1,008.00$1,169.28€957.60$1,110.82€927.36$1,075.74€967.68$1,122.48
NG-RTX6000€1,199.00$1,390.84€1,139.05$1,321.30€1,103.08$1,279.57€1,151.04$1,335.24
NG-RTX6000-512€1,799.00$2,086.84€1,709.05$1,982.50€1,655.08$1,919.89€1,727.04$2,003.40
NG-RTX6000-768€2,299.00$2,666.84€2,184.05$2,533.50€2,115.08$2,453.49€2,207.04$2,560.20
NG-H100€1,940.00$2,250.40€1,843.00$2,137.88€1,784.80$2,070.37€1,862.40$2,160.36
NG-H100×2€3,880.00$4,500.80€3,686.00$4,275.76€3,569.60$4,140.74€3,724.80$4,320.72
NG-H100×4€7,770.00$9,013.20€7,381.50$8,562.54€7,148.40$8,292.14€7,459.20$8,652.72
NG-H200×8€30,660.00$35,565.60€29,127.00$33,787.32€28,207.20$32,720.35€29,433.60$34,143.00

What starts where straight away — and what we check first

GPUs are the only product in this catalogue for which we do not guarantee immediate availability. We therefore state the situation per configuration and location in advance. Where it says “on request”, the link leads directly to the request — configuration and location are already filled in.

immediately
always available, start without review
on request
available based on capacity, the status per card is listed below
not offered
not available at this location

Availability of each GPU configuration per location, as of 17 September 2026

Situation per card type, as of 17 September 2026 — one row per card, valid for all expansion stages of this card: immediate availability, reservation lead time and quota per project
CardOn-demandReservationQuota
NVIDIA RTX PRO 4000 Blackwell SFFBase row NG-RTX4000continuously availablenot required8 GPUs
NVIDIA L4Base row NG-L4continuously availablenot required8 GPUs
NVIDIA L40SBase row NG-L40Scontinuously availablepossible from 30 days4 GPUs
NVIDIA RTX PRO 6000 Blackwell Max-QBase row NG-RTX6000usually availablefrom 30 days, 2 working days lead time2 GPUs
NVIDIA H100 SXMBase row NG-H100subject to capacityfrom 30 days, 5 working days lead time2 GPUs
NVIDIA H200 SXMBase row NG-H200×8only after reviewfrom 30 days, 10 working days lead timeon request
Query and reserve capacity
# Query free capacity per model and location
entronyx gpu availability --model h100 --region fra1
# MODEL    LOCATION  FREE  RESERVABLE    NEXT SLOT
# h100     fra1         3            12  now
# h200x8   fra1         0             2  on request
 
# Bindingly reserve capacity for 30 days
entronyx gpu reservation create \
  --flavor ng-h100 --region fra1 --count 4 --term 30d
 
# Notification as soon as an H200 node becomes available
entronyx gpu watch --flavor ng-h200x8 --region dus1 --notify webhook
The availability query is not rate-limited and may run in deployment scripts. Reservations appear as a separate item on the invoice.
A dark carrier board from above: eight square heatsinks in two rows, with four smaller ones in between.
Eight cards on a carrier board, connected via NVLink at 900 GB/s per card — the node that ENTRONYX CLOUD only allocates after a capacity check. Each card gets 8 to 48 dedicated EPYC cores so that preprocessing doesn't slow down the GPU.

Which card is where

GPU nodes require more power per rack unit and different cooling than a standard chassis. Therefore, not every configuration is available at every location — and the largest one only where liquid cooling is installed.

  • Frankfurt am Mainfra1

    Location Rhein-Main

    RTX PRO 4000 Blackwell SFF · L4 · L40S · RTX PRO 6000 Blackwell Max-Q · H100 SXM · H200 SXM

    10 of 10 configurations · PUE 1.14 · 3 ms

    Complete range

  • Düsseldorfdus1

    Location Rhein-Ruhr

    RTX PRO 4000 Blackwell SFF · L4 · L40S · RTX PRO 6000 Blackwell Max-Q · H100 SXM · H200 SXM

    10 of 10 configurations · PUE 1.12 · 4 ms

    Complete range

  • Helsinkihel1

    Location Uusimaa

    RTX PRO 4000 Blackwell SFF · L4 · L40S · RTX PRO 6000 Blackwell Max-Q · H100 SXM · H200 SXM

    10 of 10 configurations · PUE 1.08 · 21 ms

    Complete range

3 of the 3 locations carry all 10 configurations: Location Rhein-Main, Location Rhein-Ruhr, Location Uusimaa. The rest carry the cards that their power density allows. PUE is the ratio of total power to computing power — the closer to 1.0, the less goes into cooling and losses. Which configuration starts immediately at which location can be found in the availability matrix.

Rear of a compute node in the rack: Two black, braided coolant hoses lead from quick-release couplings on the chassis to a vertical stainless steel manifold with shut-off valves.
Liquid cooling per node: The largest node is only available where the cooling loop reaches the rack — 3 of 3 locations. The heat goes into the loop instead of the ambient air; this keeps the PUE at no more than 1.14.

Training data without third-country transfer

All 3 GPU locations are within the scope of the GDPR, spread across Germany and Finland. If you compute here, your training data is processed without third-country transfers. The data processing agreement according to Art. 28 GDPR is part of the main contract and not an additional form.

Data processing agreement (DPA) Contract text and sub-processors

3Locations, all without third-country transfer

Prepared, but not prescriptive

The standard image includes drivers, the CUDA toolchain and a container runtime. Everything on top is yours — we do not dictate any framework or version.

Driver
NVIDIA 570 LTS
Data centre branch, maintained monthly
CUDA
12.8 and 12.4
switchable via modules
Container
NVIDIA Container Toolkit
Docker and Podman, --gpus all
Operating system
Ubuntu 24.04 LTS
also Debian 13 and Rocky 10
First steps on a GPU instance
# Drivers, CUDA and container runtime are pre-installed in the image
nvidia-smi --query-gpu=name,memory.total,driver_version --format=csv
 
# Single GPU: container with access to the local NVMe
docker run --rm --gpus all \
  -v /mnt/nvme/datasets:/data \
  -v /mnt/nvme/checkpoints:/ckpt \
  nvcr.io/nvidia/pytorch:25.06-py3 \
  python train.py --data /data --out /ckpt --precision bf16
 
# Eight GPUs in one node: NCCL runs over NVLink, not over the network
torchrun --standalone --nproc_per_node=8 train.py \
  --precision fp8 --grad-accum 4 --checkpoint-every 500
 
# Observe usage during the run
nvidia-smi dmon -s pucm -d 5
The local NVMe is mounted at /mnt/nvme. It survives reboots, but not the deletion of the instance — checkpoints also belong in the Object Storage.

Not just language models

The L4 decodes and encodes up to eight 4K streams simultaneously in AV1, the royalty-free video format. For media libraries and live transcoding, this makes it the cheapest line in the catalogue. The L40S also brings RT cores — compute units for ray tracing — for Blender, Omniverse and Unreal render farms. Both cases pay off per hour very differently than training.

Common questions before your first GPU instance

Ten questions that regularly come up before ordering. The answers use the same catalogue values as the sections above.

Question not listed? The Finder calculates card, hour and run for your model.

Can I rent a GPU by the hour, and how much does an hour cost?

Yes: you can rent GPU servers at ENTRONYX CLOUD by the hour and without a minimum term, in data centres in Germany and Finland. Billing is per second at the hourly rate of the configuration, capped at the monthly price; the hourly rate of the entry-level NG-RTX4000 with a RTX PRO 4000 and 24 GB of graphics memory is shown in the line below this answer.

NG-RTX4000, per hour, net€0.2932$0.3401

Hourly prices of all configurations

Which card do I need for my model?

The smallest configuration whose video memory fits your model: In FP16, the weights take up around 2 GB per billion parameters, full training requires around 16 bytes per parameter. Between 24 and 141 GB are available per card; what doesn't fit, won't run.

Calculate the smallest suitable card in the finder

How is a GPU instance billed?

To the second at the hourly rate of the configuration, capped at the monthly price: You are never billed for more than 730 hours a month. The instance, local NVMe and the traffic quota of the configuration are included in the hourly rate.

NG-RTX4000, starting price per hour, net€0.2932$0.3401

What a training run costs

Do I have to commit to a term?

No, without a term you pay for the time used, at most the monthly price. With 12 or 24 months, the monthly price decreases by 5% or 8% respectively; the term applies per instance and is paid in advance. You can switch to a larger configuration even within the commitment, to a smaller one only at the end of the term.

Monthly price per term

Which cards start immediately?

RTX PRO 4000, L4 and L40S are continuously available and start without verification. You procure RTX PRO 6000, H100 and H200 based on capacity at the selected location, via a request with a pre-filled configuration.

Availability per configuration and location

Can a running card be taken away from me?

No, there are no interruptible instances at spot prices: A running card runs until you terminate it. If you want to be sure to get a card back after a restart, you reserve the capacity; it is then permanently assigned for the booked period and paid for the entire period.

Do I share the graphics card with other customers?

No, a card occupies its own slot with full bandwidth and belongs entirely to your node, without vGPU sharing. Each configuration also comes with dedicated processor cores, memory and local NVMe so that the data path does not slow down the card.

All configurations in the data sheet

Where are the GPU servers located?

In Germany and Finland, at three locations: Frankfurt am Main (fra1), Düsseldorf (dus1) and Helsinki (hel1). All are within the scope of the GDPR, and data is processed without transfer to third countries. The data processing agreement according to Art. 28 GDPR is part of the main contract.

Which card is at which location

How fast does support respond, and how do I reach them?

Via ticket in the account: The price includes the basic support of the SLA with an initial response in 8 hours for critical incidents (P1), available Monday to Friday from 08:00 to 18:00. Initial response means: A human has accepted the report, classified it and reported back the processing status — the SLA does not guarantee a resolution time. In addition to basic support, it offers three further support levels; the highest responds to P1 in 15 minutes.

Is there a minimum term, and how do I cancel?

Not without a term commitment: You can delete services billed by the hour at any time without notice in the console or via the API, and billing ends at the time of deletion (Section 11 paragraph 3 of the Terms and Conditions). 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 — otherwise they renew for twelve months (Section 11 paragraph 2 of the Terms and Conditions). You pay the term in advance and receive a 5% or 8% term discount in return.

Monthly price per term

from · per month, net€214.00$248.24

Find card

Configure GPU instance or reserve capacity

RTX PRO 4000, L4 and L40S are continuously available and start without review. You purchase RTX PRO 6000, H100 and H200 based on capacity at the selected location; a reservation of 30 days or more secures the card.

from
€214.00$248.24
VRAM in the node
1,128 GB
72-hour run from
€21.11$24.49
Locations
3