Cloud PostgreSQL service map
Understand mainstream managed and developer platforms through verified capability boundaries
Managed community PostgreSQL
| Service | Verified capabilities | Validate during selection |
|---|---|---|
| Amazon RDS for PostgreSQL | Automated backup/PITR, Multi-AZ, read replicas, VPC, and TLS | No host access; parameters, privileged capabilities, and extensions come from platform allowlists |
| Cloud SQL for PostgreSQL | Managed backup, HA/failover, encryption, private/public networking, replicas, and maintenance | Maintenance or configuration may restart instances; check regional, extension, connection, and AI-feature availability |
| Azure Database for PostgreSQL Flexible Server | Same-zone/zone-redundant HA, PITR, TLS, private networking, managed maintenance, optional built-in PgBouncer | Automated backup retention defaults to 7 days and extends to 35; built-in PgBouncer uses port 6432, so verify pooling mode |
| Alibaba Cloud RDS for PostgreSQL | Basic, High-availability, and Cluster editions; automated/manual backup, read-only instances, and proxy options | HA standbys are not directly readable; sync mode, proxy routing, and backup type vary by architecture |
| TencentDB for PostgreSQL | Managed installation, storage, HA, backup, major/minor upgrades, and read-only groups | Official guidance says one read-only instance has no HA/SLA; validate node count, routing, and consistency for production read groups |
Cloud providers do not necessarily ship the same engine or extension on the day the community does. Split “supports PostgreSQL 17/18” into three checks: can a new instance use it, can an existing instance upgrade to it, and does the required extension support it? For the two AWS paths — managed community RDS and the Aurora engine — see AWS RDS for PostgreSQL and Aurora.
PostgreSQL-compatible enhanced engines
| Service | Architecture | Difference to accept |
|---|---|---|
| Aurora PostgreSQL-Compatible | Customized PostgreSQL-compatible engine and distributed storage, managed primarily as clusters | Aurora has its own release cadence; extensions come from a support matrix and do not automatically upgrade with the community extension |
| AlloyDB for PostgreSQL | Decoupled compute/storage, cross-zone HA, optional columnar engine, vector and model integrations | Not community-binary-equivalent; validate extensions, parameters, migration tools, analytical paths, and regional capability |
“PostgreSQL-compatible” describes a migration starting point, not a test result. Exercise schema migration, critical queries, transactional concurrency, drivers, extensions, and recovery. Per-engine landing pages: AWS RDS for PostgreSQL and Aurora, AlloyDB for PostgreSQL, and Alibaba Cloud PolarDB for PostgreSQL.
Developer data platforms
| Service | Strength | Often-missed production concern |
|---|---|---|
| Neon | Separated compute/storage, autoscaling, scale-to-zero, database branching, and pooled connections | Cold starts, changing compute size, branch data governance, and the different purposes of pooled versus direct connections |
| Supabase | A full PostgreSQL database per project plus Auth, Storage, Realtime, APIs, and Supavisor | Design RLS correctly before browser-facing data APIs; verify backup/PITR plan, connection budget, and coupling to platform components |
For no-cost development environments, use the free PostgreSQL cloud database guide, checked on 2026-08-02. Supabase, Neon, Nhost, and Prisma Postgres have different platform structures and should not be ranked by free storage alone. Per-platform landing pages: Neon and Supabase.
A backup is not proven recovery
Validate recovery granularity, retention, cross-region copies, key dependencies, exportability, and measured restore time. Managed physical backups on platforms such as Azure cannot be exported directly; an exit path usually needs pg_dump, logical replication, or a migration service.
For AI workloads
When choosing cloud PG for RAG or agent metadata, check:
- the exact pgvector version, HNSW/IVFFlat support, and upgrade cadence;
- connection limits and pooling for short-lived functions and agents;
- memory, temporary storage, WAL, and replica lag during vector-index builds;
- real recall after tenant/ACL filtering, not an unfiltered benchmark;
- whether the embedding model, vector data, and database share the required residency boundary;
- whether text, metadata, and embeddings can be exported without pipeline lock-in.
Provider model endpoints, automated embedding, or AI assistants can remove glue code, but add privilege, region, model-lifecycle, and cost dimensions. They do not replace database RLS, least-privilege roles, or retrieval evaluation.
If a candidate only supports the PostgreSQL protocol or reuses its query layer, continue with PostgreSQL lineage and compatible databases.
Last updated on
Free PostgreSQL cloud database guide
Compare free PostgreSQL limits, sleep, backup, and production boundaries across Supabase, Neon, Aiven, Nhost, Prisma Postgres, Koyeb, and Render
AWS RDS for PostgreSQL and Aurora
Choose between Amazon RDS for PostgreSQL and Aurora PostgreSQL-Compatible by compatibility boundary, failover behavior, connection limits, and cost model — checked 2026-08.