Vendor-neutraler Direktvergleich von AWS und Hikube: Services, Rechenzentren, Kosten und Souveränität — datenbasiert auf comparison.cloud.
AWS positioniert sich als globaler Hyperscaler mit dem breitesten Service-Portfolio (Strategische Möglichkeiten 10/10) und starker technischer Tiefe in Bereichen wie Datenbanken und Netzwerk, was ihn für internationale Skalierung und komplexe Innovationen prädestiniert. Im Gegensatz dazu ist Hikube ein spezialisierter Schweizer Anbieter, der durch ein architektonisch integriertes 3-AZ-Design über Genf, Gland und Luzern eine hohe operative Resilienz (Hochverfügbarkeit 10/10) und technologische Souveränität (9/10) bietet. Während AWS mit einem SEAL-Score von 4,1/10 und US-Jurisdiktion punktet, liegt der Fokus von Hikube auf europäischer Unabhängigkeit mit einem SEAL-Score von 6,9/10. Für Unternehmen mit strengen Souveränitätsanforderungen und Fokus auf den Schweizer Markt ist Hikube die passende Wahl, während AWS für Organisationen mit globalem Footprint und Bedarf an einem umfassenden Ökosystem von Big Data bis AI die erste Option darstellt.
AWS ist ein globaler Hyperscaler mit einem breiten Portfolio von über 200 Services (Strategische Möglichkeiten 10/10) und starker globaler Reichweite (9/10). Hikube ist ein spezialisierter Schweizer Anbieter, der sich auf technologische Souveränität (9/10) und ein integriertes 3-AZ-Design für maximale Resilienz (10/10) konzentriert, jedoch ein kleineres Portfolio (3/10) bietet.
Hikube ist im SEAL-Framework souveräner mit einem Score von 6,9/10 (69%) im Vergleich zu AWS mit 4,1/10 (41%). Dies liegt an der Schweizer Jurisdiktion und dem Open-Source-Stack von Hikube, während AWS durch die US-Jurisdiktion und proprietäre Technologien (Technologische Souveränität 4/10) eingeschränkt ist.
Hikube hat ein besseres Gesamt-Cost Rating von 6,4/10 im Vergleich zu AWS mit 5,4/10. Besonders bei GPU-Instanzen ist Hikube mit 9,7/10 deutlich günstiger als AWS mit 5,5/10. Bei CPU-Instanzen liegt AWS mit 3,8/10 unter Hikube mit 6,2/10. Die tatsächlichen Kosten sind jedoch stark workload-abhängig.
AWS bietet mit einem Score von 10/10 (Ø alle Anbieter: 7,5/10) umfassende Netzwerk-Funktionen, einschließlich VPC, Load Balancer, DDoS-Schutz und CDN. Hikube liegt hier mit 4/10 unter dem Durchschnitt und bietet grundlegende VPC- und VPN-Funktionen, aber keine fortgeschrittenen SDN- oder CDN-Dienste.
Hikube ist besser geeignet für Workloads, die auf Schweizer Datenhoheit und integrierte Multi-Site-Resilienz angewiesen sind, wie regulierte Mittelständler. AWS ist besser für globale Skalierung, komplexe Big-Data-Analytics und Unternehmen, die ein breites Spektrum an Managed Services und AI-Tools benötigen.
| Service | AWS | Hikube |
| Interpretation | Sensitive data should be encrypted by BYOK. For stronger protection use AWS European Cloud | 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 | AWS European Sovereign Cloud eusc-de-east-1 (Brandenburg), GA since 01/2026 | Cloud Instances |
| Dedicated Resources | EC2 Dedicated Host | – |
| Dedicated Cloud | AWS Outpost Rack | Hikube (on Prem) on Request |
| Encryption | Cloud HSM | Vault as a Service (secrets management in the Swiss tenant) |
| Ownership & control | Ultimate parent Amazon.com, Inc. (Delaware, HQ Seattle) (AWS is a segment per Form 10-K FY2025) | 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 | ESC advisory board of 5 EU citizens, advisory role (2 independent, 3 Amazon; legally bound to the ESC's interest) | No independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC) |
| Third-country access risk | CLOUD Act applies to AWS (US parent) (per AWS to 'any provider with US operations') | Hidora SA, Switzerland (not EU) (ownership chain not publicly evidenced) |
| Contracting entity & jurisdiction | ESCA with the AWS Contracting Party of the customer agreement (as of 14 May 2026; Germany as Account Country (Annex 3): German law, courts of Munich) | 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 | Amazon Government Request Report twice a year (H1 2026, published 31 Jul 2026; requests by country of origin, AWS separate, content disclosures) | 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 | Customer selects the AWS regions; content not moved (AWS Customer Agreement section 1.4 (as of 14 Aug 2026), except to comply with law or a binding order) | 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 | ESC only: Customer-Created Metadata stays in the EU (ESCA section 2.1: tags, resource identifiers, IAM policies; no access by AWS personnel outside the EU) | Ancillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support) |
| AI services: processing & training | Amazon Bedrock: inputs/outputs not used for training (not shared with model providers, stored encrypted in the region used; Bedrock FAQ) | 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 | AWS Outposts: AWS capacity at the customer site (42U racks (1U/2U servers end of sale); local gateway to the on-premises network, service link to the Region) | Managed Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant) |
| EU operations & support | ESC only: operations and support solely by ESC Staff (ESCA §3.1/§8: AWS entity registered in the EU, EU residents/citizens, located in the EU) | 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 | Nitro System: no login to EC2 servers (no access to instance memory or encrypted EBS volumes; Nitro Enclaves add isolation) | No confidential computing, no attestation, no HYOK |
| Disconnected / autonomous operation | ESC 'designed to operate independently and indefinitely' (ESCA section 5.1 (14 May 2026): content retrievable and operated by ESC staff without non-EU infrastructure) | Control plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU)) |
| Hardware origin & manufacturing | Nitro Cards and Nitro Security Chip designed by AWS (hardware root of trust; Nitro whitepaper 15 Feb 2024) | 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 | AWS-proprietary stack from the US, no dependency list (Nitro, control plane, IAM) | Partially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager) |
| Open-source share & patch authority | Own OSS projects, platform proprietary (Firecracker, Bottlerocket, OpenSearch, Valkey, Cedar; Nitro hypervisor, control plane, services) | 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 | Free data transfer out when leaving AWS (request via Support, credits after approval; blog 5 Mar 2024) | 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 | SDK GA versions supported at least 24 months (AWS SDK maintenance policy; maintenance mode announced at least 6 months ahead) | 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 External Key Store (XKS/HYOK): keys stay with the customer (KMS cannot create, view or manage the keys; all regions except China) | Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM') |
| Certifications & scope | BSI C5:2020 for Frankfurt, Paris, Milan, Stockholm, Zurich, Spain (and Ireland, London; design + effectiveness; no SecNumCloud or Grundschutz) | ISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only) |
| Public audit evidence | SOC 1/SOC 2 reports only via AWS Artifact; SOC 3 public (SOC 3 as a whitepaper; ISO certificates public as PDF) | Public only: GTC, Hikube contract, privacy notice, status page |
| EU labels & schemes | CISPE Data Protection CoC: numerous AWS services (Amazon Web Services EMEA SARL, 'Controlled adherence'; monitoring Ernst & Young CertifyPoint, 22 Apr 2026) | No EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU)) |
| Energy & CO₂ transparency | PUE Frankfurt 1.33 / 1.35 / 1.24 (2023–2025) (AWS Sustainability Fact Sheet Germany; WUE 0.01/0.17 L/kWh (2024/2025)) | '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 covers Europe (Frankfurt), 33 sites (EY CertifyPoint no. 2023-021, valid to 2029; ESC Germany with 3 sites) | No own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register) |
| Service | AWS | Hikube |
| 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 | – |
| 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 | – |