AWS vs Hikube — Direktvergleich

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

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

Management Summary (Stand 2026-10)

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: Stärken

AWS: Zu bedenken

Hikube: Stärken

Hikube: Zu bedenken

AWS wählen, wenn:

Hikube wählen, wenn:

Häufige Fragen: AWS vs Hikube

Was ist der Unterschied zwischen AWS und Hikube?

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.

Welcher Anbieter ist souveräner?

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.

Welcher Anbieter ist günstiger?

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.

Welcher Anbieter bietet bessere Netzwerk-Funktionen?

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.

Für welche Workloads ist Hikube besser geeignet?

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.

Management Summary

ServiceAWSHikube
Count of Services200+20+
Cost Rating5.4/106.4/10
Saving Plan72%–
Datacenter124 AZs (in 39 regions; an AZ is one or more data centers; AWS publishes no data-center count)3
Datacenter ModelOwn datacentersColocation
Zone SeparationSeparate buildingsSeparate buildings
Server ProductionCustom design–
Countries281
SEAL Score4.1/10 (41%)6.9/10 (69%)
USPMarket leader with the widest range of features and global reach3 AZ by design: every workload runs active-active across three Swiss datacenters. VM volumes and Kubernetes are replicated by the platform.
RecommendationRecommended for innovation drivers and international scalingRecommended for Swiss organisations and regulated mid-sized companies that want built-in HA resilience without designing it themselves.

Sovereign Cloud

ServiceAWSHikube
InterpretationSensitive data should be encrypted by BYOK. For stronger protection use AWS European CloudSwiss 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 1SEAL 3
ResidencyUSSwitzerland
Shared ResourcesAWS European Sovereign Cloud eusc-de-east-1 (Brandenburg), GA since 01/2026Cloud Instances
Dedicated ResourcesEC2 Dedicated Host–
Dedicated CloudAWS Outpost RackHikube (on Prem) on Request
EncryptionCloud HSMVault as a Service (secrets management in the Swiss tenant)
Ownership & controlUltimate 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 & oversightESC 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 riskCLOUD 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 & jurisdictionESCA 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 requestsAmazon 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/DRCustomer 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 residencyESC 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 & trainingAmazon 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 environmentAWS 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 & supportESC 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-outNitro 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 operationESC '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 & manufacturingNitro 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 dependenciesAWS-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 authorityOwn 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 & exitFree 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 & automationSDK 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 & scopeBSI 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 evidenceSOC 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 & schemesCISPE 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₂ transparencyPUE 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 commitmentsISO 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)

SEAL Framework

ServiceAWSHikube
Sovereignty Score4.1/10 (41%) US jurisdiction caps strategic, legal & supply-chain objectives6.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 parent (Amazon); European Sovereign Cloud GA since 01/2026 under dedicated German-law AWS entities, not independent of AmazonFounder-led Swiss company Hidora SA; ownership chain not publicly evidenced; small provider, platform launched in 2025
SOV-2 Legal & Jurisdictional (10 %)Subject to US CLOUD Act & FISA 702Swiss jurisdiction (nFADP), no US parent; EU adequacy decision for Switzerland covers transfers from the EU
SOV-3 Data & AI (10 %)Strong residency & BYOK controls; US access risk remainsData 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 %)European Sovereign Cloud region operated exclusively by EU residents (GA since 01/2026); standard regions on the global ops modelOperated and supported by Swiss-based engineers; buildings (power, cooling, physical access) are run by third-party site operators
SOV-5 Supply Chain (20 %)Proprietary global supply chain, custom US siliconColocation 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 %)Proprietary stack, high lock-in, limited reversibilityOpen-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 27001, broad audit portfolioISO 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 energy matched; net-zero 2040 pledge100% renewable power at all three sites, heat reuse in Geneva and Lucerne; no PUE published, ISO 14001/50001 are building certificates

Availability & Locations

ServiceAWSHikube
Presence DACHGermanySwitzerland
Presence EuropeGermany Frankfurt, Brandenburg (Sovereign Cloud)Switzerland Geneva (Plan-les-Ouates), Gland, Lucerne
Presence North AmericaUSA Virginia, Ohio, Oregon, California–
Presence South AmericaBrazil São Paulo–
Presence Asia-PacificJapan Tokyo, Osaka–
Presence Middle East & AfricaBahrain Manama–
Availability Zones1243
Multi-AZ✓ verfügbar✓ verfügbar
Regions391
Countries281
Continents61
Point of Presence750+–
Dedicated Backbone✓ verfügbar–
DDoS✓ verfügbar–

