PostgreSQL Enterprise Support: Who Supports PostgreSQL and How It Is Priced

The short answer

PostgreSQL is built by the PostgreSQL Global Development Group, a community project that does not sell support. Enterprise support comes from companies: EDB, Crunchy Data and Percona sell it for PostgreSQL you run yourself, the cloud providers include it in their managed services, and OSSeva supports self-managed PostgreSQL, including versions past community end of life. They price it in different ways. EDB meters its cloud service by vCPU, Crunchy Data bundles support into product subscriptions, Percona quotes each contract, the cloud providers charge for instances and extended support, and OSSeva prices per cluster. The right choice depends on where your databases run, which versions they are on, and whether you want a vendor distribution or community PostgreSQL.

Who supports PostgreSQL?

The PostgreSQL project itself offers community support: documentation, mailing lists and IRC. Its support page says commercial support "is also available from one of the many companies providing professional services to the PostgreSQL community", and it keeps a directory of those companies by region. Companies add themselves to that list through a form, so treat it as a directory rather than a shortlist.

The PostgreSQL Licence allows use "without fee", so support is the only thing you pay for. The project supports each major version for five years. PostgreSQL 14 gets its final community release on 12 November 2026, and after that the community publishes no more fixes for it. That date is when support contracts start to differ most.

PostgreSQL support companies compared

EDB

EDB's plans run from Open Source Support, which covers community PostgreSQL and projects such as CloudNativePG, through Enterprise Postgres and Enterprise Postgres Plus, to analytics, distributed high availability and the full Postgres AI platform. Support comes at three levels: Basic, 10x5 for development and test; Production, 24x7; and Premium, 24x7 with aggressive service objectives.

On versions, EDB's compatibility page lists standard support for PostgreSQL 14 to 1 December 2026, 15 to 28 November 2027 and 16 to 9 November 2028, and nothing below 14. Its Cloud Service forces a major upgrade six months after a version's community end of life unless a customer has bought Extended Life Support, which EDB sells through its sales team without published terms.

EDB is the better fit when you want its Oracle-compatible Postgres for PL/SQL-heavy applications, its distributed high-availability product, or one vendor for both software and support. Our EDB alternatives post and EDB comparison cover the details.

Crunchy Data

Crunchy Data sells Crunchy Postgres for self-managed servers, Crunchy Postgres for Kubernetes based on its Postgres Operator, and Crunchy Bridge, a managed service on AWS, Azure and Google Cloud. Support is included with its product subscriptions. In June 2025 Crunchy Data announced it was joining Snowflake, which has since launched Snowflake Postgres as a fully managed service. If you are signing a multi-year contract for self-managed Crunchy Postgres, ask how Snowflake's plans affect the products you depend on.

Crunchy Data is a good fit for teams that want a supported Kubernetes operator from the same vendor that supports the database.

Percona

Percona sells Expert Support, ExpertOps and consulting for PostgreSQL in any environment, and ships Percona Distribution for PostgreSQL. It supports MySQL, MongoDB, MariaDB and Valkey too, which suits teams that want one database desk across several engines. Its distribution follows the community end-of-life dates, and its lifecycle policy says end-of-life products get no new builds or packages. Our Percona alternatives post and Percona comparison cover it in depth.

The cloud providers

Amazon RDS and Aurora, Azure Database for PostgreSQL and Cloud SQL run PostgreSQL for you and patch it inside their platforms. When a major version passes its end of standard support, they sell extended support. On RDS, Extended Support adds fixes for critical and high CVEs and critical bugs for up to three years, charged from the day after standard support ends and including Multi-AZ standbys; after three years RDS upgrades the database automatically. RDS for PostgreSQL 14 has standard support to 28 February 2027.

A managed service is the simplest answer if you are happy for the provider to run the database. It does not cover PostgreSQL on your own servers, and help with your workload comes through a separate cloud support plan. AWS, for example, charges for its support plans as the greater of a minimum monthly fee or a share of your monthly AWS charges. Our RDS Extended Support comparison and RDS Extended Support cost guide go further.

Community PostgreSQL or a vendor distribution

Before you pick a support vendor, decide what you want to run. Several vendors ship their own PostgreSQL builds. EDB sells Enterprise Postgres (Oracle Compatible), formerly EDB Postgres Advanced Server, which adds Oracle-style PL/SQL, packages and tools. Percona ships Percona Distribution for PostgreSQL, and Crunchy Data ships Crunchy Postgres. Each is built around PostgreSQL, but the further a distribution adds its own features, the more your applications depend on that vendor.

Community PostgreSQL keeps every option open. Any vendor that supports community PostgreSQL can take over support without a change to your binaries or data, and you can switch again later on the same terms. A vendor distribution makes sense when you need what it adds, such as Oracle compatibility for code you cannot convert. Otherwise, community PostgreSQL with a support contract gives you the same database with more freedom at renewal time.

