STACKIT vs Hikube — Direktvergleich

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

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

Management Summary (Stand 2026-10)

STACKIT positioniert sich als souveräne Deutschland-Cloud mit höchster operativer Kontrolle (10/10) und einem starken Fokus auf Datensicherheit (9/10), was durch einen SEAL-Score von 8,2/10 untermauert wird. Im Gegensatz dazu setzt Hikube auf architektonische Resilienz durch ein integriertes 3-AZ-Design über drei Schweizer Standorte, was zu einem Höchstwert bei der Hochverfügbarkeit (10/10) führt, bei einem SEAL-Score von 6,9/10. Während STACKIT ein breiteres Portfolio an Managed Databases (8/10) und Linux-Workloads (10/10) bietet, punktet Hikube mit deutlich günstigeren GPU-Preisen (Cost Rating 9,7/10) und einer stärkeren Ausrichtung auf Containerisierung (7/10). Beide Anbieter sind auf den europäischen Raum fokussiert, wobei STACKIT in Deutschland und Österreich sowie Hikube in der Schweiz operiert. Die Wahl hängt davon ab, ob maximale Compliance und Datenbank-Tiefe (STACKIT) oder integrierte Multi-Site-Resilienz und GPU-Kostenkontrolle (Hikube) im Vordergrund stehen.

STACKIT: Stärken

STACKIT: Zu bedenken

Hikube: Stärken

Hikube: Zu bedenken

STACKIT wählen, wenn:

Hikube wählen, wenn:

Häufige Fragen: STACKIT vs Hikube

Was ist der Unterschied zwischen STACKIT und Hikube?

STACKIT ist eine Deutschland-Cloud mit Fokus auf maximale operative Souveränität (10/10) und ein breites Datenbank-Portfolio (8/10), operiert in Deutschland und Österreich. Hikube ist ein Schweizer Anbieter, der durch ein integriertes 3-AZ-Design über Genf, Gland und Luzern eine hohe Resilienz (10/10) bietet und sich stark auf Containerisierung und günstige GPU-Preise konzentriert.

Welcher Anbieter ist souveräner?

STACKIT erzielt einen höheren SEAL-Score von 8,2/10 (82%) im Vergleich zu 6,9/10 (69%) bei Hikube. Zudem erreicht STACKIT den Höchstwert bei der operativen Souveränität (10/10), während Hikube hier mit 8/10 liegt. Beide Anbieter sind jedoch als EU-/Schweizer Anbieter mit hohem Souveränitätsgrad klassifiziert.

Welcher Anbieter ist preislich attraktiver?

Hikube hat ein höheres Gesamt-Cost Rating von 6,4/10 im Vergleich zu 5,4/10 bei STACKIT. Besonders bei GPU-Instanzen ist Hikube mit 9,7/10 deutlich günstiger als STACKIT (4,5/10). Bei CPU-Instanzen liegt Hikube mit 6,2/10 ebenfalls vor STACKIT (3,8/10). Die tatsächlichen Kosten sind jedoch stark von der spezifischen Workload-Architektur abhängig.

Welcher Anbieter bietet bessere Hochverfügbarkeit?

Hikube bietet mit einem Score von 10/10 die höhere Hochverfügbarkeit, da jede Workload aktiv-aktiv über drei Schweizer Rechenzentren läuft. STACKIT erreicht hier einen Score von 6/10 und bietet 3 Availability Zones in 2 Regionen (Deutschland, Österreich), jedoch ohne das integrierte 3-Standort-Design von Hikube.

Für welche Workloads ist STACKIT besser geeignet als Hikube?

STACKIT ist besser geeignet für Linux-lastige Workloads (10/10 vs. 8/10) und komplexe Datenbank-Anforderungen (8/10 vs. 5/10). Zudem bietet STACKIT ein breiteres Netzwerk-Portfolio (8/10 vs. 4/10) mit DDoS-Schutz und CDN, was für anspruchsvolle Netzwerk-Architekturen vorteilhaft ist.

Management Summary

ServiceSTACKITHikube
Count of Services40+20+
Cost Rating5.4/106.4/10
Datacenter73
Datacenter ModelOwn datacentersColocation
Zone SeparationFire compartmentsSeparate buildings
Server ProductionStandard hardware–
Countries21
SEAL Score8.2/10 (82%)6.9/10 (69%)
USPGerman cloud with BSI C5 Type 2, ISO 27001 and a clear focus on IaaS and PaaS3 AZ by design: every workload runs active-active across three Swiss datacenters. VM volumes and Kubernetes are replicated by the platform.
RecommendationRecommended for organizations prioritizing local security and trustRecommended for Swiss organisations and regulated mid-sized companies that want built-in HA resilience without designing it themselves.

