- All of the services compared run PostgreSQL 18; Aurora shipped it about seven months after RDS for PostgreSQL did.
- High availability differs: RDS, Cloud SQL and Azure use a standby in another zone; Neon spreads storage across zones and restarts compute instead.
- pgvector is available on every service here, but built-in connection pooling has conditions on Cloud SQL (Enterprise Plus only) and Azure (not on Burstable).
- For a small always-on database, Azure's Burstable tier had the lowest list price in our worked example; Neon is cheaper only when the database is idle much of the time.
- Choose the provider your application already runs on unless a feature such as branching, scale to zero or a bundled backend changes the decision.
What managed PostgreSQL includes
With managed PostgreSQL the provider installs and patches the engine and operating system, takes automated backups with point-in-time restore, monitors the server and, if you pay for it, fails over to a standby. You still design the schema, tune queries and indexes, choose instance sizes and decide on major version upgrades. That division is the same on every service here; what differs is how each one implements high availability, how quickly it adopts new PostgreSQL releases, and how it charges.
The services fall into two groups. Hyperscaler services (Amazon RDS for PostgreSQL, Amazon Aurora PostgreSQL, Google Cloud SQL for PostgreSQL, Azure Database for PostgreSQL flexible server) are instance-based and sit inside the cloud's networking and identity. Developer platforms (Neon, Supabase, DigitalOcean) trade some of that integration for simpler pricing and features such as branching or a bundled backend.
Managed Postgres services at a glance
| Service | Newest major version | High availability | Built-in pooling | pgvector |
|---|---|---|---|---|
| Amazon RDS for PostgreSQL | PostgreSQL 18 (RDS release 14 November 2025) | Multi-AZ with one standby, or a cluster with two readable standbys | RDS Proxy (separate service) | Yes (0.8.2 listed) |
| Amazon Aurora PostgreSQL | PostgreSQL 18 (Aurora release 11 June 2026) | Multi-AZ with up to 15 Aurora replicas | RDS Proxy (separate service) | Yes |
| Google Cloud SQL for PostgreSQL | PostgreSQL 18 (default version) | Regional instance with a standby in a second zone | Managed Connection Pooling, Enterprise Plus edition only | Yes (0.8.5 on PostgreSQL 13 and later) |
| Azure Database for PostgreSQL flexible server | PostgreSQL 18 | Zone-redundant or same-zone standby (zone-redundant not on Burstable) | Built-in PgBouncer on General Purpose and Memory Optimized tiers | Yes |
| Neon | PostgreSQL 14 to 18 | Storage replicated across zones; compute restarted on failure, no idle standby | PgBouncer, up to 10,000 client connections | Yes |
| Supabase | Current PostgreSQL (per project) | Read replicas; daily backups, PITR as an add-on | Shared pooler | Yes |
| DigitalOcean Managed PostgreSQL | Per cluster | Standby nodes with automatic failover | Connection pools | Check the supported extensions list |
Version lag: how fast new PostgreSQL releases arrive
PostgreSQL 18 was first released by the PostgreSQL project on 25 September 2025, and each major version is supported for five years. Managed services take time to certify a new major. AWS lists 14 November 2025 as the RDS for PostgreSQL release date for version 18, while Aurora PostgreSQL 18 arrived on 11 June 2026. Google Cloud SQL lists PostgreSQL 18 as its default version, and Azure's supported-versions page lists 18.6 as the current minor release. Neon supports the five latest majors, 14 to 18, and runs only the latest minor of each.
Two practical points follow. If you need a new PostgreSQL feature on day one, managed services will not give it to you; plan for months. And older majors are retired on a schedule: RDS and Aurora charge for Extended Support after standard support ends, and Azure marks versions 11 to 13 as Extended Support. Build major version upgrades into your plans.
High availability, pooling and pgvector
High availability. RDS offers a Multi-AZ deployment with one standby that does not serve reads, or a Multi-AZ DB cluster with two standbys that can serve read traffic. Cloud SQL's HA configuration is a regional instance with a primary and a standby in two zones, kept in sync by synchronous replication. Azure deploys the standby in a different zone by default in most regions, with a same-zone option; zone-redundant HA is not available on the Burstable tier. Neon takes a different approach: it does not run an idle standby, and recovers a failed compute by restarting it, which its documentation says takes a few seconds to a few minutes.
Connection pooling. Neon includes PgBouncer for up to 10,000 client connections. Azure offers built-in PgBouncer, but only on General Purpose and Memory Optimized compute. Cloud SQL's Managed Connection Pooling requires an Enterprise Plus edition instance. On AWS, pooling is RDS Proxy, a separate service that also keeps connections open across a failover.
Extensions and pgvector. Every service compared here supports pgvector for embeddings and similarity search, though versions differ (RDS lists 0.8.2, Cloud SQL 0.8.5). Each provider has its own allow-list, so check the exact extensions you use, such as PostGIS or TimescaleDB, before migrating.
For deeper two-way comparisons, see Aurora PostgreSQL vs RDS for PostgreSQL, Cloud SQL vs AlloyDB and Neon vs AWS RDS.
How to choose a managed Postgres database
- Your app already runs on AWS, Azure or Google Cloud: use that cloud's service (RDS or Aurora, Azure flexible server, Cloud SQL) so networking, identity and billing stay in one place.
- You want the cheapest always-on small database: compare burstable or shared-core tiers (Azure Burstable, Cloud SQL shared-core, DigitalOcean single node), remembering that shared-core Cloud SQL machines are not covered by its SLA.
- Your databases are idle much of the time, or you want a database per branch: Neon.
- You want auth, storage and APIs with the database: Supabase.
- You need very high read scale or fast failover on AWS: Aurora.
DigitalOcean deserves a note for 2026: from 15 October 2026 for new accounts, and 30 November 2026 for all accounts, new Standard Edition PostgreSQL clusters cannot use plans above 4 GiB of RAM or add standby or read-only nodes. If you need standby nodes there, read DigitalOcean's plan-change notice before choosing an edition.
Pricing
Prices from the provider's official pricing pages, checked 8 October 2026, region Azure: East US (pricing page default); Cloud SQL: Iowa (us-central1); Aurora: US East (N. Virginia); Neon and Supabase publish one rate, in USD, excluding tax. List prices only; discounts, commitments and your actual usage change the bill.
The examples price one small, always-on workload on each service: about 2 GB of memory, 20 GB of SSD storage, single zone, running 730 hours a month. The compute is not identical (burstable, shared-core and autoscaling compute behave differently under load), so read these as list-price estimates for comparable sizes, not like-for-like benchmarks. Backups beyond any included amount, network transfer and tax are excluded.
Amazon RDS for PostgreSQL is not priced here: its instance price table on the AWS pricing page is interactive and we could not capture a verifiable figure in our check. DigitalOcean's documentation lists single node clusters from 15.00 USD per month (1 GiB RAM) and highly available clusters from 30.00 USD per month per node, with additional storage at 0.115 USD per GiB per month.
Azure Database for PostgreSQL, Burstable B1ms
- 1 vCore, 2 GiB, pay as you go, East US
- 20 GiB Premium SSD; backup storage up to 100% of provisioned storage has no extra charge
| Item | Basis | Estimated per month |
|---|---|---|
| Compute | B1ms list price per month | 12.41 USD |
| Storage | 20 GiB x 0.115 USD | 2.30 USD |
| Estimated total | about 14.71 USD per month |
Google Cloud SQL for PostgreSQL, db-g1-small (shared core)
- Shared vCPU, 1.7 GB RAM, Iowa (us-central1); not covered by the Cloud SQL SLA
- 20 GiB SSD
| Item | Basis | Estimated per month |
|---|---|---|
| Compute | 730 hours x 0.035 USD | 25.55 USD |
| Storage | 20 GiB x 730 hours x 0.000232877 USD | 3.40 USD |
| Estimated total | about 28.95 USD per month |
Supabase Pro with Small compute
- 2 GB RAM shared compute, one project
- 20 GB disk (8 GB included on Pro); includes Supabase Auth, Storage and API quotas
| Item | Basis | Estimated per month |
|---|---|---|
| Pro plan | Monthly fee | 25.00 USD |
| Compute | 730 hours x 0.0206 USD = 15.04 USD, minus 10 USD credit | 5.04 USD |
| Extra disk | 12 GB x 0.125 USD | 1.50 USD |
| Estimated total | about 31.54 USD per month |
Neon Launch, 0.5 CU always on
- 0.5 CU (2 GB RAM) with scale to zero disabled
- 20 GB storage
| Item | Basis | Estimated per month |
|---|---|---|
| Compute | 0.5 CU x 730 hours = 365 CU-hours x 0.106 USD | 38.69 USD |
| Storage | 20 GB x 0.35 USD | 7.00 USD |
| Estimated total | about 45.69 USD per month |
Aurora PostgreSQL serverless, 1 ACU constant (compute only)
- 1 ACU (about 2 GiB) all month, Aurora Standard, US East (N. Virginia)
- Aurora storage and I/O excluded
| Item | Basis | Estimated per month |
|---|---|---|
| Compute | 1 ACU x 730 hours x 0.12 USD | 87.60 USD |
| Estimated total | about 87.60 USD per month plus storage and I/O |
Worked examples are estimates calculated from the list prices above; they are not quotes or measured bills.
Frequently asked questions
What is the cheapest managed Postgres?
For a small database that runs all the time, burstable or shared-core tiers are the cheapest in list price; in our worked example Azure's B1ms came lowest. For a database that is idle most of the day, Neon's usage billing can cost less. Free plans from Neon, Supabase and Aiven cost nothing within their limits.
What is Postgres as a service?
Another name for managed PostgreSQL: the provider runs the PostgreSQL server for you, including patching, backups and failover, and you connect with normal PostgreSQL clients.
Is AWS managed Postgres RDS or Aurora?
Both. RDS for PostgreSQL runs community PostgreSQL on DB instances; Aurora PostgreSQL is a PostgreSQL-compatible engine with up to 15 Aurora replicas and a serverless option. Aurora has adopted new major versions later than RDS: PostgreSQL 18 arrived about seven months after it did on RDS.
Which managed PostgreSQL supports pgvector?
All the services compared here: RDS, Aurora, Cloud SQL, Azure flexible server, Neon and Supabase. Versions differ, so check the provider's extension list if you need a specific pgvector feature.
Does DigitalOcean offer managed Postgres?
Yes. DigitalOcean Managed PostgreSQL offers single node and high availability clusters with daily backups and seven days of point-in-time restore. Note the October and November 2026 plan changes for Standard Edition clusters described above.
Sources
- PostgreSQL versioning policy
- RDS for PostgreSQL release calendar
- Aurora PostgreSQL release calendar
- RDS for PostgreSQL extension versions
- Amazon RDS User Guide: Multi-AZ deployments
- Amazon RDS User Guide: RDS Proxy
- Amazon Aurora pricing
- Cloud SQL for PostgreSQL: database versions
- Cloud SQL for PostgreSQL: high availability
- Cloud SQL for PostgreSQL: Managed Connection Pooling
- Cloud SQL for PostgreSQL: extensions
- Cloud SQL pricing
- Azure Database for PostgreSQL: supported versions
- Azure Database for PostgreSQL: high availability
- Azure Database for PostgreSQL: PgBouncer
- Azure Database for PostgreSQL: extensions
- Azure Database for PostgreSQL pricing
- Neon docs: Postgres version policy
- Neon docs: High availability
- Neon docs: Connection pooling
- Neon pricing
- Supabase pricing
- Supabase docs: Compute and disk
- DigitalOcean docs: PostgreSQL pricing
- DigitalOcean docs: PostgreSQL features
Checked 8 October 2026.
How we research cloud database guides: our editorial method. CodeWithSQL earns nothing from the providers mentioned.