Managed PostgreSQL
Managed PostgreSQL, operated in Switzerland.
Hikube managed PostgreSQL is the relational SQL engine in the Databases as a Service catalog, operated with CloudNativePG in Switzerland, without a US DBaaS.
- CloudNativePG
- Swiss S3 backups
- Private network
- ISO 27001
- 3 DC
- SLA 99.99%
For teams that already speak PostgreSQL and want operations in Switzerland: the same jurisdiction as compute, Kubernetes and backup. Other engines on the hub: the five managed database engines.
Capabilities
CloudNativePG
PostgreSQL operated with CloudNativePG. Not a proprietary dialect.
Swiss S3 backups
Optional, to object storage in the same tenant, not to a US bucket.
Private network
The database listens in the VPC. Kubernetes apps or VMs connect there.
In detail
For a line-of-business app or a Kubernetes stack that already speaks relational SQL. Teams leaving a US DBaaS (RDS, Cloud SQL) or self-operated PostgreSQL mostly want Swiss residency and an identifiable operator: Hidora SA, Geneva, Gland, Lucerne. It is the wrong product if you expect Aurora, a global proxy, or 15 SKU variants.
Operations: HA, updates, optional backups to Swiss S3. You keep the schema, clients (psql, drivers) and CI. Connection secrets go in Vault as a Service. API detail is in docs.hikube.cloud. Engineer support in French and English, from Geneva.
The path, in order. The exact screens and the API reference are in docs.hikube.cloud; what follows is the logic, which does not move.
- Create the instance from the console or the API, in the VPC where your applications already run
- Pick the size from the grid shared by all engines: it can be changed later, so do not oversize up front
- Put the credentials in Vault as a Service and have your pods read them from there: the secrets vault
- Connect with psql from a VM or pod in the same VPC: the endpoint is private and does not answer from the internet
- Bring existing data over with pg_dump and pg_restore: this is PostgreSQL, there is no intermediate format to cross
- Before cutting production over, restore a backup into a second instance and compare row counts
- Available versions and enabled extensions are not published here: ask before designing a schema that depends on one
Engines
Related products
Managed databasesPostgreSQL, MariaDB, Redis, MongoDB, ClickHouse: operated in Switzerland.- VPC & subnetsVMware VLANs to VPC and subnets, three Swiss DCs, no SDN fabric to repurchase.
Swiss S3S3 object storage in Switzerland: WORM, optional encryption, Swiss residency.- Vault as a ServiceSecrets and keys in Switzerland, for apps, CI and Kubernetes.
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.
Yes: PostgreSQL operated with CloudNativePG, not a proprietary dialect. The scope is not the full RDS catalog (Aurora, global proxy). Hub and other engines: the five managed database engines.
Ready to run on 100% Swiss infrastructure?
14-day trial, no credit card. GPUs included.