Compute

ServiceAWSHikube
Shared InstanceEC2 Elastic Compute 1vCPU-1920vCPUCloud Instances s1 / u1 / m1, 1vCPU-64vCPU
Dedicated InstanceEC2 Dedicated instance 1vCPU-896vCPU–
GPU InstanceEC2 GPU Instances G6e/G7/G7e (L40S, RTX PRO Blackwell), P5 (H100/H200), P6 (B200/B300, GB200)GPU Cloud NVIDIA L4, L40S, A100, RTX 6000 Pro, H100, H200
AI AcceleratorTrainium3 (Trn3 UltraServers) up to 144 Trainium3 chips (up to 362 FP8 PFLOPs) per UltraServer–
Windows ServerEC2 Windows Server InstancesWindows Server licence (incl. 2025, per vCPU)
ServerlessLambda–
ARM InstanceGraviton Graviton5 (M9g/C9g GA 06/2026)–
Confidential ComputingNitro Enclaves–
Virtual Private Server\nshared & low-budgetAmazon Lightsail–

Hot Storage

ServiceAWSHikube
Block StorageElastic Block StorageBlock Storage 3x Replicated NVMe, sync or async across 3 datacenters
AssetsSimple Storage Service(S3)Swiss S3 Object Storage (S3 API, WORM)
Managed NetAppFSx for NetApp ONTAP–
FileElastic File System–

Cold Storage

ServiceAWSHikube
VM BackupAMIBackup as a Service
Volume BackupEBS SnapshotsVelero (Kubernetes add-on)
ArchiveS3 - Glacier–
TapeS3 Glacier Deep Archive–
Disaster RecoveryElastic Disaster Recovery3-datacenter replication by design (restart on the remaining sites)

Managed Databases

ServiceAWSHikube
MySQLAuroraManaged MariaDB
PostGreAuroraManaged PostgreSQL (CloudNativePG)
MS SQLRDS for SQL Server–
OracleRDS for Oracle–
DB2RDS for Db2–
Document-OrientedDocumentDBManaged MongoDB
Distributed Wide-ColumnKeyspacesManaged ClickHouse
TSDBTimestream for InfluxDB–
CacheElastiCache Valkey, Redis OSS, MemcachedManaged Redis (Sentinel)
Search EngineOpenSearch–
Knowledge GraphNeptune–
VectorOpenSearch (Vector Engine)Managed Qdrant

Network & Security

ServiceAWSHikube
NetworkVirtual Private CloudVPC & Subnets
Public IPElastic IPPublic IPv4
GatewayAPI Gateways–
Load BalancerElastic Load BalancerManaged Ingress (ingress-nginx, Gateway API)
Public DNSRoute53–
Private DNSRoute53–
FirewallWAFPer-VM firewall (allowed inbound ports on the public IP; SSH 22 default, HTTP/HTTPS optional)
Private ConnectivityVirtual Private CloudSite-to-site VPN (on request)
Dedicated ConnectivityDirect Connect–
DDoS ProtectionShield–
CDNCloudfront–

Orchestration

ServiceAWSHikube
Container RegistryElastic Container RegistryRegistry as a Service
OrchestrationElastic Kubernetes Service(EKS)Managed Kubernetes

Virtualization

ServiceAWSHikube
HypervisorNitro System KVM-based, no direct accessNot disclosed (VM layer operated by Hikube; VMDK / QCOW2 / ISO import)
Instance as a ServiceEC2 InstancesCloud Instances
Managed Virtualization PlatformsVMware Cloud on AWS since 04/2024 sold only via Broadcom–
Bare Metal VirtualizationEC2 Instances .metal instance type–
Edge VirtualizationOutposts Rack–
Workload-specific VirtualizationAWS for SAP–

Management

ServiceAWSHikube
Identity ManagementIAMOrganizations & Projects (isolated projects with quotas, members and roles; API keys per project)
IaCCloudFormationHikube public API (REST/JSON, OpenAPI 2.0 spec)
Audit TrailCloudTrail–
Mail ServiceSES–
Command LineAWS CLIkubectl / Helm
MCP ServerAWS MCP Server managed, part of Agent Toolkit for AWS–
CO2 CalculatorAWS Sustainability Console builds on the Customer Carbon Footprint Tool–
CollaborationAWS Wickr (secure messaging/voice/video)–

