T Cloud Public vs Hikube — Direktvergleich

Interaktive Fassung: https://comparison.cloud/vergleich/telekom-vs-hikube

Vendor-neutraler Direktvergleich von T Cloud Public und Hikube: Services, Rechenzentren, Kosten und Souveränität — datenbasiert auf comparison.cloud.

Management Summary (Stand 2026-10)

T Cloud Public positioniert sich als breit aufgestellter EU-Anbieter mit maximaler operativer Souveränität (10/10) und einem zertifizierten Portfolio, das DACH-Regionen abdeckt, während Hikube als Schweizer Anbieter durch ein architektonisch integriertes 3-AZ-Design über Genf, Gland und Luzern punktet. Der entscheidende Unterschied liegt in der strategischen Breite: T Cloud Public bietet ein umfassendes Angebot an Managed Databases, Kubernetes und Storage, das über reine IaaS hinausgeht, wohingegen Hikube auf ein fokussiertes, resilienties Design setzt. Für Unternehmen, die höchste operative Kontrolle und ein breites Service-Spektrum in Europa benötigen, ist T Cloud Public die passende Wahl. Hikube eignet sich hingegen für Schweizer Organisationen und regulierte Mittelständler, die integrierte Multi-Site-Resilienz ohne eigene Auslegung wünschen und bei GPU-Workloads kosteneffizient arbeiten möchten.

T Cloud Public: Stärken

T Cloud Public: Zu bedenken

Hikube: Stärken

Hikube: Zu bedenken

T Cloud Public wählen, wenn:

Hikube wählen, wenn:

Häufige Fragen: T Cloud Public vs Hikube

Was ist der Unterschied zwischen T Cloud Public und Hikube?

T Cloud Public ist ein breit aufgestellter EU-Anbieter mit maximaler operativer Souveränität (10/10) und einem Portfolio von über 50 Services, das DACH-Regionen abdeckt. Hikube ist ein Schweizer Anbieter, der durch ein architektonisch integriertes 3-AZ-Design über Genf, Gland und Luzern eine hohe operative Resilienz (10/10) bietet. Während T Cloud Public auf strategische Breite und Zertifizierungen setzt, fokussiert sich Hikube auf integrierte Multi-Site-Resilienz und kosteneffiziente GPU-Preise.

Welcher Anbieter ist souveräner?

T Cloud Public erzielt einen SEAL Score von 7,6/10 (76 %) und eine operative Souveränität von 10/10, was die höchste Unabhängigkeit von nicht-EU-Interventionen im Vergleichsfeld darstellt. Hikube erreicht einen SEAL Score von 6,9/10 (69 %) und eine operative Souveränität von 8/10. Beide Anbieter sind souverän, wobei T Cloud Public durch den vollständig EU-basierten Betrieb und die Zertifizierungen (BSI C5, ISO 27001) eine höhere technische und operative Souveränität aufweist.

Welcher Anbieter ist preislich attraktiver?

Hikube bietet ein höheres Gesamt-Cost Rating von 6,4/10 im Vergleich zu 4,7/10 bei T Cloud Public. Besonders bei GPU-Instanzen ist Hikube mit 9,7/10 deutlich günstiger als T Cloud Public (6,7/10). T Cloud Public punktet hingegen bei RAM (8,2/10) und Block Storage (7,9/10) sowie Saving Plans mit bis zu 48 % Ersparnis. Die tatsächlichen Kosten sind jedoch stark workload-abhängig und sollten im Detail kalkuliert werden.

Welcher Anbieter bietet bessere Hochverfügbarkeit?

Hikube bietet mit einem Score von 10/10 die höchste Hochverfügbarkeit im Vergleichsfeld, da jede Workload aktiv-aktiv über drei Schweizer Rechenzentren (Genf, Gland, Luzern) läuft. T Cloud Public erreicht einen Score von 5/10 und bietet Multi-AZ-Fähigkeiten in 3 Regionen und 9 Availability Zones, jedoch ohne das integrierte 3-AZ-Design von Hikube.