Sovereign Cloud

ServiceSTACKITHikube
InterpretationWith headquarters in the EU, data is inherently sovereign. Additionally, the data can be encrypted at rest and in used by Edgeless SystemsSwiss 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 ResourcesPublic CloudCloud Instances
Dedicated ResourcesDistributed Cloud (SPC Restricted, hardware-separated area in STACKIT datacenters) (angekündigt)–
Dedicated CloudDistributed Cloud (SDC Core, on-prem in customer datacenter) (angekündigt)Hikube (on Prem) on Request
EncryptionConfidential Cloud by Edgeless SystemsVault as a Service (secrets management in the Swiss tenant)
Ownership & controlSchwarz Digits Cloud GmbH & Co. KG, part of Schwarz Group (renamed 2026, formerly STACKIT GmbH & Co. KG; Neckarsulm)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 body with oversight or veto rights published (searched: advisory/supervisory board, governance)No independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC)
Third-country access riskProcessing in EU/EEA, outside only by explicit agreement (DPA 2.4.2 sec. 2.5, Art. 44–48/49 GDPR; processor seated in Bad Friedrichshall, DE)Hidora SA, Switzerland (not EU) (ownership chain not publicly evidenced)
Contracting entity & jurisdictionContracting party Schwarz Digits Cloud GmbH & Co. KG (Bad Friedrichshall; Terms of Use 1.3.2 from 04.05.2026)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 (website, press, docs, privacy notice 5.4 checked)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 in EU/EEA, deviation only by explicit agreement (DPA 2.4.2 sec. 2.5; regions only eu01 (DE), eu02 (AT))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 residencyUsage and log data count as customer data, processed in EU/EEA (DPA 2.4.2 sec. 2.3 and 2.5, annex 1: IP address, log files)Ancillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support)
AI services: processing & trainingAI Model Serving: no storage of request data, no training (FAQ; open-source models only; API endpoint in eu01)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 environmentDistributed Cloud only on the product page (SPC Restricted: hardware separation, Ü2 staff, 'Future VS-NfD-capable')Managed Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant)
EU operations & supportSupport team based in the European Union, channels 24/7 (service description; access to customer services only as needed for the request (A.4))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 Kubernetes with CVMs and remote attestation (Constellation/Edgeless; service sheet 1.2, from 01.12.2025)No confidential computing, no attestation, no HYOK
Disconnected / autonomous operationSDC/Distributed Cloud 'fully air-gapped' in the customer DC (VMs, block storage, Kubernetes; per product page and one-pager)Control plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU))
Hardware origin & manufacturingNo supply-chain or origin disclosures published (Confidential Server on AMD (price list))Only the GPU vendor disclosed: NVIDIA (six cards L4 24G, L40S 48G, A100 80G, RTX 6000 Pro 96G, H100 80G, H200 141G)
Critical software dependenciesOpenStack base with upstream fixes (Nova/Neutron/OVN) (STACKIT post on openinfra.org, 22.09.2025)Partially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager)
Open-source share & patch authority99 public repos on GitHub stackitcloud (Terraform provider Apache-2.0, CLI, Go/Python SDK)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 & exitTwo-month switching notice, export of all input and output data (Terms of Use 1.3.2 (from 04.05.2026), section 6 'Switching')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 Terraform provider, Go SDK, CLI GA (09.09.2025) (Python/Java SDK beta, Pulumi alpha, API Explorer)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: generate or import keys (BYOK) (aes_256_gcm, RSA 2048–4096 (OAEP); export of generated keys not intended)Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM')
Certifications & scopeBSI-IGZ-0691-2025: ISO 27001 on IT-Grundschutz basis (30.04.2025, valid to 29.04.2028)ISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only)
Public audit evidenceISO 27001, 20000, 22301, 50001 certificates public as PDF (BSI certificate in the BSI register)Public only: GTC, Hikube contract, privacy notice, status page
EU labels & schemesCloud III sovereign cloud tender awardee, SEAL-3 group (European Commission news 17.04.2026; IP/26/833 without SEAL level)No EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU))
Energy & CO₂ transparencyPUE below 1.3, 100 % renewable electricity (colocation page, no site reference; ISO 50001, DIN EN 50600, TSI.STANDARD varying by data centre)'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 commitmentsSchwarz Group SBTi targets: −48 % by 2030, −90 % by 2050 (operational emissions vs. 2019, net zero 2050; validated 2025)No own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register)

