Choosing a Managed PostgreSQL Provider for Production
Picking a managed PostgreSQL provider affects your data sovereignty, operational burden, disaster recovery posture, and total cost for years. This page compares six options available to Swiss organizations today: self-hosted, the three major hyperscalers, Aiven, and VSHN Managed PostgreSQL.
This comparison focuses on community PostgreSQL. If your project requires Oracle compatibility or EDB enterprise tools, see enterprisedb.ch.
Quick comparison
| Self-Hosted | Amazon RDS | Google Cloud SQL | Azure Database | Aiven | VSHN AppCat PostgreSQL | |
|---|---|---|---|---|---|---|
| Data location | Your choice | EU (Frankfurt, Zurich) | EU (Zurich) | EU | EU various | Your choice (Swiss cloud or on-premises) |
| Jurisdiction | Yours | US (CLOUD Act) | US (CLOUD Act) | US (CLOUD Act) | Finnish company, US infra | Swiss |
| Ops model | You manage | AWS managed | Google managed | Microsoft managed | Aiven managed | VSHN manages |
| SLA | None | 99.95% Multi-AZ | 99.95% with HA (none single-zone) | 99.99% zone-redundant | 99.99% | Up to 99.99% |
| Max DB size | Unlimited | 64 TiB | 64 TB | 64 TiB | 11 TB (largest plan) | 500 GiB |
| PostgreSQL versions | Any | 14–18 | 13–18 | 13–18 | 14–18 | 14–18 |
| Extensions | All | Limited | Limited | Limited | Community | Community |
| Superuser | Yes | rds_superuser role |
cloudsqlsuperuser role |
azure_pg_admin role |
No superuser account | Yes, in the connection secret |
| Logical replication | Yes | Set rds.logical_replication, static, needs a reboot |
Set the cloudsql.logical_decoding flag |
Set wal_level to logical |
Yes, via the preinstalled aiven_extras extension |
On by default, 32 slots |
| Custom parameters | All | Parameter groups | Database flags | Server parameters | Curated subset | pgSettings, 15 blocked |
| Open source | Yes | Proprietary platform | Proprietary platform | Proprietary platform | Uses PostgreSQL | Fully open source (CloudNativePG) |
| Vendor lock-in | None | High | High | High | Medium | None |
| Starting price | $0 + ops team | ~$135/month (db.t3.medium, Multi-AZ, Zurich) | ~$130/month (1 vCPU, 3.75 GB, regional HA, Zurich) | ~$380/month (2 vCores, zone-redundant HA, Switzerland North) | $180/month (Business plan) | CHF 80/month (single), CHF 480/month (HA with SLA) |
Cloud provider prices are on-demand USD list prices for the configuration and region shown, read from each vendor's price list on 2026-09-15. Storage, backups and data transfer come on top, apart from the storage included in an Aiven plan.
Self-Hosted PostgreSQL
Running PostgreSQL on your own VMs or Kubernetes cluster gives full control over configuration, location, and access.
Strengths: complete data sovereignty, no per-service fees, all extensions available, any PostgreSQL version.
Limitations: the operational burden is substantial. Production PostgreSQL requires 24/7 monitoring, backup automation with restore testing, HA setup (Patroni, repmgr, or CloudNativePG), security patching, and major version upgrade management. A dedicated PostgreSQL DBA is a full salary, and one person is not round-the-clock coverage. Smaller teams frequently defer upgrades and skip restore testing. Both create risk that surfaces only during incidents.
Fits when: your organization has a dedicated database team with PostgreSQL expertise and specific customization requirements that no managed service can meet.
Amazon RDS for PostgreSQL
Amazon RDS is the market leader in managed PostgreSQL. It handles provisioning, patching, backups, and failover within the AWS ecosystem.
Strengths: mature service with broad features (read replicas, Performance Insights, point-in-time recovery), Zurich region (eu-central-2) available since 2022, deep integration with AWS services.
Limitations: Amazon is a US company subject to the CLOUD Act. Even with a Zurich region, US authorities can compel data access without Swiss judicial process. RDS runs exclusively on AWS infrastructure. There is no deployment on Cloudscale, Exoscale, or your own data center. Deep AWS lock-in with IAM, VPC, and CloudWatch dependencies. Pricing for compute, storage, IOPS, and backups is billed separately, making costs hard to predict.
Fits when: your team is already committed to AWS and accepts US jurisdiction trade-offs.
See our PostgreSQL sovereignty assessment for a detailed jurisdictional comparison.
Google Cloud SQL for PostgreSQL
Cloud SQL is Google's managed relational database service. The Zurich region (europe-west6) puts compute and storage in Switzerland.
Strengths: Zurich region with low-latency access from Swiss infrastructure, automated backups and point-in-time recovery, competitive pricing for smaller instances.
Limitations: Google is subject to the CLOUD Act regardless of data location. Cloud SQL runs exclusively on Google infrastructure. GCP lock-in with networking, identity, and monitoring. Major version upgrades require downtime or manual migration. IOPS are tied to disk size, constraining performance tuning options.
Fits when: your team is invested in Google Cloud and needs a Zurich-hosted database.
See our PostgreSQL sovereignty assessment for a detailed jurisdictional comparison.
Azure Database for PostgreSQL
Azure Database is Microsoft's managed PostgreSQL offering, available as Flexible Server with zone-redundant high availability.
Strengths: zone-redundant HA with 99.99% SLA, EU regions available, automated backups and point-in-time recovery, integration with Azure IAM and networking.
Limitations: Microsoft is subject to the CLOUD Act. Azure lock-in for networking, monitoring, and access control.
Fits when: your team is already in the Azure ecosystem and needs managed PostgreSQL.
See our PostgreSQL sovereignty assessment for a detailed jurisdictional comparison.
Aiven for PostgreSQL
Aiven is a Finnish company offering managed databases across multiple clouds. They deploy PostgreSQL on AWS, GCP, or Azure in your chosen region.
Strengths: EU-headquartered company (Helsinki), multi-cloud deployment across AWS, GCP, and Azure, good developer experience with CLI tools and Terraform provider.
Limitations: Aiven runs on US hyperscalers even in EU regions. CLOUD Act exposure remains via the underlying infrastructure. No Swiss-owned infrastructure option. The 99.99% SLA covers the Startup, Business, and Premium tiers, not only the top one. No dedicated Swiss region; closest option is typically the Frankfurt or Zurich region of the underlying hyperscaler.
Fits when: you want a single managed database provider across multiple hyperscalers and EU headquarters matters more than Swiss hosting.
VSHN Managed PostgreSQL (AppCat)
VSHN operates PostgreSQL on your chosen infrastructure via AppCat, using the open-source CloudNativePG operator on Kubernetes.
Strengths:
- Swiss company, Swiss jurisdiction. VSHN is headquartered in Zurich. No CLOUD Act exposure through the operations layer.
- Infrastructure of your choice. Cloudscale, Exoscale, on-premises, or eight providers via Servala.
- Fully open source. CloudNativePG is a Linux Foundation project with no proprietary service layer.
- PostgreSQL versions 14–18, including the latest release. Versions are dropped when upstream drops them, so 13 went with its end-of-life in November 2025.
- Automated daily backups with six retained copies (configurable).
- Up to 99.99% SLA with service credits.
- ISO 27001 certified operations.
- Self-service provisioning via Kubernetes API or Servala.
Pricing:
| Plan | Single instance | Replicated (HA) |
|---|---|---|
| Baseline | CHF 80/month | CHF 160/month (2 replicas) |
| 99.99% - 24/7 | N/A | CHF 480/month (2 replicas) |
Those prices are for the database service. Compute, memory and storage are extra: VSHN buys them for you unless you would rather keep your own cloud subscription, in which case the provider invoices you for that part.
Fits when: Swiss jurisdiction is required, you want predictable pricing, or your team cannot sustain 24/7 database operations.
Logical replication, and what it costs to turn on
If you replicate out to a data warehouse, run change data capture, or sync with something like Debezium or PowerSync, this row decides the shortlist before price does.
On our service it is already on. wal_level is logical, because CloudNativePG sets it that way by default. The role in your connection secret is the postgres superuser, so pg_create_logical_replication_slot, CREATE PUBLICATION and the pgoutput plugin work with no further grants, no parameter change, no reboot and no support ticket. You get 32 replication slots.
CloudNativePG ships enableSuperuserAccess: false upstream, and an engineer who knows that is right to be suspicious of a bare checkmark. We override it to true. That is the whole of the difference, and you can see the role in the secret yourself on day one.
Three limits, none of which is in a footnote elsewhere:
- Slots survive a failover only on PostgreSQL 17 and newer, and not at all on a single instance. Plan for re-creating the subscription if you run one.
- A major version upgrade runs
pg_upgrade, which drops replication slots. This is PostgreSQL behavior, not ours, and it means an upgrade is a scheduled interruption for your consumer. - Our alerting does not watch slot state. An inactive slot retains write-ahead log indefinitely, because
max_slot_wal_keep_sizeis at the PostgreSQL default of-1, and it will eventually fill the disk. If you create a slot, monitor it. This is the one that costs money if nobody is watching.
What the others ask for. None of them is unable to do logical replication. What differs is the ceremony: Amazon RDS wants rds.logical_replication set to 1, which is a static parameter and therefore a reboot; Cloud SQL wants the cloudsql.logical_decoding flag; Azure wants wal_level set to logical. Aiven gives you no superuser account at all, and ships aiven_extras so you can publish and subscribe without one.
Custom parameters go through pgSettings on our service. Fifteen are blocked, and a blocked one is rejected when you apply it rather than being silently overwritten later, so you find out immediately and can ask.
Which option fits?
Choose self-hosted if you have dedicated DBA capacity and need full configuration control.
Choose Amazon RDS or Cloud SQL if you are already committed to that hyperscaler ecosystem and US jurisdiction is acceptable.
Choose Azure Database if your organization is in the Azure ecosystem and 99.99% zone-redundant SLA is required at Microsoft's price point.
Choose Aiven if you need a single managed database provider across AWS, GCP, and Azure without moving to a specialist operator.
Choose VSHN Managed PostgreSQL if your data must stay under Swiss jurisdiction, you need predictable CHF pricing, or your team wants to stop running PostgreSQL operations.
Next steps
Ready to compare your current setup with Swiss-managed PostgreSQL? Book a consultation. We will review your database requirements and recommend the right approach.