Welcher Anbieter ist besser für KI-Workloads geeignet?

T Cloud Public bietet ein breiteres KI-Portfolio mit AI Foundation Services, ModelArts und Serverless Inference, erzielt jedoch nur einen Score von 2/10. Hikube bietet GPU as a Service mit einem Cost Rating von 9,7/10 und einem AI-Score von 4/10. Für reine GPU-Workloads ist Hikube preislich attraktiver, während T Cloud Public mehr Managed-Dienste für ML-Training und Inference bietet, albeit mit begrenzter Tiefe.

Management Summary

ServiceT Cloud PublicHikube
Count of Services50+20+
Cost Rating4.7/106.4/10
Saving Plan48%–
Datacenter53
Datacenter ModelHybridColocation
Zone SeparationSeparate buildingsSeparate buildings
Server ProductionStandard hardware–
Countries31
SEAL Score7.6/10 (76%)6.9/10 (69%)
USPGerman cloud provider with an independent, broad public cloud portfolio combining shared and dedicated resources, including first serverless capabilities.3 AZ by design: every workload runs active-active across three Swiss datacenters. VM volumes and Kubernetes are replicated by the platform.
RecommendationRecommended for companies in DACH and the Netherlands that operate regionally but require high availability and strong data sovereignty.Recommended for Swiss organisations and regulated mid-sized companies that want built-in HA resilience without designing it themselves.

Sovereign Cloud

