Hetzner vs Hikube — Direktvergleich

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

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

Management Summary (Stand 2026-10)

Hetzner und Hikube positionieren sich als europäische Cloud-Anbieter mit unterschiedlichen Schwerpunkten: Hetzner setzt auf kosteneffiziente Compute-Ressourcen und Bare-Metal-Infrastruktur, während Hikube durch ein integriertes 3-AZ-Design in der Schweiz architektonische Resilienz und Managed-Services bietet. Bei der Preisgestaltung für typische IaaS-Workloads liegt Hetzner mit einem Cost Rating von 8,9/10 deutlich vor Hikube (6,4/10), was insbesondere für CPU-lastige Lasten relevant ist. Hikube überzeugt hingegen mit einer Hochverfügbarkeits-Bewertung von 10/10 und einem stärkeren Portfolio an Managed-Diensten wie Kubernetes und Datenbanken, während Hetzner hier Lücken aufweist. Beide Anbieter weisen hohe Werte bei der technologischen Souveränität auf, wobei Hikube mit 9/10 leicht vor Hetzner (8/10) liegt. Für DACH-Teams mit Fokus auf Kosteneffizienz und Bare-Metal eignet sich Hetzner, während Schweizer Organisationen und regulierte Unternehmen, die auf Multi-Site-Resilienz ohne eigenen Design-Aufwand setzen, Hikube bevorzugen sollten.

Hetzner: Stärken

Hetzner: Zu bedenken

Hikube: Stärken

Hikube: Zu bedenken

Hetzner wählen, wenn:

Hikube wählen, wenn:

Häufige Fragen: Hetzner vs Hikube

Was ist der Unterschied zwischen Hetzner und Hikube?

Hetzner fokussiert auf kosteneffiziente IaaS und Bare-Metal-Infrastruktur mit einem Cost Rating von 8,9/10, während Hikube ein integriertes 3-AZ-Design in der Schweiz bietet und Managed-Services wie Kubernetes und Datenbanken bereitstellt. Hetzner punktet mit Bare-Metal (10/10), Hikube mit Hochverfügbarkeit (10/10) und technologischer Souveränität (9/10).

Welcher Anbieter ist souveräner im Sinne des SEAL-Scores?

Hetzner erzielt einen SEAL Score von 7,4/10 (74%), während Hikube bei 6,9/10 (69%) liegt. Bei der operativen Souveränität liegt Hetzner mit 9/10 vor Hikube (8/10), bei der technologischen Souveränität ist es umgekehrt: Hikube (9/10) vor Hetzner (8/10).

Welcher Anbieter ist günstiger?

Hetzner hat ein Cost Rating von 8,9/10, Hikube liegt bei 6,4/10. Dies deutet darauf hin, dass Hetzner für typische IaaS-Workloads preislich wettbewerbsfähiger ist. Allerdings sind die tatsächlichen Kosten stark von der Workload-Struktur abhängig, insbesondere bei GPU-Nutzung, wo Hikube mit 9,7/10 sehr konkurrenzfähig ist.

Welcher Anbieter bietet bessere Hochverfügbarkeit?

Hikube bietet mit einem Score von 10/10 (Ø aller Anbieter: 6,9) die höchste Resilienz durch das 3-AZ-Design über Genf, Gland und Luzern. Hetzner liegt bei 4/10, was auf eine geringere Multi-AZ-Integration im Vergleich zu Hikube hindeutet.

Welcher Anbieter eignet sich besser für Container-Workloads?

Hikube bietet Managed Kubernetes mit einem Score von 7/10 (Ø aller Anbieter: 7,3) sowie Registry-as-a-Service und FluxCD. Hetzner hat hier einen Score von 1/10, was auf fehlende Managed-Kubernetes-Plattformen hindeutet.

Management Summary

