Open Telekom Cloud pricing, under the name T Cloud Public since January 2026, is Elastic Cloud Servers per hour or as reserved packages per month, object storage per GiB and month in tiered classes, block storage per GiB and month by performance level, Kubernetes clusters per hour, Elastic IPs and load balancers per hour, and outbound internet traffic per GiB in tiers; every price stands in euro without taxes and duties in the service description from T-Systems. On the bill the servers dominate, elastic by runtime or reserved by package, followed by block storage, which keeps running on stopped servers.
Pricing dimensions
T Cloud Public is the new name of the Open Telekom Cloud; the website states that the product carried that name until January 2026, and the documentation continues at docs.otc.t-systems.com. The prices sit in the service description with price list, last revised on 2026-10-09, per region EU-DE and EU-NL, and for compute in three models: elastic per hour, reserved over 12 or 24 months per month, and reserved with upfront payment.
| Dimension | Unit | What drives it | Optional |
|---|---|---|---|
| Elastic Cloud Server, elastic | Seconds recorded, summed per month, billed in hours, running state only | Flavor (s2 general purpose, c3 and c4 dedicated, m3 memory-optimised, e3 large memory, d2 disk, i3 I/O, p2v and g6 GPU), region, operating system | No |
| Elastic Cloud Server, reserved | Monthly package per flavor type over 12 or 24 months, an hour contingent per month | Up to 60 percent off; the contingent lapses monthly; excess at the elastic rate | Yes |
| Reserved upfront | The full amount for 8,760 hours at the start | Largest discount, no switch to larger types | Yes |
| Elastic Volume Service | GiB per month by class | Common I/O EUR 0.0506, High I/O EUR 0.0660, GP SSD EUR 0.1040, Ultra-High I/O EUR 0.1100, Extreme SSD EUR 0.3080 per GiB-month in EU-DE; GP SSD v2 EUR 0.0820 plus IOPS and throughput above the allowances | No |
| Object Storage Service | GiB per month in tiers by class, requests per 1,000 | Standard EUR 0.0242 per GiB up to 1,000 GiB, falling to EUR 0.0231; Warm EUR 0.0132; Cold EUR 0.00462; the first 5 GiB of Standard free | Yes |
| Internet traffic | GiB per month outbound in tiers; inbound free | 1 GiB free, then EUR 0.074489 per GiB up to 1,000 GiB, EUR 0.070351 to 10,000, EUR 0.066 to 50,000, EUR 0.0462 to 150,000, falling to EUR 0.0418 | Only above 1 GiB |
| Elastic IP | Hour per address | EUR 0.0044 per hour; mail addresses EUR 0.030074 | Yes |
| Elastic Load Balancer | Hour per instance or LCU | Shared EUR 0.04301 per hour; dedicated from EUR 0.045408 per hour at 10 LCU | Yes |
| Cloud Container Engine | Hour per cluster by size and availability | A small VM cluster without HA free; medium EUR 0.133395; small HA EUR 0.380181; xlarge HA EUR 0.92051 per hour; nodes as servers | Yes |
Elastic servers pay for runtime only: usage is recorded by the second, summed over the calendar month and billed in hours; a stopped server costs no more compute time, its EVS disks and Elastic IPs keep running, and flavors with local disks or GPUs are billed while stopped too. Reserved packages are tied to the flavor type, not to an instance, and are billed whether the server runs or not: every month brings an hour contingent of days times 24, what lies above it is billed elastically, what stays below lapses; nothing renews by itself at the end of the term, and a switch to a larger or newer type is possible through the service desk. The upfront payment brings the largest discount, rules out the switch and falls due at the start of the term; the service description provides for a compensation payment of half the remaining payments on early termination. For an s2.medium.1 with 1 vCPU and 1 GiB on Linux in EU-DE that means EUR 0.014980 per hour elastic, EUR 8.00 per month reserved over 12 months, EUR 6.75 over 24 months and EUR 84.70 upfront for 12 months; Windows costs EUR 0.065516 per hour on the same flavor. The logic of such packages is described for the hyperscalers in commitment exchange, cancellation and expiry.
Internet traffic is tiered outward and free inward, with only 1 GiB of allowance a month; that places T Cloud Public closer to the hyperscalers' metered models than the other providers in this chapter, as included traffic and flat pricing models sets out, even though the price per GiB falls with volume. Object storage has three classes with minimum durations, early deletion fees and restores from the cold class at three speeds; the mechanics are in storage tiers and lifecycle. The Cloud Container Engine is free up to 50 nodes without high availability, larger or highly available clusters pay per hour, and the ECS nodes appear separately on the invoice, as containers and Kubernetes describes.
Invoices, exports and APIs
Telekom, more precisely T-Systems International GmbH in Bonn, issues one monthly invoice per contract, that is per tenant, by email or post; the customer collects it in the MyWorkplace portal and receives there a connection overview in CSV format with the daily use of the resources in machine-readable form. All prices exclude the taxes and duties applicable at the time of invoicing; what that means for VAT is in VAT and reverse charge. Price changes are announced, by the service description, at least six weeks ahead in text form.
The free Financial Dashboard, formerly Enterprise Dashboard, shows the services used and the costs incurred daily, and the Tag Management Service assigns costs per resource to a tag that can be analysed in the documents accompanying the invoice and in the dashboard; tags can be created by hand or from a CSV template. An alert service in MyWorkplace reports when spend passes a threshold, and vouchers are applied at the end of the billing run. The price page names the PDF invoice with its CSV attachment as the standard. A billing API per resource and hour is not documented in the service description; the daily CSV and the dashboard are the sources, and what can be won from them for FOCUS columns is in collecting cost data from European providers.
Levers
Configuration
Stopping ends the compute time of elastic servers but not EVS and Elastic IPs; development environments that stand still at night save the server, not the disk, which scheduling and auto-scaling puts in context. Flavors with local disks or GPUs pay while stopped, and the choice of EVS class spans a factor of six between Common I/O and Extreme SSD. Rightsizing here also means checking the operating system: Windows and commercial Linux distributions multiply the hourly price of the same flavor.
Purchase option
Reserved packages pay for servers that run through the month; the service description names up to 60 percent against elastic, and the example above shows about 27 percent over 12 and 38 percent over 24 months on the smallest flavor. Because the contingent is tied to the type and lapses monthly, a package for s2.medium.1 covers no s2.large.1, and a package without a running server is pure waste; commitment coverage and utilisation describes the measurement.
Architecture
Outbound traffic costs from the second GiB, so deliveries in volume belong in the cost calculation, not only the servers; the tiers fall with volume, and inbound and internal traffic is free, as data transfer and egress explains in general. The small CCE cluster without high availability is free; the HA variant costs EUR 0.38 per hour even at the smallest size, more than a medium server.
Where it goes wrong
- The package runs, the server does not. Symptom: the bill shows the reserved package although no server ran. Cause: the package is tied to the flavor type and billed regardless of operation; the monthly contingent lapses.
- The contingent exceeded. Symptom: elastic hours appear beside the package. Cause: two servers of the same type share one contingent of days times 24 hours; what lies above pays elastically.
- Stopped but billed. Symptom: a stopped server with a local disk or GPU keeps costing. Cause: those flavors are billed while stopped; on others EVS and the Elastic IP keep running.
- Egress from the second gigabyte. Symptom: a traffic line even with little delivery. Cause: the allowance is 1 GiB per month, not terabytes as with other providers in the chapter.
- Old name, new invoice. Symptom: invoices and portals carry "T Cloud Public" instead of "Open Telekom Cloud" since 2026. Cause: the renaming in January 2026; the contracting party stays T-Systems.
- Early termination. Symptom: a compensation payment after ending a reserved package. Cause: the service description provides for half the remaining payments on termination before the minimum term ends.
- Daily values only. Symptom: costs cannot be assigned to an hour of a resource. Cause: the CSV in MyWorkplace carries daily usage; it gets no finer.
Example
List prices for the EU-DE region from the service description, euro without taxes, read on 2026-10-21: an s2.medium.1 (1 vCPU, 1 GiB, Linux) costs EUR 0.014980 per hour elastic, EUR 8.00 per month reserved over 12 months, EUR 6.75 over 24 months and EUR 84.70 upfront for 12 months; an s2.large.1 (2 vCPU, 2 GiB) EUR 0.095230 per hour or EUR 43.53 per month reserved over 12 months; an s2.xlarge.1 (4 vCPU, 4 GiB) EUR 0.195951 per hour or EUR 88.23 reserved. EVS GP SSD costs EUR 0.1040 per GiB-month, OBS Standard EUR 0.0242 per GiB-month up to 1,000 GiB, outbound traffic EUR 0.074489 per GiB in the first tier, an Elastic IP EUR 0.0044 per hour and a small CCE cluster with high availability EUR 0.380181 per hour. The figures show that the s2.medium.1 costs EUR 10.79 elastic in 720 hours and EUR 8.00 reserved, 26 percent less, that 1 TiB of outbound traffic costs about EUR 76 and so more than seven small servers, and that a cluster's high availability at EUR 274 in 720 hours is twelve times a reserved small server.
Sources
Read on 2026-10-21. Prices: Service description and price list T Cloud Public, revised 2026-10-09 (PDF), Prices, Pricing models for computing and containers, Pricing models. Service: T Cloud Public, home page with the renaming notice, Elastic Cloud Server.