Managed Postgres services

The PaaS, Distributions and Docker Images sections of awesome-postgres — twenty-four entries, as catalogued on 2026-08-20, at the catalog's word (T3).

Scope note. Managed-database pricing and hosting is ../cloud-wiki's subject; the engine as a subject is this spoke's. This page exists for the part that is a database-architecture matter — what a managed platform does to the extension model — and records the roster so awesome-postgres' coverage is complete. Pricing figures below are the catalog's own and unchecked.

Hyperscaler and general managed offerings

Amazon RDS for PostgreSQL · Azure Database for PostgreSQL · Google Cloud SQL for PostgreSQL · Aiven PostgreSQL (across AWS/Azure/DigitalOcean/GCP/UpCloud) · DigitalOcean Managed Databases (from $15/mo) · OVHcloud Cloud Databases · Render Managed PostgreSQL (from $7/mo) · Scaleway Managed Database (EU-hosted, from €10/mo) · ScaleGrid PostgreSQL DBaaS (HA with superuser control) · Heroku Postgres · Database Labs (from $20/mo) · Crunchy Bridge · Thalassa Cloud DBaaS (multi-AZ, Netherlands)

The newer shapes

Supabase (managed Postgres with read replicas and a GUI) · Neon (serverless with branching) · Nile (multi-tenant serverless) · PlanetScale for Postgres · Vela (backend-as-a-service for AI apps)

Two of these matter to pages the spoke already holds. PlanetScale for Postgres is the vendor this wiki pages as a MySQL sharding house (planetscale, vitess, and the Neki work) now selling Postgres — a fact the catalog records in one line and the planetscale page should carry. Neon's branching is the same idea the CLI section's pgsh implements locally and turso sells at the embedded end; copy-on-write database branches are becoming a category, and nothing in this corpus reads a primary source on how they work.

Distributions and images

Postgres.app (macOS) · Pigsty (battery-included distribution with observability, and the maintainer of the "400+ extensions" catalogue cited by postgresql-extensions) · postgres (the official Docker image) · citusdata/citus (official citus images) · paradedb/paradedb (ParadeDB with pg_search) · mdillon/postgis (PostGIS 2.3 on Postgres 9 — an image for a nine-year-old major version, listed without comment, and a good illustration of the catalog's dating problem)

The architectural point this roster makes

Eighteen managed services, each deciding which extensions may load. postgresql-extensions establishes that Postgres grows by extension and that loading one is a privileged act needing shared_preload_libraries and a restart. Put those together and the open ecosystem meets a closed per-vendor allowlist at the moment of deployment — which is why pgmq ships a SQL-only install path "if you are running someplace that does not natively support the PGMQ Extension", and why pg-stat-statements, a contrib module shipped with the server, is nonetheless a thing you may not be permitted to enable.

That is the tension recorded in synthesis.md, and this page is the half of the evidence that lives outside the engine.

Related

postgresql-extensions · pgmq · pg-stat-statements · planetscale · turso · citus · awesome-postgres · operational-databases