ServiceHetznerHikube
Count of Services15+20+
Cost Rating8.9/106.4/10
Datacenter6 (3 own data-center parks in DE/FI, 3 colocation sites in US/SG)3
Datacenter ModelHybrid (own parks Nuremberg, Falkenstein, Helsinki; colocation in Ashburn, Hillsboro, Singapore)Colocation
Zone SeparationMulti-site onlySeparate buildings
Server ProductionIn-house manufacturing–
Countries41
SEAL Score7.4/10 (74%)6.9/10 (69%)
USPVery strong price-performance IaaS from a German independent Provider on EU-operated data centers, focussing on compute power3 AZ by design: every workload runs active-active across three Swiss datacenters. VM volumes and Kubernetes are replicated by the platform.
RecommendationRecommended for cost-sensitive DACH teams that want a modern data center with basic requirements on bare metal inrastructureRecommended for Swiss organisations and regulated mid-sized companies that want built-in HA resilience without designing it themselves.

Sovereign Cloud

ServiceHetznerHikube
InterpretationGerman-owned, privately held independent with no US parent. The cloud and DACH data centers are operated by German and Finnish EU entities.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
SEALSEAL 3SEAL 3
ResidencyGermanySwitzerland
Shared ResourcesCloud Servers CX / CAX / CPXCloud Instances
Dedicated ResourcesDedicated vCPU–
Ownership & controlHetzner Online GmbH, Ansbach HRB 6089, one known shareholder (ENSoXX Holding AG; holdings include Hetzner Cloud GmbH, Hetzner US LLC)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 independent supervisory or advisory body with veto rights (checked: legal notice (3 managing directors), about us, certification, data-protection docs)No independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC)
Third-country access riskGerman GmbH, no US parent ('Data protection at Hetzner' docs, 2026-07-20)Hidora SA, Switzerland (not EU) (ownership chain not publicly evidenced)
Contracting entity & jurisdictionContracting party Hetzner Online GmbH, Gunzenhausen (DPA template §13.1: German law, exclusive venue Gunzenhausen; Hetzner may also sue at customer's seat)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 requestsNo transparency report on government requests (checked: legal section, DSA page, privacy policy, docs)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/DRProcessing only in EU/EEA, third country only with consent (public DPA template v1.1 (2025-02-10) §3(1); Annex 3: EU location keeps server data in the EU)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 residencyHetzner's own data only in the EU (customer master, contract, billing; 'Data protection at Hetzner' docs)Ancillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support)
AI services: processing & trainingInference models operated entirely on own Hetzner infrastructure (privacy policy §4.5.2: zero retention, no training on prompts; logfiles kept 6 months)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 Root Servers (bare metal: AX, EX, GPU lines) (Nuremberg, Falkenstein/Vogtland and Helsinki; data centers ISO 27001:2022 certified)Managed Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant)
EU operations & supportProcessing exclusively in the EU/EEA (DPA §3)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-outNo confidential computing, attestation, HYOK or external KMSNo confidential computing, no attestation, no HYOK
Disconnected / autonomous operationNo on-prem, air-gapped or local control-plane offering (checked: DC page, cloud, dedicated, colocation, docs)Control plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU))
Hardware origin & manufacturingServers developed in-house, assembled in own hardware department (sustainability page; EMAS site 'Administration and Production', Gunzenhausen; avg. 8-year life)Only the GPU vendor disclosed: NVIDIA (six cards L4 24G, L40S 48G, A100 80G, RTX 6000 Pro 96G, H100 80G, H200 141G)
Critical software dependenciesKVM and Open vSwitch, managed by custom-built tooling (Hetzner blog 2026-10-08; no Proxmox VE, OpenStack or oVirt; OVS orchestration 'Flusskrebs')Partially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager)
Open-source share & patch authorityGitHub org hetznercloud with 33 repos (hcloud CLI (MIT), Terraform provider (MPL-2.0), cloud-controller-manager (Apache-2.0), CSI driver (MIT))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 & exitS3-compatible Object Storage; egress 1 Gbit unlimited on dedicated (10 Gbit 20 TB + €1/TB; cloud EU ≥20 TB incl., +€1/TB)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 & automationOfficial OpenAPI 3.1.2 specification of the Hetzner Cloud API (hcloud CLI and Go/Python libraries 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)No KMS, no HSM, no BYOK/HYOK (TOMs: encryption at rest = customer; no FIPS/CC statements)Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM')
Certifications & scopeISO/IEC 27001:2022 certificationISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only)
Public audit evidencePublic: ISO 27001:2022 certificate, C5 Type 2 attestation, PCI DSS proof (TOMs in the DPA template; PCI DSS proof via Computop)Public only: GTC, Hikube contract, privacy notice, status page
EU labels & schemesNo EU labels (not in CISPE member list, EU Cloud CoC register or CNDCP list; no Cloud III SEAL, no EUCS/C3A)No EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU))
Energy & CO₂ transparencyPUE 1.10–1.16 as annual average across sites, WUE 0 L/kWh (sustainability page; no per-site value)'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 commitmentsEMAS certification for the German sites, not Finland (sustainability page; renewable power since 2008 (DE) and 2018 (FI))No own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register)
Dedicated Cloud–Hikube (on Prem) on Request
Encryption–Vault as a Service (secrets management in the Swiss tenant)