ServiceT Cloud PublicHikube
InterpretationEU-based sovereign cloud operated by T-Systems with full GDPR, BSI C5 and KRITIS complianceSwiss operator (ownership chain not publicly evidenced); compute and storage run in three Swiss datacenters, transfers abroad only with consent except in security emergencies or legal obligations. The buildings are colocation sites run by third parties, sub-processor locations are not published, and the platform only opened in 2025
SEALSEAL 3SEAL 3
ResidencyGermanySwitzerland
Shared ResourcesT Cloud PublicCloud Instances
Dedicated ResourcesDedicated Hosts–
EncryptionKey Management ServiceVault as a Service (secrets management in the Swiss tenant)
Ownership & controlFederal Republic of Germany 14.22 % + KfW 14.37 % (Deutsche Telekom AG, parent of T Cloud Public; IR shareholder structure)Hidora SA, Petit-Lancy, Switzerland (not EU), CHE-286.910.173 (commercial register GE/Zefix; AG since 2016, capital CHF 144,750 in restricted registered shares)
EU governance & oversightNo separate sovereignty board (oversight by Deutsche Telekom AG's 20-member co-determined supervisory board, chair F. Appel)No independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC)
Third-country access riskNo US/CN parent; contract under German law (with Telekom Deutschland GmbH)Hidora SA, Switzerland (not EU) (ownership chain not publicly evidenced)
Contracting entity & jurisdictionContracting party Telekom Deutschland GmbH, Bonn (GTC IT services 4 Aug 2025 cl. 1; HRB 5919)Contracting party HIDORA SA, Petit-Lancy; Swiss law, Geneva courts (GTC October 2026 clause 21; CHE-286.910.173; Switzerland (not EU))
Transparency on authority requestsGroup transparency report, annual since 2014 (2025: 36,337 interceptions, 53,754 subscriber data)No transparency report on government requests (checked: security & compliance, CLOUD Act guide (2026-06-10, upd. 2026-08-21), resources, blog)
Data residency incl. backups/DREU-DE served from data centres in Germany, EU-NL from the Netherlands (service description 9 Oct 2026 sec. 2.1)Operated from Swiss DCs: Geneva (Plan-les-Ouates), Gland, Lucerne (Hikube service agreement October 2026, clause 3 and Annex A; Switzerland (EU adequacy decision))
Metadata & support data residencyDPA covers only processing of customer data on behalf (Apr 2026: no third countries without adequacy decision; sub-processors in DE, NL, HU, SK, RO, ES)Ancillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support)
AI services: processing & trainingCategory-1 models operated by Telekom, prompts and results not stored, no training (Llama 3.3, Mistral Small 3, Qwen3; 'in EU/EEA or adequacy countries'; Enterprise Trust docs v1.2.0)Not applicable: no managed AI service (GPU as a Service only, 6 NVIDIA cards L4–H200 on VMs/node groups; 'no opaque ML PaaS')
Dedicated / segregated environmentDedicated Host: physical servers for ECS (extra security layer at the physical level, e.g. s2 with 72 or 144 vCPUs)Managed Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant)
EU operations & supportSub-processors only in DE, NL, HU, SK, RO, ES (DPA April 2026 Annex IV; access only in exceptional cases after separate customer approval)Support by Hidora SA engineers in Geneva (support page 2026-08-23; business days 08:00–18:00 CET, 24×7 infrastructure on-call)
Technical operator lock-outConfidential computing only as Intel SGX enclaves (ECS flavor c7t (physical); applications must be SGX-ready)No confidential computing, no attestation, no HYOK
Disconnected / autonomous operationRegions EU-DE/EU-NL from own data centres, no hyperscaler substrate (service description sec. 2.1)Control plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU))
Hardware origin & manufacturingOnly public statement: provider blog of 23 Jul 2020 (x86 servers/network gear from Huawei and Western vendors, CPUs/GPUs Intel/NVIDIA, dual-vendor strategy)Only the GPU vendor disclosed: NVIDIA (six cards L4 24G, L40S 48G, A100 80G, RTX 6000 Pro 96G, H100 80G, H200 141G)
Critical software dependenciesCloud OS is the Huawei OpenStack Distribution (blog 23 Jul 2020; T-Systems reviews all (security) fixes, Huawei only third-level support, no platform access)Partially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager)
Open-source share & patch authorityIaaS based on OpenStack technology (service description as of 09.10.2026; OpenStack APIs and standard CLI tools usable)Managed OSS services: OpenBAO, Harbor/Trivy, Grafana, MariaDB (release notes Hikube v1.1.2 (19 Mar 2026); OpenBAO = open-source fork of HashiCorp Vault; RabbitMQ)
Portability & exitData Act switching: request ≥30 days ahead, 30-day window (Art. 26; free outbound traffic during the switch)Reversibility: return 'in a reasonable standard format' (GTC Oct 2026 cl. 9.2; content kept thirty (30) days after termination, then deletion (Annex D cl. 11))
IaC & automationTerraform provider opentelekomcloud v1.37.11 (Registry, published 22 Oct 2026, tier community; source on GitHub)Public REST/JSON API with OpenAPI 2.0 specification (api.hikube.cloud: VMs, disks, S3 buckets, Kubernetes, VPC, databases, backups, GPU, pricing)
Key sovereignty (BYOK/HYOK, EU HSM)KMS with FIPS 140-2 Level 3 HSMs, BYOK (service description sec. 3.9.2; keys not exportable (switching page))Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM')
Certifications & scopeBSI C5 Type II attestation (ISAE 3000, EY) (Open Telekom Cloud from data centres in Germany and the Netherlands, 1 Jan 2024–31 Oct 2024)ISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only)
Public audit evidenceISO certificates freely downloadable (incl. ISO/IEC 27001, 27017, 27018)Public only: GTC, Hikube contract, privacy notice, status page
EU labels & schemesGaia-X founding membership per own press release, no service label (Jun 2021, DT incl. T-Systems)No EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU))
Energy & CO₂ transparencyProvider-stated PUE per site: Biere/Magdeburg 1.28 (Aalsmeer/Almere 1.46/1.40; 100 % electricity from renewable sources)'No PUE published'; 100% renewable power at three sites (infrastructure page; Gland approx. 6.9 g CO₂-eq/kWh, Geneva waste heat up to 4.4 MW (CAD-ZIPLO))
Climate commitmentsT-Systems in the Climate Neutral Data Centre Pact since 2021 (certified member since 2023; energy management to ISO 50001)No own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register)
Dedicated Cloud–Hikube (on Prem) on Request

