Compare
Hikube vs AWS: Swiss cloud, no US parent
Hikube vs AWS compares Swiss IaaS (3 DCs, Hidora SA) with Amazon Web Services. A Zurich region stays under the CLOUD Act. Hikube takes the regulated core: VMs, Kubernetes, data, backups. AWS wins on the global catalogue.
- ISO 27001
- 3 DC
- SLA 99.99%
Hikube vs AWS is a Swiss enterprise cloud comparison, not a feature-count contest. AWS is a US company. Even a Zurich or eu-central region stays under the CLOUD Act. Hikube is Swiss IaaS operated by Hidora SA (Geneva): compute, storage, backups and metadata stay on three independent datacenters in Geneva, Gland and Lucerne. Swiss law on that compute. Published SLA 99.99%, ISO 27001 (SQS), engineer support in French and English. AWS wins on catalog breadth, Marketplace and a global footprint. Hikube wins when the constraint is legal and geographic: data that never leaves Switzerland, native 3-site replication (block sync or async, not the same RPO), an identifiable Swiss operator, IN/OUT traffic not billed. Many teams keep AWS for non-sovereign work and move the regulated core (VMs, EKS-like Kubernetes, GPU, line-of-business S3, backup, vault, VPC) to Hikube. Microsoft 365, if it is in the estate, stays at Microsoft: that hybrid model is detailed on /compare/azure. AWS lock-in sits mainly in IAM, CloudFormation and AWS Terraform, proprietary PaaS (Lambda, DynamoDB, Aurora Serverless), egress costs when leaving, and Marketplace. Hikube is Swiss IaaS: API and console today, VMDK import; Terraform and Cluster API integration in preparation. IN/OUT traffic is not billed: leaving Hikube is not egress-taxed the way leaving AWS is. We do not claim the 200-product AWS catalogue. kubectl, Helm and S3 clients stay. GPUs are in the 14-day trial. Windows Server is a licensed image (10 CHF/vCPU/month). No vs-Exoscale page.
| Workload | Where to put it |
|---|---|
| AWS Marketplace, global SaaS | Often AWS (catalogue, global footprint) |
| IaaS, Kubernetes, data, backups | Hikube (Hidora SA, 3 Swiss DCs) |
| Microsoft 365 | Stays at Microsoft (see /compare/azure) |
| Non-sensitive global SaaS | Cost / latency decision |
| Capabilities | Hikube | AWS |
|---|---|---|
| Model | Regulated core here; Marketplace / non-sovereign often AWS | AWS stack, including Zurich region |
| CLOUD Act | Hidora SA, Swiss company with no US parent | Applies (US group), including Zurich region |
| Residency | Hidora SA, Geneva, Gland, Lucerne. Compute, storage, backups and metadata stay in Switzerland. No US parent. | US group. A Zurich region fixes latency, not the operator or the CLOUD Act. |
| 3-site replication | Native, sync or async (geo-redundant, not the same RPO) | You design it (AZ/region) |
| Egress | IN/OUT traffic not billed | Egress billed to leave |
| Lock-in | Swiss IaaS, API and console, VMDK import; Terraform and Cluster API coming. IN/OUT traffic not billed. | IAM, CloudFormation / AWS Terraform, proprietary PaaS, egress to leave, Marketplace |
| Control plane | Hikube API and console (Terraform coming) | AWS API / Console / IaC |
| Kubernetes | Managed KCSP, workers auto-spread, 3 DCs | EKS + AWS ecosystem |
| Windows Server | Licensed image, 10 CHF/vCPU/month | Images and licenses in the AWS ecosystem |
| Support | Engineers in Geneva, FR and EN | Global support organisation |
How to read this table. The criteria are the ones that come up in Swiss tenders, not a coverage of both catalogues: AWS publishes more than two hundred services, Hikube around ten, and pretending to compare them line by line would be dishonest. The AWS columns describe the service’s public behaviour, the provider’s documentation and price list, and were reviewed on 8 September 2026; check them on the date of your decision, they move. Two rows do not compare the same thing and you should know it: “Support” sets a desk of engineers in Geneva against a tiered global organisation, which is neither better nor worse but different; “Kubernetes” sets a managed service against a managed service surrounded by an ecosystem Hikube does not have. The legal reasoning sits elsewhere: the CLOUD Act guide.
Frequently asked questions
No. Many keep Marketplace, global SaaS, or an AWS account for non-sovereign work. Hikube takes the workloads where jurisdiction and data residency matter: VMs, Kubernetes, data, backups. Microsoft 365, if present, stays at Microsoft.
For latency, often yes. For the CLOUD Act, no: AWS remains a US group. Hikube changes the compute operator (Hidora SA, three Swiss DCs), not only the region.
No. We migrate VMs, EKS-like Kubernetes, line-of-business S3, common databases (PostgreSQL, MariaDB, Redis, MongoDB, ClickHouse; not FerretDB, no separate MySQL SKU) and backups. No 1:1 twin of AWS PaaS.
On the AWS side: IAM, CloudFormation / AWS Terraform, proprietary PaaS (Lambda, DynamoDB, Aurora Serverless), egress costs to leave AWS, and Marketplace. On the Hikube side: Swiss IaaS, API and console control, VMDK import. Terraform and Cluster API integration in preparation. IN/OUT traffic is not billed: leaving Hikube is not egress-taxed the way leaving AWS is. No switching-cost figure is published: it depends on your estate.
On Hikube: Geneva, Gland and Lucerne, operator Hidora SA, no US parent. On AWS, including a Zurich region: the group remains American. A Switzerland region is not a Swiss cloud.
No. IN/OUT traffic is not billed, as published. AWS bills egress to leave. This is not an SLA credit: it is the Hikube tariff. Not to be confused with an assisted restitution at the end of a contract, which is a service and may be billed: terms in the general terms.
No. Public comparisons cover AWS, Azure and VMware. No vs-Exoscale page.
Yes: IaaS operated by Hidora SA on three Swiss DCs (Geneva, Gland, Lucerne), 99.99% SLA, ISO 27001, FR/EN support. Not shared web hosting. GPUs are in the 14-day trial. Windows Server is a licensed image on instances.
Ready to run on 100% Swiss infrastructure?
14-day trial, no credit card. GPUs included.