Managed databases
PostgreSQL, MariaDB, Redis, MongoDB, ClickHouse: operated in Switzerland.
Hikube managed databases are database services whose operations (HA, updates, optional backups to Swiss S3) are handled for you, without exposing data to a US DBaaS.
- Useful engines, not 200 SKUs
- Swiss S3 backups
- Private network
- ISO 27001
- 3 DC
- SLA 99.99%
Engines: PostgreSQL, MariaDB, Redis, MongoDB, ClickHouse. Backups to Hikube Object Storage. Private access via VPC.
Capabilities
Useful engines, not 200 SKUs
The scope covers SQL, cache, MongoDB document and OLAP.
Swiss S3 backups
Optional, to object storage in the same tenant, not to a US bucket.
Private network
Databases listen in the VPC. Kubernetes apps or VMs connect there.
Engines
Engines
| Service | Role |
|---|---|
| PostgreSQL | Relational SQL (CloudNativePG) |
| MariaDB | Widely deployed SQL |
| Redis | Cache / queues (Sentinel) |
| MongoDB | Document |
| ClickHouse | OLAP / analytics |
In detail
PostgreSQL, MariaDB, Redis, MongoDB and ClickHouse. One page per engine: managed PostgreSQL, managed MariaDB, managed Redis, managed MongoDB, managed ClickHouse. Kafka is billed as a database instance on the pricing page; the product page is Kafka streaming. Published sizes: nano (4 CHF/month) to 2xlarge (160 CHF/month). Not Cosmos, not Aurora Serverless v2, not 15 warehouse variants. If your app speaks SQL or Redis, you stay on the standard.
The criterion is not which one is best, it is what your application already speaks. Rewriting an application costs more than any difference between engines.
- Transactions, joins and constraints: PostgreSQL, managed PostgreSQL
- An estate already written in MySQL-family SQL: MariaDB, managed MariaDB
- Cache, sessions and queues, with a dataset that fits in memory: Redis, managed Redis
- Documents whose shape varies from one record to the next: MongoDB, managed MongoDB
- Analytics: aggregates over large volumes, batch writes rather than single-row, ClickHouse, managed ClickHouse
- Event streams rather than a database: Kafka, billed as a database instance, product page Kafka streaming
The same grid serves all five engines: 7 sizes, from nano (CHF 4 per month) to 2xlarge (CHF 160 per month), which tops out at 8 vCPU and 8 GB of RAM. That is a selection criterion, not a billing detail: past it the answer is not a bigger SKU, it is a database you operate yourself on cloud instances, with block storage to match. The memory ceiling bites hardest on Redis, whose dataset lives in RAM. Sizes and prices: the pricing page.
Backups are optional and go to object storage in the same Swiss tenant, never to a US bucket: S3 object storage. What follows holds for all five engines.
- Migration in and out uses the engine’s standard tooling: no proprietary format to cross
- A backup is not a restore: test the restore before going live, with a stopwatch
- Point-in-time recovery (PITR) is not advertised on these pages: if your RPO requires it, have it confirmed before you commit
- Available engine versions and enabled extensions are not published here: the console and an engineer are authoritative, a Hidora engineer
- Connection secrets go into Vault as a Service, not into a configuration file: the secrets vault
By default, no. Access is through the VPC. A public expose is an exception to justify (and firewall), not the handbook default.
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. Managed MongoDB in Switzerland, not Atlas. Page: managed MongoDB.
Yes. Hub: the five managed database engines. PostgreSQL (CloudNativePG): managed PostgreSQL. MariaDB: managed MariaDB. Redis (Sentinel): managed Redis. MongoDB: managed MongoDB. ClickHouse (OLAP): managed ClickHouse.
Ready to run on 100% Swiss infrastructure?
14-day trial, no credit card. GPUs included.