SEAL Framework

ServiceT Cloud PublicHikube
Sovereignty Score7.6/10 (76%) Operated by T-Systems in DE, NL and CH, certified; cloud OS is Huawei's OpenStack distribution6.9/10 (69%) Swiss operator (ownership chain not publicly evidenced) on an open-source stack in colocation sites; own compliance certification ISO 27001
SOV-1 Strategic (15 %)Deutsche Telekom ownership, significant German state stakeFounder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025
SOV-2 Legal & Jurisdictional (10 %)German jurisdiction, T-Systems operatedSwiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU
SOV-3 Data & AI (10 %)Customer data only in DE, NL or CH datacenters (CH: T Cloud Switzerland)Data in three Swiss datacenters; transfers abroad only with consent, except in security emergencies or legal obligations; dedicated GPUs, but no managed AI services
SOV-4 Operational (15 %)Operated by T-Systems from DE, NL and CH; support teams based in EuropeOperated and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators
SOV-5 Supply Chain (20 %)Servers from Huawei and Western vendors (dual-vendor), cloud OS from Huawei; partner change possible per Telekom (blog 2020), no exit documentedColocation in three third-party buildings (Stack Infrastructure, backed by US investor IPI Partners, in Geneva and Gland; EWL in Lucerne); hardware sourced on the global market
SOV-6 Technology (15 %)OpenStack & Kubernetes based; OpenStack distribution supplied by HuaweiOpen-source, Kubernetes-native stack (Talos Linux, Cilium, OpenBAO, upstream PostgreSQL/MariaDB/Redis/Kafka), S3 API, kubectl/Helm/GitOps, VMDK/QCOW2/ISO import; hypervisor and storage layer not disclosed
SOV-7 Security & Compliance (10 %)BSI C5, ISO 27001, TISAXISO 27001 (operator ISMS, certified by SQS; certificate not published online); no C5, SOC 2, ISO 27017/27018; SLA 99.99% per service published (GPU passthrough and preview services excluded); RPO/RTO not published (Hidora states < 5 min, publication announced)
SOV-8 Environmental (5 %)DT climate targets, renewable energy100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates

Availability & Locations

ServiceT Cloud PublicHikube
Presence DACHGermanySwitzerland
Presence EuropeGermany Biere, MagdeburgSwitzerland Geneva (Plan-les-Ouates), Gland, Lucerne
Availability Zones93
Multi-AZ✓ verfügbar✓ verfügbar
Regions31
Countries31
Continents11
DDoS✓ verfügbar–

Compute

ServiceT Cloud PublicHikube
Shared InstanceElastic Cloud Server (ECS) 1vCPU-64vCPUCloud Instances s1 / u1 / m1, 1vCPU-64vCPU
Dedicated InstanceDedicated Host–
GPU InstanceECS - GPU acceleratedGPU Cloud NVIDIA L4, L40S, A100, RTX 6000 Pro, H100, H200
AI AcceleratorIndustrial AI Cloud NVIDIA DGX B200 / RTX PRO 6000, Run:ai scheduler, NVIDIA AI Enterprise; Munich–
Confidential ComputingElastic Cloud Server c7t Intel SGX–
Windows ServerElastic Cloud Server Windows Server public imagesWindows Server licence (incl. 2025, per vCPU)
ServerlessFunction Graph–
Virtual Private Server\nshared & low-budgetTelekom Webhosting–

Hot Storage

ServiceT Cloud PublicHikube
Block StorageElastic Volume ServiceBlock Storage 3x Replicated NVMe, sync or async across 3 datacenters
AssetsObject Storage ServiceSwiss S3 Object Storage (S3 API, WORM)
FileScalable File Service–