SEAL Framework

ServiceHetznerHikube
Sovereignty Score7.4/10 (74%) German-owned independent; EU-run data centers; ISO 27001 and BSI C5 Type 26.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 %)German privately held, founder-controlled, no US, VC or PE parentFounder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025
SOV-2 Legal & Jurisdictional (10 %)German and Finnish EU entities, no CLOUD Act exposure for the EU regions; US and SG sites under foreign jurisdictionSwiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU
SOV-3 Data & AI (10 %)EU residency for DE and FI; AI only as free experimental Inference API (open Qwen models, zero retention), no production AI PaaSData 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 %)Self-operated own EU data-center parks with EU staff and no outsourcingOperated and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators
SOV-5 Supply Chain (20 %)Owns and operates its EU data centers (colocation in US/SG); hardware sourced from global vendorsColocation 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 %)Open standards, no proprietary lock-inOpen-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 %)ISO/IEC 27001:2022, BSI C5:2020 Type 2 (EU sites) and KRITIS §8a BSIG; no SecNumCloud, SOC 2 or HDSISO 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 %)Renewable power (DE since 2008, FI since 2018), EMAS for German sites, PUE 1.10–1.16; not yet climate-neutral, no ISO 50001/14001100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates

Availability & Locations

ServiceHetznerHikube
Presence DACHGermanySwitzerland
Presence EuropeGermany FalkensteinSwitzerland Geneva (Plan-les-Ouates), Gland, Lucerne
Presence North AmericaUSA Ashburn, Hillsboro (colocation, cloud only)–
Presence Asia-PacificSingapore (colocation, cloud only)–
Availability Zones63
Countries41
Regions4 Network zones1
Continents31
Multi-AZ–✓ verfügbar

Compute

ServiceHetznerHikube
Shared InstanceCloud Server CX 2vCPU-16vCPUCloud Instances s1 / u1 / m1, 1vCPU-64vCPU
ARM InstanceCloud Server CAX 2vCPU-16vCPU–
Dedicated InstanceDedicated Cloud Server CCX 2vCPU-48vCPU–
GPU InstanceDedicated GPU Server GEX45–GEX430 NVIDIA RTX PRO 4000 / 6000 Blackwell, 1–4 GPUs; MIG on GEX63/131/430GPU Cloud NVIDIA L4, L40S, A100, RTX 6000 Pro, H100, H200
Windows ServerWindows Server 2025 (SPLA add-on, Dedicated Server)Windows Server licence (incl. 2025, per vCPU)
Virtual Private Server\nshared & low-budgetWebhosting–

Hot Storage

ServiceHetznerHikube
Block StorageBlock StorageBlock Storage 3x Replicated NVMe, sync or async across 3 datacenters
AssetsObject Storage (S3-compatible, FSN1 / HEL1 / NBG1)Swiss S3 Object Storage (S3 API, WORM)
FileStorage Share (Nextcloud)–

Cold Storage

ServiceHetznerHikube
VM BackupCloud Server Backups (daily, 7 slots)Backup as a Service
Volume BackupStorage BoxVelero (Kubernetes add-on)
Disaster Recovery–3-datacenter replication by design (restart on the remaining sites)

Network & Security

ServiceHetznerHikube
NetworkPrivate Networks (subnets, routes, vSwitch coupling; free of charge)VPC & Subnets
Public IPPrimary IPs / Floating IPs (IPv4, IPv6)Public IPv4
FirewallFirewall statefulPer-VM firewall (allowed inbound ports on the public IP; SSH 22 default, HTTP/HTTPS optional)
Load BalancerLoad BalancerManaged Ingress (ingress-nginx, Gateway API)
DDoS ProtectionDDoS protection (automatic filtering, free of charge for all customers)–
Public DNSDNS Management–
Private Connectivity–Site-to-site VPN (on request)

