Hikube — Cloud-Profil

Interaktive Fassung: https://comparison.cloud/cloud/hikube

Europäischer Anbieter. Jede Workload läuft standardmäßig aktiv-aktiv über drei Schweizer Rechenzentren (Genf, Gland, Luzern), was Multi-Site-Resilienz ohne zusätzliche Konfiguration gewährleistet.

Eckdaten

KennzahlWert
Count of Services20+
Cost Rating6.4/10
Datacenter3
Countries1
SEAL Score6.9/10 (69%)
Stand der Daten2026-10

Empfehlung: Empfohlen für Schweizer Organisationen und regulierte Mittelständler, die integrierte Multi-Site-Resilienz ohne eigenes Design benötigen. Besonders geeignet für Workloads mit hohem GPU-Bedarf, da die Preisattraktivität hier im Vergleichsfeld heraussticht.

Bewertung (Stand: 2026-10)

Hikube ist ein Schweizer Cloud-Anbieter, der durch ein architektonisch integriertes 3-AZ-Design über Genf, Gland und Luzern eine hohe operative Resilienz bietet. Die Plattform punktet mit technologischer Souveränität und günstigen GPU-Preisen, weist jedoch bei Netzwerk, Speicher und strategischen Zusatzdiensten deutliche Einschränkungen im Vergleich zum Marktdurchschnitt auf.

Pro

Contra

Häufige Fragen zu Hikube

Für wen eignet sich Hikube?

Hikube richtet sich an Schweizer Organisationen und regulierte Mittelständler, die auf integrierte Multi-Site-Resilienz angewiesen sind. Die Plattform ist besonders für Workloads mit hohem GPU-Bedarf interessant, da die Preisattraktivität hier mit 9.7/10 im Cost Rating sehr hoch ist.

Wie souverän ist Hikube?

Der SEAL Score liegt bei 6.9/10 (69%). Die operative Souveränität wird mit 8/10 bewertet, gestützt durch den Schweizer Sitz und die lokale Betriebsführung. Die technologische Souveränität erreicht 9/10, was auf einen Open-Source-Stack und geringen Lock-in hindeutet.

Wie ist die Preisgestaltung bei Hikube?

Das allgemeine Cost Rating liegt bei 6.4/10. Besonders hervorzuheben ist die GPU-Preisattraktivität mit 9.7/10 und das Egress-Rating von 10.0/10. Die tatsächlichen Kosten sind jedoch stark von der spezifischen Workload-Konfiguration abhängig.

Wo ist Hikube besonders stark?

Die stärkste Kategorie ist die Hochverfügbarkeit mit einem Score von 10/10 (Ø andere: 6.7), ermöglicht durch das 3-AZ-Design. Ebenfalls stark ist die technologische Souveränität mit 9/10 (Ø andere: 7.4) sowie die operative Souveränität mit 8/10.

Welche Einschränkungen gibt es bei Hikube?

Das Netzwerk-Portfolio ist mit 4/10 (Ø andere: 7.8) unterdurchschnittlich, ebenso wie das Speicher-Portfolio mit 5/10 (Ø andere: 7.7). Strategische Möglichkeiten wie Big Data und AI sind mit 3/10 bzw. 4/10 begrenzt, und Collaboration Tools fehlen nahezu vollständig (1/10).

Wie ist die Verfügbarkeit und der Standort von Hikube?

Hikube betreibt drei Verfügbarkeitszonen in der Schweiz: Genf (Plan-les-Ouates), Gland und Luzern. Es gibt eine Region in einem Land (Schweiz) auf einem Kontinent (Europa). Die Rechenzentren sind als separate Gebäude im Colocation-Modell betrieben.

Kategorie-Bewertungen

KategorieScore (1–10)
Datensicherheit & Verschlüsselung6/10
Technologische Souveränität9/10
Operative Souveränität8/10
Strategische Möglichkeiten3/10
Preis6/10
Collaboration Tools1/10
Globale Reichweite1/10
Big Data3/10
AI4/10
Bare Metal1/10
Virtualisierung5/10
Containerisierung7/10
Datenbanken5/10
Hochverfügbarkeit10/10
Microsoft4/10
Linux8/10
Encryption4/10
Speicher5/10
Netzwerk4/10

Skala: 1–2 = kein/marginales Angebot, 3–4 = Basisangebot mit Lücken, 5–6 = solides Mittelfeld, 7–8 = starkes Angebot, 9–10 = marktführend. Letzte Überprüfung: 2026-07-16.

Souveränität