Cold Storage

ServiceT Cloud PublicHikube
VM BackupCloud Backup & RecoveryBackup as a Service
Volume BackupCloud Backup & RecoveryVelero (Kubernetes add-on)
ArchiveCloud Backup & Recovery–
Disaster RecoveryStorage Disaster Recovery Service3-datacenter replication by design (restart on the remaining sites)

Managed Databases

ServiceT Cloud PublicHikube
MySQLRDS for MySQLManaged MariaDB
PostGreRDS for PostgreSQLManaged PostgreSQL (CloudNativePG)
MS SQLRDS for SQL Server–
OracleOracle-optimized (Beta) OCI-compatible VMs on Oracle PCA, BYOL, self-managed–
Document-OrientedDocument Database ServiceManaged MongoDB
Distributed Wide-ColumnGeminiDB (Cassandra API)Managed ClickHouse
TSDBGeminiDB Influx API (EU-DE)–
CacheDistributed Cache ServiceManaged Redis (Sentinel)
Search EngineCloud Search Service–
VectorRDS for PostgreSQL (pgvector)Managed Qdrant

Network & Security

ServiceT Cloud PublicHikube
NetworkVirtual Private CloudVPC & Subnets
Public IPElastic IPPublic IPv4
GatewayNAT Gateway–
Load BalancerElastic Load BalanceManaged Ingress (ingress-nginx, Gateway API)
Public DNSDomain Name Service–
Private DNSDomain Name Service (private zones within VPC)–
FirewallCloud FirewallPer-VM firewall (allowed inbound ports on the public IP; SSH 22 default, HTTP/HTTPS optional)
Private ConnectivityVirtual Private Network (VPN)Site-to-site VPN (on request)
Dedicated ConnectivityDirect Connect–
DDoS ProtectionAnti-DDoS–

Orchestration

ServiceT Cloud PublicHikube
Container RegistrySoftware Repository for ContainerRegistry as a Service
OrchestrationCloud Container Engine (Kubernetes)Managed Kubernetes

Virtualization

ServiceT Cloud PublicHikube
HypervisorKVM (OpenStack-based)Not disclosed (VM layer operated by Hikube; VMDK / QCOW2 / ISO import)
Instance as a ServiceElastic Cloud ServerCloud Instances
Bare Metal VirtualizationBare Metal Server–

Management

ServiceT Cloud PublicHikube
Identity ManagementIdentity & Access ManagementOrganizations & Projects (isolated projects with quotas, members and roles; API keys per project)
IaCTerraform ProviderHikube public API (REST/JSON, OpenAPI 2.0 spec)
Audit TrailCloud Trace Service–
Mail ServiceSecure Mail Gateway–
Command LineOTC-Authkubectl / Helm
CollaborationSovereignDesk (OpenTalk, Matrix, Office)–
CO2 CalculatorSustainability Dashboard (per-tenant energy and emissions data)–

Big Data

ServiceT Cloud PublicHikube
DashboardsCloud Eye & AOMGrafana (Monitoring Agents add-on, per cluster)
Data StreamingDistributed Message Service (Apache Kafka)Managed Kafka
MessagingDistributed Message Service (Kafka, RocketMQ)Managed RabbitMQ
Business AnalyticsBusiness Analytics–
Big Data ProcessingData Lake Insight–
Big Data PlattformData Warehouse ServiceManaged ClickHouse (OLAP)
Log MonitoringLog Tank ServiceMonitoring Agents add-on

AI & Machine Learning