How PostgreSQL enterprise support is priced

Vendors do not publish comparable price lists, but the models are public and they decide how the bill moves:

• Metered by vCPU. EDB's Cloud Service charges for the vCPUs provisioned, by the hour. Bills rise as instances grow.
• Bundled with a product subscription. Crunchy Data includes support with its subscriptions; Crunchy Bridge is pay-as-you-go.
• Quoted per contract. Percona and EDB's self-managed plans are quoted by sales. Ask what unit the quote counts.
• Instance charges plus extended support. Cloud providers bill instance hours and storage, then add extended support charges for each enrolled instance past the standard date, plus a separate support plan.
• Per cluster. OSSeva prices each PostgreSQL cluster, including its replicas, so adding a replica does not reprice the contract.

To compare like for like, list your clusters, nodes, vCPUs and versions, ask each vendor to quote against that list, and model next year's growth. The database support cost calculator does this with your own numbers.

What enterprise support should include

• Response commitments in writing, with the severity definitions that trigger them.
• A version list, including what happens on the day each version reaches community end of life.
• Fix delivery: patched builds, or advice only. Ask how a critical CVE reaches a server on a version the community no longer supports.
• Coverage of the pieces around Postgres: Patroni or repmgr, PgBouncer, backup tools and the extensions you run.
• Audit evidence: signed builds, SBOMs and CVE remediation records your auditors will accept.
• Where it runs: whether the contract covers bare metal, VMs, Kubernetes and every cloud account you use.

Which provider fits which team

• EDB if you want Oracle compatibility, its distributed high-availability product, or EDB's own platform.
• Crunchy Data if you want a supported Kubernetes operator from the database vendor, or the managed Crunchy Bridge.
• Percona if PostgreSQL is one of several databases and you want one consultative desk, on current versions.
• A cloud provider if you want the database run for you and accept its version calendar.
• OSSeva if you run community PostgreSQL yourself, need versions past end of life patched, or want the rest of the stack on the same contract.

Where OSSeva fits

OSSeva for PostgreSQL supports community PostgreSQL wherever you run it. OSSeva Patch backports security and data-corruption fixes into 11, 12 and 13, and into 14 from 12 November 2026, as signed DEB and RPM packages, tarballs and container images. A patched build installs like a minor release on the same data directory, under Patroni or repmgr. OSSeva Assure adds major-version upgrade planning to 17 or 18, a performance and vacuum review and a compliance attestation package. OSSeva Operate adds 24/7 replication and failover monitoring and a 15-minute P1 response. There is no migration: OSSeva takes over support of the binaries you run, with MySQL, MariaDB, Redis, Valkey, Kafka and RabbitMQ under the same contract. Pricing is per cluster; book a discovery call for a quote. See switching PostgreSQL support without a migration, PostgreSQL end-of-life support providers and PostgreSQL end-of-life support.

Frequently asked questions

Who supports PostgreSQL?

The PostgreSQL Global Development Group develops PostgreSQL and offers community support through mailing lists and documentation. It does not sell support. Commercial support comes from companies such as EDB, Crunchy Data, Percona and OSSeva, and from cloud providers for their managed services.

Is there an official PostgreSQL enterprise support vendor?

No. No company owns PostgreSQL. The project lists commercial support companies on postgresql.org, and companies add themselves to that list. Every vendor's support is its own product.

How much does PostgreSQL enterprise support cost?

It depends on the vendor's pricing model and your estate. EDB's cloud service is metered by vCPU, Crunchy Data bundles support into subscriptions, Percona quotes each contract, cloud providers charge for instances and extended support, and OSSeva prices per cluster. Model your own estate in the support cost calculator before comparing quotes.

Is PostgreSQL free for enterprise use?

Yes. The PostgreSQL Licence permits use, copying, modification and distribution without a fee. You pay only for the support, hosting or tooling you choose.

What PostgreSQL support services do companies offer?

Typically a 24x7 support desk with response commitments, consulting for architecture and performance, managed operations, upgrade and migration help, and, from a few vendors, patched builds for versions past community end of life.

Who supports PostgreSQL 14 after 12 November 2026?

The community stops on that date. EDB lists standard support for 14 to 1 December 2026. RDS keeps 14 in standard support to 28 February 2027 and then sells Extended Support. OSSeva ships patched 14 builds for self-managed servers from 12 November 2026.

Can we change PostgreSQL support vendors without migrating?

Yes, if you run community PostgreSQL. The binaries and data stay where they are; only the support contract changes. If you run a vendor distribution such as EDB Postgres Advanced Server, a change of vendor usually means moving to community PostgreSQL first.