AspektBeleg
InterpretationSwiss 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 3
ResidencySwitzerland
Shared ResourcesCloud Instances
Shared ResourcesManaged Kubernetes (dedicated control plane per cluster)
Dedicated CloudHikube (on Prem) on Request
EncryptionVault as a Service (secrets management in the Swiss tenant)
Ownership & controlHidora 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)
Ownership & controlShareholders not public (auditor Fiduciaire Marc Gobet SA)
EU governance & oversightNo independent board or advisory body with veto/oversight rights (checked: about, imprint, security & compliance, GTC)
EU governance & oversightSingle legal entity Hidora SA, ordinary board of directors only (per commercial register)
Third-country access riskHidora SA, Switzerland (not EU) (ownership chain not publicly evidenced)
Third-country access riskProcessing only on documented instructions (GTC October 2026 Annex D clause 3; exception 'mandatory legal obligations' with prior notice where permitted)
Third-country access risk30 days' notice before a change of control, termination right (GTC clause 12.4)
Contracting entity & jurisdictionContracting party HIDORA SA, Petit-Lancy; Swiss law, Geneva courts (GTC October 2026 clause 21; CHE-286.910.173; Switzerland (not EU))
Contracting entity & jurisdictionSubprocessor register only towards clients, not published (Annex D clause 6, notification)
Transparency on authority requestsNo transparency report on government requests (checked: security & compliance, CLOUD Act guide (2026-06-10, upd. 2026-08-21), resources, blog)
Transparency on authority requestsOnly a general statement: 'Swiss mutual legal assistance exists.'
Data residency incl. backups/DROperated from Swiss DCs: Geneva (Plan-les-Ouates), Gland, Lucerne (Hikube service agreement October 2026, clause 3 and Annex A; Switzerland (EU adequacy decision))
Data residency incl. backups/DRNo transfer outside Switzerland without written consent ('except in security emergencies or legal obligations' (open-ended); sub-processor locations not published)
Metadata & support data residencyAncillary processing 'may involve subcontractors' (service agreement October 2026 clause 3: anti-DDoS, monitoring, support)
Metadata & support data residencyLocation only in the DPA or subprocessor register, not published (no commitment for telemetry/logs/billing)
AI services: processing & trainingNot applicable: no managed AI service (GPU as a Service only, 6 NVIDIA cards L4–H200 on VMs/node groups; 'no opaque ML PaaS')
AI services: processing & trainingCustomers run inference/fine-tuning themselves (no managed model/inference APIs, no AI assistant)
Dedicated / segregated environmentManaged Kubernetes control plane dedicated to your cluster (own API server, own etcd, 'shared with nobody'; workers in own tenant)
Dedicated / segregated environmentNo bare metal, no dedicated region (on-premises edition exists per Hidora, no public product page – not rated)
EU operations & supportSupport by Hidora SA engineers in Geneva (support page 2026-08-23; business days 08:00–18:00 CET, 24×7 infrastructure on-call)
EU operations & supportWebsite statement only (access logging and break-glass not documented)
Technical operator lock-outNo confidential computing, no attestation, no HYOK
Technical operator lock-outPrivileged operator access not described (security & compliance page: 'until a written model exists'; encryption 'available')
Disconnected / autonomous operationControl plane operated exclusively in Switzerland (guide 2026-07-15, upd. 2026-09-07: Geneva, Gland and Lucerne; Switzerland (not EU))
Disconnected / autonomous operationOn-premises edition per Hidora, public product page announced (until then no documented disconnected offering)
Hardware origin & manufacturingOnly the GPU vendor disclosed: NVIDIA (six cards L4 24G, L40S 48G, A100 80G, RTX 6000 Pro 96G, H100 80G, H200 141G)
Hardware origin & manufacturingServer vendors, manufacturing, chip dependencies not published (no supply-chain policy)
Critical software dependenciesPartially disclosed: Talos Linux, Cilium, Grafana, VictoriaMetrics (Managed Kubernetes page; VictoriaLogs, cert-manager)
Critical software dependenciesHypervisor, identity provider, DNS/PKI not addressed (non-EU dependencies not addressed)
Open-source share & patch authorityManaged OSS services: OpenBAO, Harbor/Trivy, Grafana, MariaDB (release notes Hikube v1.1.2 (19 Mar 2026); OpenBAO = open-source fork of HashiCorp Vault; RabbitMQ)
Open-source share & patch authorityKubernetes v1.30–v1.35; no OSS share, no patch statements
Portability & exitReversibility: 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))
Portability & exit'Fees may apply'; export formats and egress not named in the contract
IaC & automationPublic REST/JSON API with OpenAPI 2.0 specification (api.hikube.cloud: VMs, disks, S3 buckets, Kubernetes, VPC, databases, backups, GPU, pricing)
IaC & automationAPI 'preview (v1alpha1)', no commitment for critical automation (per the docs; account, projects, members, keys console-only)
IaC & automationNo official client, no Terraform provider (under consideration)
Key sovereignty (BYOK/HYOK, EU HSM)Vault as a Service in your Swiss tenant, operated by Hidora ('without US KMS or US Vault'; 'no self-operated HSM')
Key sovereignty (BYOK/HYOK, EU HSM)No BYOK/HYOK, FIPS/CC or custody protocol (no HashiCorp API compatibility claimed)
Certifications & scopeISO 27001 'certified by SQS' per the provider ('the PDF is not online'; attestation, scope annex, validity date on request only)
Certifications & scopeNo further own certifications listed (site certificates belong to the building operators Stack Infrastructure and EWL)
Public audit evidencePublic only: GTC, Hikube contract, privacy notice, status page
Public audit evidenceISO certificate, DPA, subprocessor list on request only (isolation description also on request; no pentest summary, no shared-responsibility matrix)
EU labels & schemesNo EUCS, Gaia-X, EU Cloud CoC, CISPE, SecNumCloud or Cloud III SEAL (no BSI C3A; Swiss provider (not EU))
EU labels & schemesOnly Swiss Label/Swiss Hosting badges, CNCF KCSP (logos; Certified Kubernetes)
Energy & CO₂ transparency'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))
Energy & CO₂ transparencyOperator figures, no own CO₂/water reporting
Climate commitmentsNo own climate targets (Hidora/Hikube not in the Climate Neutral Data Centre Pact public register)
Climate commitmentsColocation operator STACK EMEA listed since 21 Jan 2021 (2024 status: Self-Certified; EWL/RZ Stollen absent)

