PostgreSQL

PostgreSQL is infrastructure, not an application. In a go-to-market context it turns up in two roles: as the database a self-hosted GTM tool (an open-source CRM, a data pipeline, a lead store) is built on, and as the destination a revenue team's data lands in when they want to own it rather than rent it. Nothing about it is opinionated toward sales - it is a general-purpose relational engine with a long release cadence and a well-documented support lifecycle, which is exactly why it ends up under so much else.

• Full SQL object-relational database engine
• Extensive official documentation, versioned per release and downloadable as PDF
• A published versioning policy with dated end-of-support commitments per major version
• Public beta programme - PostgreSQL 19 Beta 2 was released 2026-07-16 at check time
• Documentation translated into Chinese, French, Japanese and Russian
• A published feature matrix comparing capabilities across versions
• Open governance, with the project's governance model published on the site

Anyone who needs a durable relational store they control - from a solo builder running a self-hosted CRM to an enterprise data platform. There is no licence gate on scale, so fit is determined by whether you have someone to operate it.

PostgreSQL is a database, not a tool a revenue team can use directly: there is no UI, no CRM, no workflow layer, and nothing here that a salesperson would open. The costs it moves rather than removes are operational - the project publishes a versioning policy with hard end-of-support dates (PostgreSQL 14 stops receiving fixes on 12 November 2026), so running it means owning an upgrade schedule, and there is no vendor to escalate to when it breaks. Teams that want the data model without the operations should be looking at a managed Postgres provider rather than at the project itself.

Setup assessment: custom

There is no single setup path - installing a local instance, deploying a self-managed production cluster with replication and backups, and pointing an application at a managed provider are three different projects with three different timescales. The project publishes installation guidance in the official documentation rather than a quickstart with an expected duration.

Prerequisites

• A machine or managed service to run it on
• Someone to own backups, upgrades and the version-support calendar
• A supported major version - check the versioning policy; PostgreSQL 14 loses fixes on 2026-11-12

• The project's source repository, mailing lists and official social accounts
• Published pricing was not available in the reviewed source set; confirm current commercial terms with the vendor.