Big Data

ServiceAWSHikube
DashboardsCloudWatchGrafana (Monitoring Agents add-on, per cluster)
Data StreamingKinesis Data StreamsManaged Kafka
MessagingMQManaged RabbitMQ
Business AnalyticsAWS Quick Sight formerly Amazon QuickSight–
Big Data ProcessingEMR–
Big Data PlattformGlueManaged ClickHouse (OLAP)
Log MonitoringCloudwatchMonitoring Agents add-on

AI & Machine Learning

ServiceAWSHikube
AssistantLex–
TranslationTranslate–
Audio AnalysisTranscribe–
Computer VisionRekognition–
NLPComprehend–
Image GenerationBedrock–
Machine LearningSageMakerGPU as a Service (dedicated NVIDIA GPUs on VMs or Kubernetes node groups)
AI RouterBedrock–
Document IntelligenceTextract–
Large Language ModelsBedrock Anthropic, OpenAI, Amazon Nova, Mistral, Meta, xAI, DeepSeek, Qwen and more–
EmbeddingsBedrock–
Serverless InferenceBedrock on-demand pay-per-token, per-model RPM/TPM quotas; OpenAI- & Anthropic-compatible APIs–
Batch InferenceBedrock Batch Inference −50 % vs. on-demand for select models; JSONL input/output via S3–
Dedicated InferenceProvisioned Throughput hourly per model unit; no commitment, 1- or 6-month terms–
Service TiersPriority tier 75 % premium over Standard pricing (select models)–
Fine-TuningBedrock Supervised Fine-Tuning Nova 2 Lite, Nova Pro/Lite/Micro, Llama 3.x, Claude 3 Haiku · US regions only–
GuardrailsBedrock Guardrails content & prompt-attack filters, denied topics, PII masking, grounding checks–
AI Data PolicyNo training, no provider access I/O not used to train Nova/Titan/third-party models, not shared with providers–
AI AgentsBedrock AgentCore Runtime serverless agent hosting, session isolation; any framework or model; MCP + A2A–
RAG & GroundingBedrock Managed Knowledge Base fully managed RAG: 7 connectors, managed embedding + reranking, agentic retrieval–
Prompt CachingBedrock Prompt Caching up to 90 % lower cost and up to 85 % lower latency for supported models–
Evaluation & ObservabilityBedrock Evaluations model + RAG evaluation: programmatic, human workers, LLM-as-a-judge–
Video & Music GenerationBedrock Luma Ray2 text/image-to-video clips via async API (StartAsyncInvoke); us-west-2 only–
Sovereign / On-Prem AIBedrock in European Sovereign Cloud eusc-de-east-1: Gemma 4 GA since 09/2026, in-Region only, zero operator access–

LLM Models