SEAL Framework

ServiceSTACKITHikube
Sovereignty Score8.2/10 (82%) Schwarz Group owned, DE/AT only; EU sovereign cloud tender awardee 20266.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 %)100% German Schwarz Group ownershipFounder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025
SOV-2 Legal & Jurisdictional (10 %)Exclusively EU (German/Austrian) jurisdictionSwiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU
SOV-3 Data & AI (10 %)Data exclusively in DE/AT datacentersData 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 %)EU personnel, group-owned datacentersOperated and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators
SOV-5 Supply Chain (20 %)Group-owned DCs; standard global hardware sourcingColocation 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-source based platform, low 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 %)BSI C5, ISO 27001ISO 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 %)Green energy powered datacenters100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates

Availability & Locations

ServiceSTACKITHikube
Presence DACHGermanySwitzerland
Presence EuropeGermanySwitzerland Geneva (Plan-les-Ouates), Gland, Lucerne
Availability Zones33
Regions21
Countries21
Continents11
DDoS✓ verfügbar–
Multi-AZ–✓ verfügbar

Compute

ServiceSTACKITHikube
Shared InstanceCompute Engine 1vCPU-120vCPUCloud Instances s1 / u1 / m1, 1vCPU-64vCPU
GPU InstanceCompute Engine GPUGPU Cloud NVIDIA L4, L40S, A100, RTX 6000 Pro, H100, H200
Windows ServerWindows ServerWindows Server licence (incl. 2025, per vCPU)
ARM InstanceARM Flavors (Ampere)–
Confidential ComputingConfidential Server (AMD SEV)–

Hot Storage

ServiceSTACKITHikube
Block StorageBlock StorageBlock Storage 3x Replicated NVMe, sync or async across 3 datacenters
AssetsObject StorageSwiss S3 Object Storage (S3 API, WORM)
FileFile Storage (NFS)–

Cold Storage

ServiceSTACKITHikube
VM BackupBackup StorageBackup as a Service
Volume BackupBackup StorageVelero (Kubernetes add-on)
ArchiveArchiving Service–
Disaster Recovery–3-datacenter replication by design (restart on the remaining sites)

Managed Databases

ServiceSTACKITHikube
MySQLMariaDBManaged MariaDB
MS SQLSQLServer Flex–
PostGrePostGreSQL FlexManaged PostgreSQL (CloudNativePG)
Document-OrientedMongoDB FlexManaged MongoDB
CacheKey Value Store (Valkey)Managed Redis (Sentinel)
Search EngineOpensearch–
VectorPostgreSQL Flex (pgvector)Managed Qdrant
Distributed Wide-Column–Managed ClickHouse

Network & Security

ServiceSTACKITHikube
NetworkNetwork & SecurityVPC & Subnets
Public IPPublic IPPublic IPv4
Load BalancerNetwork Load BalancerManaged Ingress (ingress-nginx, Gateway API)
Public DNSDNS (Anycast)–
FirewallUnified FirewallPer-VM firewall (allowed inbound ports on the public IP; SSH 22 default, HTTP/HTTPS optional)
DDoS ProtectionCDN (DDoS protection)–
Private ConnectivitySTACKIT VPNSite-to-site VPN (on request)
CDNContent Delivery Network–

Orchestration

ServiceSTACKITHikube
Container RegistryContainer Registry (Beta)Registry as a Service
OrchestrationCloud FoundryManaged Kubernetes

Virtualization

ServiceSTACKITHikube
HypervisorKVM OpenStack-based, no direct accessNot disclosed (VM layer operated by Hikube; VMDK / QCOW2 / ISO import)
Instance as a ServiceCompute EngineCloud Instances
Edge VirtualizationDistributed Cloud (edge racks / mobile edge devices) (angekündigt)–

Management

ServiceSTACKITHikube
Identity ManagementIAM (STACKIT IdP, service accounts)Organizations & Projects (isolated projects with quotas, members and roles; API keys per project)
IaCTerraformHikube public API (REST/JSON, OpenAPI 2.0 spec)
Audit TrailAudit Log–
Mail ServiceMailOut (Beta)–
Command LineSTACKIT CLIkubectl / Helm
MCP ServerSTACKIT AI–
CollaborationWorkspace by STACKIT (sovereign Google Workspace)–

Big Data

