Support That Starts With an Engineer
When your database is down you don't need a ticket queue, you need a Postgres expert who already knows your environment. Command Prompt has provided PostgreSQL support longer than anyone in North America — we supported Postgres95 before the postgresql.org project existed.
We deliver Tier 4 support. Your ticket is triaged and assigned directly to a senior Postgres engineer — one handoff, not a climb through three levels of escalation where you re-explain your architecture at each rung. Our staff is distributed across the U.S. and globally, so 24/7 PostgreSQL support means genuine follow-the-sun coverage, not an on-call rotation bolted onto business hours.
mini-cta here:
Tell us about your environment → · Call +1.503.667.4564 · sales@commandprompt.com
Why Enterprises Choose Us Over the Big Postgres Vendors
We'll still be here. 26 years in business, profitable for 24 of them, zero debt, no venture capital, employee majority owned. No acquisition, no pivot, no sunset notice on your support contract three years in.
Your ticket gets routed, not escalated. Triage identifies the right specialist and assigns it to them. One handoff to a senior Postgres engineer — not a ladder where each rung learns your architecture from scratch.
Our pricing doesn't punish growth. No per-instance, per-socket, or per-database-size charges. Add nodes, grow your data, split your workload — without re-opening your contract.
We publish our terms. Billed in 15-minute increments, time actually spent. Compare that against any competitor's pricing page.
We support the version you can't upgrade off. Extended Life Support reaching back to PostgreSQL 9.6, so an end-of-life version doesn't become a forced migration.
Any Platform, Any Deployment
Wherever your Postgres runs, the support boundary doesn't move. We provide Postgres support for:
- Open Source PostgreSQL
- EnterpriseDB Postgres Advanced Server
- AWS RDS for PostgreSQL
- AWS Aurora for PostgreSQL
- Azure Database for PostgreSQL
- Google Cloud SQL for PostgreSQL
- Google AlloyDB
- PgEdge Distributed Postgres
On-premise, cloud, or hybrid. If you're on a managed platform, your provider handles the infrastructure and hands the database back to you — that gap is where most production incidents actually live, and it's where we work.
No Per-Instance, Per-Socket, or Per-Database Pricing
We do not charge per instance, per socket, or per database size. Support is priced enterprise-wide. Scale your footprint without re-opening your support contract.
Three Ways to Engage Us
Coverage spans the full lifecycle — development and proof-of-concept, QA and test, deployment, and production. Most clients begin On-Demand and move to an SLA or PSLA addendum as their reliance on Postgres grows.
On-Demand
Flexibility when you need it, with no annual commitment.
- 24x7x365 availability
- Billed in 15-minute increments — we only bill time actually spent
- After-hours, holiday, and emergency rates apply
- Time and materials, billed monthly
- Option to prepay for a "bucket" of hours
SLA
For enterprises that want Postgres experts in their portfolio without engaging day to day — closest to standard break/fix commercial support.
- Annual option only
- Fixed rate, enterprise-wide
- Fixed rate 24x7x365 coverage
- Priority SLA response
Proactive SLA (PSLA)
"An extension of your team." Everything in the SLA, plus committed proactive hours.
- 24x7x365 support, monthly or annual options
- 4 hours of professional services and support included each month
- Prioritized SLA response
- Optional Proactive Monitoring available as an add-on
Coverage spans the full lifecycle — development and proof-of-concept, QA and test, deployment, and production. Most clients begin On-Demand and move to an SLA or PSLA addendum as their reliance on Postgres grows.
Not sure which fits? Start On-Demand — no annual commitment, no minimum. Most clients move to an SLA once they've seen how we work. Start a conversation →
Who You'll Work With
Command Prompt was founded in 1997 by Joshua D. Drake ("JD"), founder of United States PostgreSQL and Postgres Conference, and President of the International Committee of the PostgreSQL China Association. Our engineers cover Postgres and Linux administration, SQL engineering, automation, and architecture — and team retention means the same people stay on your account year over year.
Beyond the Database
Production systems are never just Postgres. We also support Long Term Release Linux (Rocky, RHEL, Ubuntu LTS), Ansible and Salt automation, Python and Django, Ceph and LXD architecture, and identity services including MFA and single sign-on.
Running an End-of-Life Postgres Version?
Community support ends; your obligations don't. PgLTS is our productized Extended Life Support — no forced upgrades, on your timeline. Neither Percona nor EDB offers extended support reaching back to 9.6.
Frequently Asked Questions
Which companies offer Postgres support?
Several vendors offer commercial PostgreSQL support, including Command Prompt, EDB, Percona, and Cybertec. Command Prompt is the longest-operating provider in North America — supporting Postgres since before postgresql.org existed — and the only one in the space that is profitable, debt-free, employee-owned, and not venture funded.
How much does PostgreSQL support cost?
It depends on the engagement model. On-Demand is time and materials billed in 15-minute increments, so you pay only for time used. SLA is annual and fixed-rate enterprise-wide; PSLA is monthly or annual. We never charge per instance, per socket, or per database size. Contact us for a quote against your environment.
Do you support managed Postgres like RDS, Aurora, Azure, or AlloyDB?
Yes — on every major managed platform, plus self-hosted and hybrid deployments, often covering the database layer your provider's support explicitly excludes.
Do you offer remote DBA and on-call support?
Yes. Our staff is distributed across the U.S. and globally, providing remote DBA and on-call PostgreSQL support around the clock.
What does Tier 4 support actually mean?
It describes how deep the expertise goes, not how many people your ticket passes through. Tickets are triaged and assigned to a senior Postgres engineer — people who work in Postgres internals, not generalists working from a runbook. In practice that means one handoff rather than a multi-level escalation chain.