ServiceAWSHikube
Jamba 1.5 Large (AI21 Labs · open weights)✓ verfügbar · 256k Kontext (Legacy since 26 May 2026; EOL 26 Nov 2026)–
Qwen3-235B-A22B-Instruct-2507 (Alibaba Cloud · open weights)✓ verfügbar · 256k Kontext–
Qwen3-Coder-480B-A35B-Instruct (Alibaba Cloud · open weights)✓ verfügbar · 256k Kontext (Legacy since 30 Sep 2026; EOL 30 Mar 2027)–
Amazon Nova 2 Lite (Amazon · proprietary)✓ verfügbar · 1M Kontext–
Amazon Nova Lite (Amazon · proprietary)✓ verfügbar · 300k Kontext–
Amazon Nova Micro (Amazon · proprietary)✓ verfügbar · 128k Kontext–
Amazon Nova Pro (Amazon · proprietary)✓ verfügbar · 300k Kontext–
Claude Fable 5.1 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Haiku 4.5 (Anthropic · proprietary)✓ verfügbar · 200k Kontext–
Claude Haiku 5.5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Mythos 5.1 (Anthropic · proprietary)✓ verfügbar · 1M Kontext (Preview)–
Claude Opus 4.8 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Opus 5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Opus 5.5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Sonnet 4.6 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Sonnet 5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
Claude Sonnet 5.5 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–
DeepSeek-V3.2 (DeepSeek · open weights)✓ verfügbar · 164k Kontext–
Gemma 4 31B (Google · open weights)✓ verfügbar · 256k Kontext–
Llama 4 Maverick 17B 128E Instruct (Meta · open weights)✓ verfügbar · 1M Kontext (Legacy since 30 Sep 2026; EOL 30 Mar 2027)–
Llama 4 Scout 17B 16E Instruct (Meta · open weights)✓ verfügbar · 10M Kontext (Legacy since 30 Sep 2026; EOL 30 Mar 2027)–
MiniMax M2.5 (MiniMax · open weights)✓ verfügbar · 196k Kontext–
Devstral 2 (123B) (Mistral AI · open weights)✓ verfügbar · 256k Kontext (Legacy since 30 Sep 2026; EOL 30 Mar 2027)–
Mistral Large 3 (Mistral AI · open weights)✓ verfügbar · 256k Kontext–
Kimi K3 (Moonshot AI · open weights)✓ verfügbar · 1M Kontext–
Nemotron 3 Super 120B-A12B (NVIDIA · open weights)✓ verfügbar · 256k Kontext–
GPT-5.6 Luna (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-5.6 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-5.6 Terra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6 Astra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6 Luna (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6 Sol (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
GPT-6.1 Sol (OpenAI · proprietary)✓ verfügbar · 1M Kontext–
GPT-6.1 Terra (OpenAI · proprietary)✓ verfügbar · 1.1M Kontext–
gpt-oss-20b (OpenAI · open weights)✓ verfügbar · 128k Kontext–
gpt-oss-120b (OpenAI · open weights)✓ verfügbar · 128k Kontext–
Palmyra X5 (Writer · proprietary)✓ verfügbar · 128k Kontext (Legacy since 21 Sep 2026; EOL 21 Mar 2027)–
Grok 4.7 (xAI · proprietary)✓ verfügbar · 524k Kontext–
GLM-5.3 (Z.ai · open weights)✓ verfügbar · 1M Kontext–
Kimi K3.1 Pro (Moonshot AI · open weights)✓ verfügbar · 1M Kontext–
Claude Mythos 5.2 (Anthropic · proprietary)✓ verfügbar · 1M Kontext (Preview)–
Claude Fable 5.2 (Anthropic · proprietary)✓ verfügbar · 1M Kontext–

Embedding Models

ServiceAWSHikube
Nova Multimodal Embeddings (Amazon)✓ verfügbar (text, image, video, audio in one vector space; us-east-1 only)–
Titan Text Embeddings V2 (Amazon)✓ verfügbar (8k context, configurable dimensions; in-Region in six EU regions)–
Cohere Embed 3 (Cohere)✓ verfügbar (Embed English and Multilingual (100+ languages))–
Cohere Embed 4 (Cohere)✓ verfügbar (multimodal: text + image)–
Marengo Embed 3.0 (TwelveLabs)✓ verfügbar (video embeddings for search and retrieval; in-Region eu-west-1 (Ireland) + EU geo profile)–

Quantum Computing

ServiceAWSHikube
EmulatorBraket–
EngineBraket–

Compliance & Certificates

ServiceAWSHikube
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–

Cost Indication

ServiceAWSHikube
Rating5.4/106.4/10
CPU vCPU/h3.8/10 0,0356685 €6.2/10 0,0119212 €
GPU H100/h5.5/10 5,8480000 €9.7/10 2,9785142 €
RAM GB/h5.6/10 0,0041262 €3.0/10 0,0119212 €
VMware CPU/h-–
Managed MySQL Ratio1/43.4/10 0,0860000 €4.2/10 0,0744966 €
Block Storage GB/h | 3000 IOPS7.4/10 0,0001122 €5.7/10 0,0002719 €
S3 Storage GB/h4.1/10 0,0000289 €4.0/10 0,0000298 €
Archive Storage GB/h7.9/10 0,0000048 €–
Tape GB/h8.8/10 0,0000021 €–
Kubernetes-Service-Premium Cluster/h5.3/10 0,0860000 €8.5/10 0,0476848 €
Serverless-Request per 1 Mil Requests8.8/10 0,1700000 €–
Serverless-Compute GB-Sec5.9/10 0,0000142 €–
Generative AI-Token Input gpt-oss-120b per 1Mil tokens6.8/10 0,1720000 €–
Generative AI-Token Output gpt-oss-120b per 1Mil tokens3.0/10 0,6794000 €–
Egress per GB3.4/10 0,0774000 €10.0/10 0,0000000 €

Einzelprofile