ServiceSTACKITHikube
DashboardsObservabilityGrafana (Monitoring Agents add-on, per cluster)
Data StreamingIntake (Kafka protocol to Iceberg tables)Managed Kafka
MessagingRabbitMQManaged RabbitMQ
Big Data ProcessingWorkflows (Beta) Apache Airflow–
Big Data PlattformDremio (Public Preview)Managed ClickHouse (OLAP)
Log MonitoringLogMeMonitoring Agents add-on

AI & Machine Learning

ServiceSTACKITHikube
AssistantAI Model Serving Qwen3.8 27B, Qwen3-VL 235B, GPT-OSS 120B/20B, Llama 3.3 70B, Gemma 4 31B–
Computer VisionAI Model Serving image input: Qwen3-VL 235B, Qwen3.8 27B, Gemma 4 31B–
NLPAI Model Serving (E5 Mistral 7B, Qwen3-VL embeddings)–
Machine LearningAI Model ServingGPU as a Service (dedicated NVIDIA GPUs on VMs or Kubernetes node groups)
Large Language ModelsAI Model Serving Qwen, gpt-oss, Llama, Gemma–
EmbeddingsAI Model Serving–
Serverless InferenceAI Model Serving (shared models) pay-per-token, OpenAI-compatible, chat 30–80 RPM, 200–350k TPM (output tokens ×5)–
AI Data PolicyNo storage of request data no training on customer data; open-source models only; endpoint region eu01 (DE)–
Evaluation & ObservabilityAI Model Experiments (Beta) managed MLflow: LLM/agent tracing, LLM-as-a-judge evals, prompt versioning–

LLM Models

ServiceSTACKITHikube
Qwen3-VL-235B-A22B-Instruct (Alibaba Cloud · open weights)✓ verfügbar · 200k Kontext (LLM-Premium category)–
Qwen3.6-27B (Alibaba Cloud · open weights)✓ verfügbar · 262k Kontext (deprecated, migrate by 08.12.2026) (auslaufend)–
Qwen3.8-27B (Alibaba Cloud · open weights)✓ verfügbar · 262k Kontext–
Gemma 4 31B (Google · open weights)✓ verfügbar · 256k Kontext–
Llama 3.3 70B Instruct (Meta · open weights)✓ verfügbar · 128k Kontext–
gpt-oss-20b (OpenAI · open weights)✓ verfügbar · 131k Kontext–
gpt-oss-120b (OpenAI · open weights)✓ verfügbar · 131k Kontext–

Embedding Models

ServiceSTACKITHikube
Qwen3-VL-Embedding-8B (Alibaba Cloud)✓ verfügbar (text + image input, 4096 dim (Matryoshka), 32k input)–
e5-mistral-7b-instruct (Microsoft)✓ verfügbar (4096 dim, 4k input, English-focused)–

Quantum Computing

ServiceSTACKITHikube
EmulatorQuantum (simulators, closed private preview) (angekündigt)–
EngineQuantum (reserved time on European quantum hardware, closed private preview) (angekündigt)–

Compliance & Certificates

ServiceSTACKITHikube
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 50001\nEnergy management for data centers✓ verfügbar–
SOC 1,2,3\nService organization control audit reports✓ verfügbar–
VS-NfD\nGerman classified-information handlingIn preparation SPC Restricted: VS-NfD rollout announced for 2026; security products in BSI review (angekündigt)–

Cost Indication

ServiceSTACKITHikube
Rating5.4/106.4/10
CPU vCPU/h3.8/10 0,0351759 €6.2/10 0,0119212 €
GPU H100/h4.5/10 8,0413472 €9.7/10 2,9785142 €
RAM GB/h5.7/10 0,0040801 €3.0/10 0,0119212 €
Managed MySQL Ratio1/45.5/10 0,0592222 €4.2/10 0,0744966 €
Block Storage GB/h | 3000 IOPS3.0/10 0,0010948 €5.7/10 0,0002719 €
S3 Storage GB/h3.0/10 0,0000364 €4.0/10 0,0000298 €
Archive Storage GB/h4.5/10 0,0214751 €–
Kubernetes-Service-Premium Cluster/h4.6/10 0,0995951 €8.5/10 0,0476848 €
Generative AI-Token Input Qwen3.8-27B per 1Mil tokens8.0/10 0,4500000 €–
Generative AI-Token Output Qwen3.8-27B per 1Mil tokens10.0/10 0,6500000 €–
Generative AI-Token Input gpt-oss-120b per 1Mil tokens3.0/10 0,4500000 €–
Generative AI-Token Output gpt-oss-120b per 1Mil tokens3.4/10 0,6500000 €–
Egress per GB10.0/10 0,0000000 €10.0/10 0,0000000 €

Einzelprofile