Postgres is the foundation under most of the managed offerings in this category, and the right answer when the question is "which database should I use." It's the rare piece of infrastructure where boring really does win: ACID guarantees, decades of optimizer work, a rich extension ecosystem (pgvector, PostGIS, Citus, TimescaleDB), and a release cadence that ships meaningful performance gains every September. If you're picking a database in 2026 without a strong reason to pick something else, the answer is Postgres.
- Boring works, decades of stability, predictable upgrades, no surprises
- Extension ecosystem covers vectors, geo, time-series, sharding
- All major managed providers (Supabase, Neon, RDS) run real Postgres
- Free, BSD-licensed, no vendor lock-in
- Postgres 18 brings async I/O, improved query parallelism, OAuth auth
- Self-managed ops is real work, backups, replication, tuning, upgrades
- Default config is conservative; production tuning required
- Horizontal scaling needs Citus or app-layer sharding
- Vacuum behavior surprises teams new to MVCC
- No built-in connection pooling, needs PgBouncer or pgpool
PostgreSQL is the open-source relational database that has quietly become the default choice for new applications. Originally derived from the POSTGRES project at Berkeley in the mid-1980s, it now underpins most of the managed database services on the market, Supabase, Neon, RDS Postgres, Cloud SQL, and dozens more all ship real Postgres rather than a wire-compatible reimplementation.
Where it fits
Postgres is the default OLTP database for new web applications in 2026, full stop. It handles transactional workloads, ad-hoc analytics, vector search, geospatial queries, and time-series data without bolt-on infrastructure, thanks to a mature extension ecosystem. Teams reach past it only when the use case is genuinely document-shaped (MongoDB), wide-column (Cassandra), edge-replicated (SQLite/Turso), or reactive-by-default (Convex).
The practical question for most teams is not “Postgres or X” but “which Postgres”, self-managed, managed via a cloud provider, or the modern serverless flavors (Supabase, Neon) that wrap Postgres in a developer-friendly workspace.
Cost to adopt
Free, BSD-licensed, self-hostable on any cloud or on-prem. The real cost is operational: backups, point-in-time recovery, replication setup, version upgrades, monitoring, and vacuum tuning. For most teams shipping a web app, the math favors a managed Postgres provider, pay $20-$50/month and skip the ops.
Self-hosting becomes economic at scale (mid-six-figure annual DB spend), when compliance forces it, or when latency-sensitive workloads need the database next to the app on dedicated metal. Citus (sharding) and Patroni (HA) are the standard self-hosted add-ons; both are open source.
How it compares
Supabase, Managed Postgres with auth, storage, realtime, and edge functions in one workspace. Pick when you want a complete backend rather than just a database.
Neon, Serverless Postgres with separated compute and storage, instant branching, and scale-to-zero. Pick for elastic workloads and per-PR preview databases.
MongoDB, Document database with a flexible schema and an extensive aggregation framework. Pick when your data model is genuinely document-shaped.
What changed recently
Postgres 18 shipped in late 2025 with async I/O for sequential scans (meaningful gains on cloud storage), improved query parallelism, native UUIDv7 generation, and built-in OAuth authentication. The 18.4 patch landed May 14 2026 with security fixes and 60+ bug fixes across all supported versions. Postgres 14 reaches end-of-life on November 12 2026, teams still on 14 should plan upgrades. The extension ecosystem continues to expand: pgvector remains the standard for AI workloads, and DuckDB-style analytics extensions are an active area of development.
Sources
- PostgreSQL News, postgresql.org, May 2026
- PostgreSQL 18 Release Notes, postgresql.org
- PostgreSQL Versioning Policy, postgresql.org
- pgvector, github.com/pgvector/pgvector
- beat · 2026-07-06
PostgreSQL's JDBC driver patches a silent channel-binding downgrade that hits the hardened setups first
PostgreSQL's official JDBC driver shipped a July 6 fix for CVE-2026-54291, a silent SCRAM channel-binding downgrade that only bites connections requiring channel binding over modern Ed25519 or post-quantum certificates. The hardened setups are the exposed ones.
- launch · 2026-06-16
PostgreSQL 19 Beta lands SQL/PGQ graph queries and concurrent table repacking
PostgreSQL 19 Beta 1 shipped on 2026-06-04 with SQL/PGQ property graph queries and a new REPACK ... CONCURRENTLY command, the largest categorical additions to vanilla Postgres since pgvector. GA is targeted at September or October 2026.
- launch · 2026-06-15
Neon ships neon.ts, bringing TypeScript infrastructure-as-code to a Postgres branching platform
Neon launched neon.ts on 2026-06-15, a TypeScript file that declares Postgres, Auth, and Data API services with per-branch compute settings. Applied via neonctl config plan and apply, the file gives Neon a Terraform-shaped workflow without the Terraform.
- launch · 2026-06-11
Microsoft open-sources pg_durable, putting Temporal-style durable workflows inside Postgres
Microsoft's new pg_durable extension brings durable workflow execution into PostgreSQL itself, with checkpoints, retries, and replay handled by a background worker rather than an external orchestrator. Open source under the PostgreSQL License, preinstalled in Azure HorizonDB.
- beat · 2026-06-05
Supabase closes $500M Series F at $10.5B as AI agents take over Postgres provisioning
Supabase raised $500M at a $10.5B post-money valuation on June 4, 2026, led by GIC. The company says 60% of new databases on the platform are now provisioned by AI coding tools, with Claude Code the largest single driver and Multigres open-sourced alongside.