ServiceT Cloud PublicHikube
AssistantAI Foundation Services SmartChat (managed RAG, deep research), operated on T-Cloud Germany–
NLPAI Foundation Services LLM Serving API (GPT-OSS, Qwen, GLM, Mistral, Gemma, GPT, Claude, Gemini)–
Machine LearningModelArts Training & InferenceGPU as a Service (dedicated NVIDIA GPUs on VMs or Kubernetes node groups)
Document IntelligenceOCR–
Audio AnalysisAI Foundation Services Whisper Large v3 / v3 Turbo speech-to-text & translation, T-Cloud Germany–
Computer VisionAI Foundation Services vision LLMs: Qwen 3.8 27B / 3.6 35B, Gemma 4, Mistral Small 4, GLM 5.3 Flash (T-Cloud)–
Image GenerationAI Foundation Services GPT Image 2 / Gemini 3 Pro Image, forwarded to Azure / Google Cloud–
Large Language ModelsAI Foundation Services open models on T-Cloud (DE); Claude and Gemini via Google Cloud, GPT via Azure–
EmbeddingsAI Foundation Services–
Serverless InferenceShared LLM Serving Service OpenAI-compatible, pay-per-token, self-service via T-Cloud Marketplace–
Dedicated InferenceDedicated LLM Serving reserved GPUs (e.g. NVIDIA DGX B200), fixed monthly fee, no RPM/TPM caps–
Service TiersEssential / Professional / Agentic min. 1k / 3k / 5k €/month, ~300 / 600 / 1,000 RPM; Premium models from Professional–
Fine-TuningAIFS fine-tuning (on request) optional service per Service Description; self-service API withdrawn–
AI Data PolicyT-Cloud models: EU/EEA processing prompts and results not stored, not viewable by Telekom or third parties–
AI AgentsT-AI Agent Platform Telekom-operated n8n on dedicated T Cloud; LLMs via AIFS or BYOLLM; shared tier Q2 2027–
RAG & GroundingSmartChat knowledge bases fully managed document RAG via UI or API, 50+ retrieval settings, run in DE–
Prompt CachingPrefix caching (T-Cloud models) automatic, on by default; cached prompt tokens billed at 15 % of input price–
Sovereign / On-Prem AIAIFS in customer-owned environment optional service: LLM serving installed on customer infrastructure (feasibility check)–

LLM Models