Alle Services von Hikube (60)

SEAL Framework

ServiceHikube
Sovereignty Score6.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 %)Founder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025
SOV-2 Legal & Jurisdictional (10 %)Swiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU
SOV-3 Data & AI (10 %)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 and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators
SOV-5 Supply Chain (20 %)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 %)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 %)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 %)100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates

Availability & Locations

ServiceHikube
Presence DACHSwitzerland
Presence EuropeSwitzerland Geneva (Plan-les-Ouates), Gland, Lucerne
Availability Zones3
Multi-AZ✓ verfügbar
Regions1
Countries1
Continents1

Compute

ServiceHikube
Shared InstanceCloud Instances s1 / u1 / m1, 1vCPU-64vCPU
GPU InstanceGPU Cloud NVIDIA L4, L40S, A100, RTX 6000 Pro, H100, H200
Windows ServerWindows Server licence (incl. 2025, per vCPU)

Hot Storage

ServiceHikube
Block StorageBlock Storage 3x Replicated NVMe, sync or async across 3 datacenters
AssetsSwiss S3 Object Storage (S3 API, WORM)

Cold Storage

ServiceHikube
VM BackupBackup as a Service
Volume BackupVelero (Kubernetes add-on)
Disaster Recovery3-datacenter replication by design (restart on the remaining sites)

Managed Databases

ServiceHikube
MySQLManaged MariaDB
PostGreManaged PostgreSQL (CloudNativePG)
Document-OrientedManaged MongoDB
Distributed Wide-ColumnManaged ClickHouse
CacheManaged Redis (Sentinel)
VectorManaged Qdrant

Network & Security

ServiceHikube
NetworkVPC & Subnets
Public IPPublic IPv4
Load BalancerManaged Ingress (ingress-nginx, Gateway API)
FirewallPer-VM firewall (allowed inbound ports on the public IP; SSH 22 default, HTTP/HTTPS optional)
Private ConnectivitySite-to-site VPN (on request)

Orchestration

ServiceHikube
Container RegistryRegistry as a Service
OrchestrationManaged Kubernetes

Virtualization

ServiceHikube
HypervisorNot disclosed (VM layer operated by Hikube; VMDK / QCOW2 / ISO import)
Instance as a ServiceCloud Instances

Management

ServiceHikube
Identity ManagementOrganizations & Projects (isolated projects with quotas, members and roles; API keys per project)
IaCHikube public API (REST/JSON, OpenAPI 2.0 spec)
IaCFluxCD
Command Linekubectl / Helm

Big Data

ServiceHikube
DashboardsGrafana (Monitoring Agents add-on, per cluster)
Data StreamingManaged Kafka
MessagingManaged RabbitMQ
MessagingManaged NATS
Big Data PlattformManaged ClickHouse (OLAP)
Log MonitoringMonitoring Agents add-on

AI & Machine Learning

ServiceHikube
Machine LearningGPU as a Service (dedicated NVIDIA GPUs on VMs or Kubernetes node groups)

Compliance & Certificates

ServiceHikube
ISO 27001\nInformation security management system✓ verfügbar

Cost Indication

ServiceHikube
Rating6.4/10
CPU vCPU/h6.2/10 0,0119212 €
GPU H100/h9.7/10 2,9785142 €
RAM GB/h3.0/10 0,0119212 €
Managed MySQL Ratio1/44.2/10 0,0744966 €
Block Storage GB/h | 3000 IOPS5.7/10 0,0002719 €
S3 Storage GB/h4.0/10 0,0000298 €
Kubernetes-Service-Premium Cluster/h8.5/10 0,0476848 €
Egress per GB10.0/10 0,0000000 €

Geprüfte Primärquellen

Direktvergleiche