Management

ServiceHetznerHikube
IaCTerraform (hcloud Provider)Hikube public API (REST/JSON, OpenAPI 2.0 spec)
Command Linehcloud CLIkubectl / Helm
MCP ServerMCP (Third Party)–
CollaborationStorage Share (Managed Nextcloud)–
Identity Management–Organizations & Projects (isolated projects with quotas, members and roles; API keys per project)

Virtualization

ServiceHetznerHikube
HypervisorKVM custom-built tooling, no OpenStackNot disclosed (VM layer operated by Hikube; VMDK / QCOW2 / ISO import)
Instance as a ServiceCloudCloud Instances
Bare Metal VirtualizationDedicated Root Servers (no hypervisor layer)–

AI & Machine Learning

ServiceHetznerHikube
AssistantInference API (Experimental) OpenAI-compatible, Qwen3.6-35B / Qwen3.8-27B–
NLPInference API (Experimental) OpenAI-compatible, Qwen3.6-35B / Qwen3.8-27B–
Computer VisionInference API (Experimental) image input via Qwen3.6-35B-A3B / Qwen3.8-27B–
Large Language ModelsInference API (Experimental) Qwen3.6 and Qwen3.8, OpenAI-compatible–
Serverless InferenceInference API (Experimental) OpenAI-compatible, free while experimental, 10 req/min, no SLA, not for production–
AI Data PolicyZero retention (Inference API) prompts/outputs not stored or trained on; own HW, DC country not named–
Machine Learning–GPU as a Service (dedicated NVIDIA GPUs on VMs or Kubernetes node groups)

LLM Models

ServiceHetznerHikube
Qwen3.6-35B-A3B (Alibaba Cloud · open weights)✓ verfügbar · 262k Kontext (experimentell)–
Qwen3.8-27B (Alibaba Cloud · open weights)✓ verfügbar · 262k Kontext (experimentell)–

Compliance & Certificates

ServiceHetznerHikube
C5\nGerman cloud security catalogue✓ verfügbar–
ISO 27001\nInformation security management system✓ verfügbar✓ verfügbar
PCI DSS\nPayment card data security standard✓ verfügbar–

Cost Indication

ServiceHetznerHikube
Rating8.9/106.4/10
CPU vCPU/h6.2/10 0,0119842 €6.2/10 0,0119212 €
RAM GB/h8.3/10 0,0013900 €3.0/10 0,0119212 €
Block Storage GB/h | 3000 IOPS8.1/10 0,0000784 €5.7/10 0,0002719 €
S3 Storage GB/h10.0/10 0,0000086 €4.0/10 0,0000298 €
Archive Storage GB/h5/10 0,0051 €–
Generative AI-Token Input Qwen3.8-27B per 1Mil tokens10.0/10 0,0000000 €–
Generative AI-Token Output Qwen3.8-27B per 1Mil tokens10.0/10 0,0000000 €–
Egress per GB10.0/10 0,0010000 €10.0/10 0,0000000 €
GPU H100/h–9.7/10 2,9785142 €
Managed MySQL Ratio1/4–4.2/10 0,0744966 €
Kubernetes-Service-Premium Cluster/h–8.5/10 0,0476848 €

Managed Databases

ServiceHetznerHikube
MySQL–Managed MariaDB
PostGre–Managed PostgreSQL (CloudNativePG)
Document-Oriented–Managed MongoDB
Distributed Wide-Column–Managed ClickHouse
Cache–Managed Redis (Sentinel)
Vector–Managed Qdrant

Orchestration

ServiceHetznerHikube
Container Registry–Registry as a Service
Orchestration–Managed Kubernetes

Big Data

ServiceHetznerHikube
Dashboards–Grafana (Monitoring Agents add-on, per cluster)
Data Streaming–Managed Kafka
Messaging–Managed RabbitMQ
Big Data Plattform–Managed ClickHouse (OLAP)
Log Monitoring–Monitoring Agents add-on

Einzelprofile