ServiceT Cloud PublicHikube
Qwen3.6-35B-A3B (Alibaba Cloud · open weights)✓ verfügbar · 256k Kontext–
Qwen3.8-27B (Alibaba Cloud · open weights)✓ verfügbar · 256k Kontext–
Claude Fable 5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Haiku 4.5 (Anthropic · proprietary)✓ verfügbar · 200k Kontext (auslaufend)–
Claude Opus 4.6 (Anthropic · proprietary)✓ verfügbar · 200k Kontext (auslaufend)–
Claude Opus 4.8 (Anthropic · proprietary)✓ verfügbar · 200k Kontext (auslaufend)–
Claude Opus 5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Opus 5.5 (Anthropic · proprietary)✓ verfügbar–
Claude Sonnet 4.6 (Anthropic · proprietary)✓ verfügbar · 200k Kontext (auslaufend)–
Claude Sonnet 5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Sonnet 5.5 (Anthropic · proprietary)✓ verfügbar–
DiffusionGemma 26B A4B (Google · open weights)✓ verfügbar · 256k Kontext (Preview)–
Gemini 3 Flash (Google · proprietary)✓ verfügbar · 1M Kontext–
Gemini 3 Pro (Google · proprietary)✓ verfügbar · 1M Kontext (auslaufend)–
Gemini 3.1 Pro (Google · proprietary)✓ verfügbar · 1M Kontext–
Gemini 3.5 Flash (Google · proprietary)✓ verfügbar · 1M Kontext–
Gemini 3.8 Flash (Google · proprietary)✓ verfügbar–
Gemma 4 31B (Google · open weights)✓ verfügbar · 102k Kontext–
Mistral Medium 3 (Mistral AI · proprietary)✓ verfügbar · 128k Kontext–
Mistral Small 4 (119B) (Mistral AI · open weights)✓ verfügbar · 256k Kontext–
Nemotron 3 Super 120B-A12B (NVIDIA · open weights)✓ verfügbar · 1M Kontext–
GPT-5 (OpenAI · proprietary)✓ verfügbar · 400k Kontext (auslaufend)–
GPT-5 mini (OpenAI · proprietary)✓ verfügbar · 400k Kontext (auslaufend)–
GPT-5-Codex (OpenAI · proprietary)✓ verfügbar · 400k Kontext (auslaufend)–
GPT-5.4 (OpenAI · proprietary)✓ verfügbar · 400k Kontext (auslaufend)–
GPT-5.4 mini (OpenAI · proprietary)✓ verfügbar · 400k Kontext (auslaufend)–
GPT-5.5 (OpenAI · proprietary)✓ verfügbar · 400k Kontext (auslaufend)–
GPT-5.6 Luna (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-5.6 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-5.6 Terra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6 Luna (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6.1 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
gpt-oss-120b (OpenAI · open weights)✓ verfügbar · 128k Kontext–
GLM-5.2 (Z.ai · open weights)✓ verfügbar · 1M Kontext–
GLM-5.3-Flash (Z.ai · open weights)✓ verfügbar · 1M Kontext–

Embedding Models

ServiceT Cloud PublicHikube
Qwen3-Embedding-8B (Alibaba Cloud)✓ verfügbar (T-Cloud Germany, multilingual, 32k context)–
BGE-M3 (BAAI)✓ verfügbar (T-Cloud Germany, 8k context)–
jina-embeddings-v2-base-de (Jina AI)✓ verfügbar (T-Cloud Germany, German-focused, 8k context)–
text-embedding-ada-002 (OpenAI)✓ verfügbar (forwarded to Microsoft Azure (EU regions))–

Compliance & Certificates

ServiceT Cloud PublicHikube
C5\nGerman cloud security catalogue✓ verfügbar–
ISO 20000\nIT service management system standard✓ verfügbar–
ISO 27001\nInformation security management system✓ verfügbar✓ verfügbar
ISO 27017\nCloud security controls for providers✓ verfügbar–
ISO 27018\nPersonal data protection for cloud✓ verfügbar–
ISO 27701\nPrivacy information management extension✓ verfügbar–
ISO 50001\nEnergy management for data centers✓ verfügbar–
SOC 1,2,3\nService organization control audit reports✓ verfügbar–
ISO 9001\nQuality management system standard✓ verfügbar–

Cost Indication

ServiceT Cloud PublicHikube
Rating4.7/106.4/10
CPU vCPU/h3.0/10 0,0513620 €6.2/10 0,0119212 €
GPU H100/h6.7/10 5,2200000 €9.7/10 2,9785142 €
RAM GB/h8.2/10 0,0014419 €3.0/10 0,0119212 €
Managed MySQL Ratio1/43.3/10 0,0881790 €4.2/10 0,0744966 €
Block Storage GB/h | 3000 IOPS7.9/10 0,0000904 €5.7/10 0,0002719 €
S3 Storage GB/h3.5/10 0,0000332 €4.0/10 0,0000298 €
Archive Storage GB/h4.2/10 0,0000181 €–
Tape GB/h3.0/10 0,0000063 €–
Kubernetes-Service-Premium Cluster/h3.0/10 0,1333950 €8.5/10 0,0476848 €
Serverless-Request per 1 Mil Requests7.5/10 0,1700000 €–
Serverless-Compute GB-Sec7.0/10 0,000014 €–
Generative AI-Token Input Qwen3.8-27B per 1Mil tokens6.1/10 0,5000000 €–
Generative AI-Token Output Qwen3.8-27B per 1Mil tokens4.2/10 2,5000000 €–
Generative AI-Token Input gpt-oss-120b per 1Mil tokens6.2/10 0,2000000 €–
Generative AI-Token Output gpt-oss-120b per 1Mil tokens3.4/10 0,6500000 €–
Egress per GB3.5/10 0,0744890 €10.0/10 0,0000000 €

Einzelprofile