Block storage
NVMe volumes in Switzerland, geo-redundant, sync or async.
Hikube block storage is network NVMe attached to instances and Kubernetes PVCs. Always geo-redundant: synchronous (real time) or asynchronous (improved performance) replication across Geneva, Gland and Lucerne. Optional encryption. Not a non-replicated local volume.
- NVMe
- 3-DC geo-redundancy
- Optional encryption
- ISO 27001
- 3 DC
- SLA 99.99%
For volumes attached to instances and Kubernetes PVCs. Geo-redundant 3-DC replication, synchronous or asynchronous. Encryption optional. Prices on the pricing page. S3 object storage is a different product.
Capabilities
NVMe
High-performance block storage, attached to VMs and PVCs.
3-DC geo-redundancy
Synchronous (real time) or asynchronous (improved performance) replication across Geneva, Gland and Lucerne. No local block volume.
Optional encryption
Encrypted and unencrypted SKUs, at the same replication mode.
Block storage SKUs (CHF / GB / month)
| SKU | CHF/GB/mo |
|---|---|
| Encrypted Block Storage 3xReplicated | 0.22 |
| Block Storage 3xReplicated | 0.18 |
| Encrypted Block Storage 3xReplicated async | 0.22 |
| Block Storage 3xReplicated async | 0.18 |
In detail
No. The flavor publishes vCPU and RAM. Volumes bill per GB/month according to the SKU (3x replicated sync or async, encrypted or not). Stopping the instance stops compute, not the volume while it stays provisioned. Pricing page: the pricing page.
Both modes write to the three sites. They differ on when your application gets its acknowledgement, and everything follows from that.
- Synchronous: a write is acknowledged only once it exists on the copies. Nothing is lost if a site fails, and every write pays the latency between sites
- Asynchronous: the write is acknowledged immediately and copied after. More throughput, and a loss window equal to the copy lag
- How to choose: measure your application’s write latency on your real profile, not on a generic figure. A transactional database and an analytics warehouse do not trade the same way
- How to verify: the mode is a property of the volume, visible on its page in the console. Check it before going live, not after the first incident
- What neither does: protect you from a deletion, which replicates too, or from ransomware encryption. That is backup: managed backup
Volume replication keeps several live copies of your blocks: it answers a disk or a site failing. Restarting the VM is another thing: the volume survives, the machine comes back, and the time that restart takes is not covered by replication. Application availability is elsewhere again: it depends on how many instances of your application run and how traffic fails over, not on storage. And backup answers what none of the three covers: human error and corruption, because those replicate. The volume bills per gigabyte per month, CHF 0.18 per GB, read from the catalogue, attaches to a VM or serves as a Kubernetes PVC, and three-site replication is inside that price: there is no high-availability surcharge to add. Prices: the pricing page.
No. 3-site replication is the 3xReplicated SKU (sync or async), not an AWS-style HA line stacked on top. Every block volume is geo-redundant; there is no non-replicated local SKU. Sync and async do not share the same RPO.
Block attaches to VMs and PVCs. S3 is for objects, Velero backups, datasets. Both stay in Switzerland, with Hidora SA. S3: S3 object storage.
Frequently asked questions
No. Hikube is a sovereign cloud: compute, storage, backups and metadata stay on three independent Swiss datacenters (Geneva, Gland, Lucerne). There is no replication to the EU or the United States.
The operator is Hidora SA, a Swiss company in Lancy (Geneva), with no US parent. Compute, storage, backups and metadata stay in Geneva, Gland and Lucerne. That is not the same legal basis as AWS, Azure or GCP. We are not your counsel: GDPR for EU data in Switzerland relies in particular on adequacy.
Through the Hikube API and the console. Terraform and Cluster API integration in preparation. kubectl, Helm and S3 clients stay. Docs: docs.hikube.cloud.
No. The public catalogue is NVMe, geo-redundant replication (3-DC sync or async) and encryption. No IOPS grid. Page: block storage.
Ready to run on 100% Swiss infrastructure?
14-day trial, no credit card. GPUs included.