Skip to content

Backup as a Service

Managed backups in Switzerland, VMware DR.

Hikube Backup as a Service is a managed backup service for instances, volumes and related workloads. Copies stay in Switzerland and support DR (including VMware exit) plus nFADP audits. Hikube provides the copy; the application restore runbook stays yours.

  • Copies in Switzerland
  • VMware DR
  • Recovery objectives defined case by case
ISO 27001
3 DC
SLA 99.99%

Essential for VMware exit (replacing Veeam/on-prem once VMs are imported) and for finance (restore evidence). Works with Object Storage and Vault. We do not publish an RPO. Geo-redundant block (sync or async) is not the same product: not the same RPO. Guide: backup, vault and compliance.

Copies in Switzerland

No CLOUD Act backup target by default.

VMware DR

Backup and restore go in the 10 to 20 VM pilot, not on cutover day.

Recovery objectives defined case by case

Retention and tests are framed with an engineer. The runbook stays yours.

Velero vs platform

Velero is an optional Kubernetes addon. Backup as a Service targets instances and volumes.

nFADP framework

Copies in-country for the Swiss frame, under Swiss law.

S3, Vault, Terraform

Works with object storage and Vault. Terraform integration in preparation: today API and console.

In detail

We replace the function (copy, retention, restore) in the Hikube cloud model, once VMs are imported (VMDK / QCOW2 / ISO). We do not clone every Veeam plugin. Highly specific application jobs are a workshop. S3 object storage remains available if you keep a tool you operate. The 10 to 20 VM pilot must test a restore, not only a green job. Path: the VMware exit.

You, with scheduled tests. Hikube provides the service and can assist. FINMA/DORA files expect evidence, not a green job screenshot. We do not publish an RPO or an SLA credit. Geo-redundant block (sync in real time, or async, improved performance) is another product: block storage.

A backup never restored is not a backup, it is an intention. The discipline below holds whatever the tool, and it is what an auditor looks at, not a screenshot of a green job.

  • Restore into a separate target, never over the source: a failed restore must not destroy what is left
  • Time it: the real restore duration is the only figure that tells you whether your recovery objective holds
  • Check the content, not the status: count rows, open a file, start the service, a green job is not evidence
  • Date and file the result: that record is what a FINMA or nFADP file asks for, not the backup policy
  • Repeat it after every architecture change, not once at go-live

The model fits in one sentence: you choose the frequency, the retention period and the destination S3 bucket, Hikube’s or your own, and you pay for the storage, nothing else. There is no backup licence and no per-machine fee: at CHF 0.02 per GB per month on Hikube S3, the bill is the volume you decide to keep, which makes a retention period directly readable in francs. Two things are not published and are framed with an engineer: the exact list of objects covered and excluded for your estate, and any recovery objective : we publish neither RPO nor RTO, and an objective read here would be wrong for half the readers. What the page can state: if the destination is a Hikube bucket, copies stay in the Swiss tenant; testing the restore stays your responsibility; and Backup as a Service is neither block replication nor a bucket left on its own, see the next section.

Hidora SA operates the platform copy, the three DCs and FR/EN support. You keep the application runbook, frequency, written retention, tests and the pilot RPO/RTO alignment. Kubernetes: Velero (optional addon) is another lever, for the cluster. Terraform integration in preparation.

VMware exit: AD, files, IIS, line-of-business Linux after import. Finance: restore evidence in the Swiss tenant. Healthcare nFADP: copies in-country, not HDS. A US bucket for copies breaks the file. Vault page: the secrets vault.

Backup as a Service is the managed copy for DR and audits. Block storage is always geo-redundant, sync (real time) or async (improved performance): not the same RPO, not this product. S3 object storage (optional WORM) is a bucket, not a VM restore runbook. Guide: backup, vault and compliance.

No. nFADP / nLPD frame. Hikube is not an HDS host and is not HDS-certified. Healthcare copies stay in Geneva, Gland and Lucerne if you stay on this product. A US KMS or bucket breaks the file. Healthcare page: healthcare.

Frequently asked questions

Yes. Hikube is Swiss cloud IaaS (VMs, managed Kubernetes, GPU, S3, backup, vault) operated by Hidora SA on three datacenters: Geneva, Gland, Lucerne. Published SLA 99.99%, ISO 27001, engineer support in French and English. It is not shared web hosting. GPUs are in the 14-day trial. Windows Server is a licensed image on instances.

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.

None. Retention and restore are framed with an engineer. Block storage sync and async do not share the same RPO. The runbook stays yours.

Yes, the copy brick once VMs are imported. The 10 to 20 VM pilot must test a restore. Not on day one without a runbook.

No. nFADP frame. Hikube is not an HDS host. Healthcare page: healthcare.

Through the Hikube API and the console. Terraform and Cluster API integration in preparation. kubectl, Helm and S3 clients stay. Docs: docs.hikube.cloud.

Ready to run on 100% Swiss infrastructure?

14-day trial, no credit card. GPUs included.