Vendor-neutraler Direktvergleich von IBM Cloud und Hikube: Services, Rechenzentren, Kosten und Souveränität — datenbasiert auf comparison.cloud.
IBM Cloud positioniert sich als Enterprise-Hybrid-Cloud mit tiefem Portfolio in Confidential Computing, Big Data und KI, operiert jedoch unter US-Jurisdiktion, was die operative Souveränität einschränkt. Hikube ist ein Schweizer Anbieter, der durch ein architektonisch integriertes 3-AZ-Design über Genf, Gland und Luzern maximale operative Resilienz und technologische Souveränität bietet, jedoch ein deutlich kleineres Service-Portfolio aufweist. Während IBM Cloud für komplexe, globale Enterprise-Anforderungen mit hohem Bedarf an Datenanalyse und Verschlüsselungshoheit geeignet ist, richtet sich Hikube an Schweizer und regulierte Organisationen, die auf lokale Betriebsführung und aktive Multi-Site-Redundanz ohne eigene Design-Aufwände setzen. Der entscheidende Unterschied liegt im Trade-off zwischen globaler Portfolio-Breite und technischer Tiefe (IBM) versus regionaler Souveränität und architektonischer Resilienz (Hikube).
IBM Cloud ist ein globaler Hyperscaler mit einem sehr breiten Portfolio in KI, Big Data und Confidential Computing, operiert jedoch unter US-Jurisdiktion. Hikube ist ein Schweizer Anbieter mit einem fokussierten Portfolio, das auf operative Souveränität und ein integriertes 3-AZ-Design für maximale Resilienz setzt. Während IBM auf globale Reichweite und technische Tiefe setzt, priorisiert Hikube lokale Kontrolle und architektonische Redundanz.
Hikube erzielt einen höheren SEAL Score von 6,9/10 (69%) im Vergleich zu 4,9/10 (49%) bei IBM Cloud. Dies liegt vor allem an der operativen Souveränität (8/10 bei Hikube vs. 3/10 bei IBM Cloud) und der technologischen Souveränität (9/10 bei Hikube vs. 6/10 bei IBM Cloud). IBM Cloud unterliegt als US-Konzern dem CLOUD Act, was die jurisdiktionelle Unabhängigkeit einschränkt.
Hikube hat ein insgesamt höheres Cost Rating von 6,4/10 im Vergleich zu 5,8/10 bei IBM Cloud. Besonders bei GPU-Instanzen ist Hikube mit 9,7/10 deutlich günstiger als IBM Cloud mit 3,0/10. Bei CPU-Instanzen liegt IBM Cloud mit 3,7/10 unter Hikube (6,2/10). Die tatsächlichen Kosten sind jedoch stark workload-abhängig und hängen von der genauen Konfiguration und den genutzten Services ab.
Hikube bietet mit einem Score von 10/10 die höchste Resilienz im Vergleichsfeld, da jede Workload aktiv-aktiv über drei Schweizer Rechenzentren (Genf, Gland, Luzern) läuft. IBM Cloud bietet Multi-AZ-Designs in 13 Regionen mit 30+ Availability Zones, was für globale Ausfallsicherheit geeignet ist, aber nicht die gleiche integrierte Multi-Site-Architektur innerhalb einer Region bietet wie Hikube.
IBM Cloud bietet mit einem Score von 9/10 (Ø aller Anbieter: 7,5/10) ein umfassendes Netzwerk-Portfolio, das VPC, Load Balancer, DDoS-Schutz und CDN-Dienste umfasst. Hikube hat hier einen Score von 4/10, da fortgeschrittene SDN-Funktionen, DDoS-Schutz und CDN-Dienste im aktuellen Portfolio nicht verfügbar sind.
| Service | IBM Cloud | Hikube |
| Interpretation | US parent company despite EU regions, IBM Cloud for Financial Services and KYOK on FIPS 140-2 Level 4, IBM Cloud remains subject to the US CLOUD Act and FISA 702 | Swiss 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 |
| SEAL | SEAL 1 | SEAL 3 |
| Residency | US | Switzerland |
| Shared Resources | IBM Cloud Virtual Server for VPC | Cloud Instances |
| Dedicated Resources | IBM Cloud Bare Metal Servers | – |
| Dedicated Cloud | IBM Cloud Satellite IBM Cloud services on customer on-premises, edge or other-cloud infrastructure | Hikube (on Prem) on Request |
| Encryption | Hyper Protect Crypto Services (KYOK, FIPS 140-2 Level 4) | Vault as a Service (secrets management in the Swiss tenant) |
| Ownership & control | Ultimate parent International Business Machines Corp., Armonk (NY) (Form 10-K for the period ending 31 Dec 2025, filed with the SEC 24 Feb 2026) | 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 & oversight | No independent EU body with veto or oversight rights (over IBM Cloud EU operations) | No independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC) |
| Third-country access risk | US corporation: CLOUD Act and FISA apply | Hidora SA, Switzerland (not EU) (ownership chain not publicly evidenced) |
| Contracting entity & jurisdiction | Country-specific IBM client agreement, entity not named (Terms of Use: DE/AT/BE/NL/DK/FI/IE/LU/SE and other countries) | 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 requests | Semiannual Law Enforcement Requests Transparency Report (by requesting country and data location) | 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/DR | Client data stored and processed in the selected region (IBM product blog; EU MZRs Frankfurt and Madrid) | 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 residency | EU Supported setting restricts support cases to EU teams (but 'processing activities might be performed by teams that are outside of the EU region') | Ancillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support) |
| AI services: processing & training | watsonx.ai: prompts, outputs, tuning data not used for training (not logged; docs) | 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 environment | IBM Cloud Satellite: dedicated management plane per location (in an IBM Cloud multizone metro; etcd not shared with other customers) | Managed Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant) |
| EU operations & support | EU Supported Cloud: access only by EU-based personnel (IBM Cloud Service Description i126-6605-28 §2.1) | 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-out | Confidential computing for x86 VPC in 'preview' only (Intel TDX/SGX with attestation; Frankfurt (eu-de) only, few profiles) | No confidential computing, no attestation, no HYOK |
| Disconnected / autonomous operation | Satellite: workloads keep running offline, config blocked (control plane in an IBM Cloud multizone metro via Satellite Link; FAQ) | Control plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU)) |
| Hardware origin & manufacturing | Firmware signed by approved suppliers, IBM secure-boot chain (Virtual Server for VPC; IBM product blog, undated) | Only the GPU vendor disclosed: NVIDIA (six cards L4 24G, L40S 48G, A100 80G, RTX 6000 Pro 96G, H100 80G, H200 141G) |
| Critical software dependencies | Control plane, IAM, hypervisor, OpenShift are IBM/Red Hat (US) | Partially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager) |
| Open-source share & patch authority | Red Hat OpenShift on IBM Cloud based on open-source Kubernetes (IBM sets up the master and patches the control plane (IBM/Red Hat, US)) | 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 & exit | Reduced egress charges for EU clients migrating out (Terms of Use, EU Data Act (Reg. (EU) 2023/2854); France: SREN waiver since January 2026, on request) | 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 & automation | VPC API published as OpenAPI 3.0.0 specification (SDKs for Java, Node, Python and Go 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) | Key Protect Standard: BYOK, multi-tenant, FIPS 140-2 Level 3 | Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM') |
| Certifications & scope | C5:2020 (ISAE 3000) for listed services, reports on request (VPC, Kubernetes, Object Storage, Bare Metal, Schematics; regions not named, Type 1/2 not stated) | ISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only) |
| Public audit evidence | ISO 27001 certificates publicly linked (IBM Cloud infrastructure, IBM Corporation; EU Cloud CoC entry public) | Public only: GTC, Hikube contract, privacy notice, status page |
| EU labels & schemes | EU Cloud Code of Conduct Level 2, 27 IBM Cloud services (ID 2023LVL02SCOPE5316, assessed 25 Jun 2026, public register) | No EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU)) |
| Energy & CO₂ transparency | Weighted average data-center PUE 1.39, 85 % renewable electricity (IBM 2025 environmental reporting; 44 data centers on 100 % renewable electricity) | '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 commitments | ISO 50001:2018 certified by Bureau Veritas, valid to July 2027 (certificate US020128, version 3) | No own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register) |
| Service | IBM Cloud | Hikube |
| Sovereignty Score | 4.9/10 (49%) US-owned (IBM, NYSE: IBM); CLOUD Act exposure despite strong EU regions and KYOK | 6.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 %) | US corporation IBM, no EU control | Founder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025 |
| SOV-2
Legal & Jurisdictional (10 %) | US jurisdiction, CLOUD Act & FISA 702 | Swiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU |
| SOV-3
Data & AI (10 %) | EU regions Frankfurt/Madrid, watsonx AI | 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 %) | Global operations, no EU-only staffing | Operated and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators |
| SOV-5
Supply Chain (20 %) | Own hardware (Power, LinuxONE, Telum), own datacenters | Colocation 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 %) | Red Hat OpenShift and open standards, but proprietary platform | Open-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 %) | C5, BaFin, TISAX, DORA, GDPR; FIPS 140-2 Level 4 | ISO 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 %) | No specific environmental certification verified in research | 100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates |
| Service | IBM Cloud | Hikube |
| granite-embedding-278m-multilingual (IBM) | ✓ verfügbar (768 dim, 512 tokens; available incl. Frankfurt and London) | – |
| slate-30m-english-rtrvr-v2 (IBM) | ✓ verfügbar (deprecated; withdrawal 12.01.2027) (auslaufend) | – |
| slate-125m-english-rtrvr-v2 (IBM) | ✓ verfügbar (deprecated; withdrawal 12.01.2027) (auslaufend) | – |
| multilingual-e5-large (Microsoft) | ✓ verfügbar (1,024 dim, 512 tokens) | – |
| all-MiniLM-L6-v2 (Sentence Transformers) | ✓ verfügbar (deprecated; withdrawal 12.01.2027) (auslaufend) | – |
| Service | IBM Cloud | Hikube |
| C5\nGerman cloud security catalogue | ✓ verfügbar | – |
| ISO 27001\nInformation security management system | ✓ verfügbar | ✓ verfügbar |
| ISO 20000\nIT service management system standard | ✓ 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 | – |
| CSA STAR\nCloud Security Alliance assurance registry | ✓ verfügbar | – |
| SOC 1,2,3\nService organization control audit reports | ✓ verfügbar | – |
| PCI DSS\nPayment card data security standard | ✓ verfügbar | – |
| ISO 9001\nQuality management system standard | ✓ verfügbar | – |