Mr.PlanB Logo

    Scored, not ranked · Updated October 2026

    Open Telekom Cloud CCE review 2026

    Open Telekom Cloud Cloud Container Engine (CCE, CCE Turbo), now T Cloud Public · Sovereign German CCE

    Open Telekom Cloud CCE is scored in the Managed Cloud Kubernetes Ledger 2026 (Ledger Index 61 out of 100) but not ranked, because it fails one of the Ledger's inclusion tests. T Cloud Public builds toward a German sovereign container service on Huawei-derived CCE technology, with Turbo clusters, H100 nodes and add-ons as the…

    Scores

    Ledger Index
    61/100
    not ranked
    Capability
    62.2/100
    Credibility
    16/25
    Commercial risk
    8/25
    lower is better
    Lock-in
    11.5/25
    lower is better
    AI delivery
    7/20

    Source: Managed Cloud Kubernetes Ledger 2026, edition 2026-10-13. How each score works: methodology.

    Pros

    • Regions, sovereignty and SLA4/5

    Cons

    • Multi-cluster, hybrid and fleet2/5

    What the Ledger says

    T Cloud Public builds toward a German sovereign container service on Huawei-derived CCE technology, with Turbo clusters, H100 nodes and add-ons as the next steps. The record shows a public roadmap that is mostly kept but late, Kubernetes minors that arrive about ten months after upstream, and end-of-service dates that were shortened in 2025. A buyer gets German operation, C5 and TISAX, and pays with old Kubernetes versions and no CNCF conformance listing.

    AI say-do: 3 tracked, 1 shipped (H100 in CCE), 2 pending (NVLink H100, confidential containers). GPU nodes are the substance; no MCP server and no confirmed assistant.

    Capability by area

    Versions, upgrades and support3/5
    Nodes, autoscaling and compute choice3/5
    Networking3/5
    Storage and data protection3/5
    Security and compliance3.5/5
    Observability and day-2 operations3/5
    Multi-cluster, hybrid and fleet2/5
    Developer and app platform3/5
    GPU and AI workloads3.5/5
    Regions, sovereignty and SLA4/5

    Buying, lock-in and release record

    Buying and licence (commercial risk)(lower is better)

    Price and licence volatility2
    Common I/O disk end of sales 2025-07-01 and decommissioning 2026-12-31, GPU family retirements, rename to T Cloud Public; no control-plane fee change found
    Purchase constraints1
    Self-service booking with a 250 euro credit; pay-as-you-go
    Channel and access1
    Public pricing models and release notes; docs site behind a bot challenge; two regions
    Owner stability1.5
    Deutsche Telekom subsidiary; reorganised into the T Cloud division in 2025 and renamed in 2026
    Cost of staying supported2.5
    Two-year support windows without fees, but versions arrive about 10 months late and end-of-service dates were cut

    Technical lock-in(lower is better)

    Formats1.5
    Kubernetes API with Everest storage classes and ELB annotations; no CNCF conformance listing found
    Export path2
    Velero-based migration guide; egress charges not read
    Stack coupling2.5
    Everest CSI, ELB ingress and Turbo pod ENIs with provider security groups
    Hardware / cloud coupling4
    Runs only in the two Open Telekom Cloud regions; UCS hybrid is planned, not released
    Skills and tooling coupling1.5
    Standard kubectl and Terraform plus CCE console and add-on specifics

    Release credibility

    Cadence3
    Minor release about every 4 to 5 months since 2025, but each about 10 months behind upstream and no published calendar
    Roadmap transparency4
    Public roadmap page with archived history plus dated release notes and a documented version policy
    Say-do3.5
    6 of 8 roadmap items shipped within 12 months of first listing; CCE Turbo GA took 18.5 months, 1.33 took 15
    Velocity3
    One or two substantive capabilities a quarter: Turbo GA, new minors, H100, add-ons
    Lifecycle stability2.5
    About two years per version, but end-of-service dates were shortened by 3 to 9 months in 2025 and 1.26 was skipped

    Partners and services

    Partner programme openness3.5
    CIRCLE and TECH partner programmes listed on the site; not opened
    Multi-tenancy and self-service3.5
    IAM projects and enterprise dashboards; per-region cluster quotas
    API and infrastructure-as-code4.5
    Terraform provider with 7.2 million downloads, Crossplane provider 1.0 on 2026-09-04, Python SDK
    Skills and certification3.5
    T Cloud Public certification programme since 2020-03-17 and a training catalogue

    Alternatives to Open Telekom Cloud CCE

    Is Open Telekom Cloud CCE right for you?

    Describe what you run and the free advisor ranks Open Telekom Cloud CCE against the other managed Kubernetes services for your case.

    Open the advisor

    Questions about Open Telekom Cloud CCE

    Is Open Telekom Cloud CCE any good?

    Open Telekom Cloud CCE is scored in the Managed Cloud Kubernetes Ledger 2026 (Ledger Index 61 out of 100) but not ranked, because it fails one of the Ledger's inclusion tests. Its strongest areas are regions, sovereignty and sla. Its weakest are multi-cluster, hybrid and fleet.

    What are the best alternatives to Open Telekom Cloud CCE?

    The closest by Ledger Index are DigitalOcean DOKS (61.9), Scaleway Kapsule/Kosmos (62.2), IBM IKS / ROKS (62.4), Tencent TKE (58.6).

    How is Open Telekom Cloud CCE licensed and sold?

    Common I/O disk end of sales 2025-07-01 and decommissioning 2026-12-31, GPU family retirements, rename to T Cloud Public; no control-plane fee change found.

    How much lock-in does Open Telekom Cloud CCE bring?

    Open Telekom Cloud CCE scores 11.5 out of 25 on technical lock-in (lower is better). Export path: Velero-based migration guide; egress charges not read.

    User reviews of Open Telekom Cloud CCE

    No reviews yet

    Be the first to say how Open Telekom Cloud CCE worked for you.

    Write a review

    No account needed and no email asked. We read every review before it appears and remove adverts, spam and personal attacks.

    Your rating