Managed PostgreSQL

Managed PostgreSQL Services: In Your Cloud or Hosted on Ours

Last reviewed by Tyler Eastridge

AceMQ fully manages your PostgreSQL database in your own cloud account, Kubernetes cluster or data centre (Tier 3), or on a dedicated PostgreSQL host we run (Tier 4). We manage monitoring, high availability with Patroni failover, backups with point-in-time recovery, upgrades and the pager. The engine stays community Postgres, so the data and the exit are yours.

Support quotes answered within 1 hour, by a senior engineer.

min fastest response target, by plan
15
across Americas, EMEA, APAC
24/7
enterprise customers
160+
countries served
26+

Planning a build, upgrade or migration instead? See AceMQ PostgreSQL consulting and services.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

What's Included

Everything in your PostgreSQL managed services contract

Vacuum, replication, connection handling, backups and upgrades are all inside the agreement, for self-managed servers and the cloud services you run.

  • 01

    Monitoring and On-Call

    We manage monitoring of what predicts PostgreSQL incidents: replication lag and inactive replication slots, WAL volume growth, autovacuum progress and transaction ID age, long idle-in-transaction sessions, connection counts against max_connections, and disk headroom. Then we take the pager, so an alert reaches an engineer who already knows your topology.

  • 02

    High Availability and Failover

    We manage high availability with Patroni-based clusters, or the repmgr or cloud failover you already have, and rehearse a failover on a schedule instead of finding out during an outage. Patroni keeps its leader state in a distributed store such as etcd, Consul, ZooKeeper or Kubernetes, so that store is monitored as part of the cluster.

  • 03

    Backups and Point-in-Time Recovery

    A base backup plus continuous WAL archiving is what makes point-in-time recovery possible. We deploy and manage pgBackRest or Barman, set retention against your recovery point objective, and restore into a scratch environment on a schedule, because a backup that has never been restored is a guess.

  • 04

    Patching and CVE Management

    We manage patching: minor releases applied on a defined cadence, with CVE assessment against the version you run. PostgreSQL ships minor releases at least every three months. Databases on a major the community has stopped patching stay covered while the upgrade is planned.

  • 05

    Performance, Vacuum and Capacity

    We manage database performance: slow query review with EXPLAIN and pg_stat_statements, index and partition design as tables grow, autovacuum settings per busy table, connection pooling with PgBouncer in the mode your application needs, and capacity planning written down instead of kept in someone's head.

  • 06

    Cloud, Kubernetes and On-Premises Hosting

    We deploy and manage a PostgreSQL database on virtual machines or bare metal in your AWS, Azure or Google Cloud account, on Kubernetes with the operator you already use, and on-premises or air-gapped estates. The playbook is the same; the access and change process are yours.

Why AceMQ

Why PostgreSQL teams call us instead of searching forums

  • Your Cloud or Ours

    Run a fully managed PostgreSQL database in your own account or data centre (Tier 3) when residency and compliance rules keep the data in your boundary. Or have AceMQ host a dedicated PostgreSQL cluster (Tier 4), a managed Postgres database service when you want endpoints and no cloud account, patching or on-call rota to run. The operator is a PostgreSQL specialist in both cases, not a generic hosting contract.

  • A Named Senior Engineer Owns It

    Incidents start with a named senior PostgreSQL engineer who already knows your replication layout and your largest tables, not with a ticket queue. Response targets from 15 minutes, by plan, are response times, not resolution times.

  • The Application Is in Scope

    Many PostgreSQL incidents come from what the application does to the database: idle transactions that block vacuum, a pool per instance that exhausts connections, a query plan that flips. We manage the database server and also work on queries, workload patterns and pooling.

  • Community PostgreSQL, So Exit Is a Handover

    There is no fork and no licence change: PostgreSQL stays under the PostgreSQL License. Runbooks, topology documentation and monitoring configuration are maintained as yours. If you bring operations back in-house, or move a database between your infrastructure and ours, there is a current handover pack ready.

PostgreSQL platforms covered

PostgreSQL from 11 to 18, self-managed or on RDS, Aurora, Azure Flexible Server, Cloud SQL and AlloyDB, plus operator-managed clusters on Kubernetes.

  • Your AWS, Azure or Google Cloud account
  • Virtual machines and bare metal
  • PostgreSQL on Kubernetes
  • On-premises and air-gapped data centres
  • Patroni with etcd, Consul, ZooKeeper or Kubernetes
  • repmgr and streaming replication
  • pgBackRest and Barman backups
  • PgBouncer connection pooling
  • Dedicated PostgreSQL clusters hosted and operated by AceMQ

The 4 tiers

Four tiers of PostgreSQL operations outsourcing

Each tier moves one more responsibility from your team to AceMQ: first diagnosis, then early warning, then running the database, then owning the platform it runs on. Tiers 1 and 2 are AceMQ's PostgreSQL support. Tiers 3 and 4 are managed PostgreSQL services, and they are what the rest of this page describes.

Four tiers of PostgreSQL operations outsourcing
TierWho holds the pagerWhat AceMQ does
Tier 1: Reactive supportYouA senior PostgreSQL engineer responds to your tickets under the contracted SLA, with escalation and a written root-cause analysis after every P1. Access to your environment is on request, while a ticket is worked.
Tier 2: Proactive supportYou, with AceMQ raising problems earlyTier 1, plus monitoring and scheduled reviews of autovacuum, bloat, replication lag, backup restores and CVEs, so the problem is found in a review and not in an outage.
Tier 3: Managed on your infrastructureAceMQAceMQ operates PostgreSQL in your cloud account, Kubernetes cluster or data centre: monitoring, Patroni failover, backups, upgrades, change execution and on-call. You keep the account, the data and the cloud bill.
Tier 4: Managed on AceMQ infrastructureAceMQAceMQ provides PostgreSQL hosting: it hosts and operates a dedicated PostgreSQL cluster on its own infrastructure, with streaming replication, point-in-time recovery and upgrades. You get connection endpoints, not a server, a cloud account or an on-call rota to run.

Tier 3 and Tier 4 get the same operations. What differs is where the database runs and who owns the infrastructure underneath it. Tell us the workload and we will recommend a tier. Tiers 1 and 2 are on the PostgreSQL support page.

The same four tiers cover Kafka, Redis and RabbitMQ; the escalation-first option is set out in managed open-source operations.

In your account or RDS

Managed in your account, or on Amazon RDS and Aurora?

A cloud provider's managed PostgreSQL service runs the instance. AceMQ's Tier 3 runs the whole database, with high availability and backups, in an account you own. Both are legitimate; they differ on four things.

  • Where the data and the bill live

    On RDS or Aurora the database is a line on the provider's invoice and a resource inside its service. At Tier 3 it runs on instances you own, so the data stays in your account and your cloud commitments apply. At Tier 4 AceMQ owns the infrastructure and you receive endpoints.

  • Extensions and settings

    A managed database service allows the PostgreSQL extensions, such as PostGIS or pgvector, and the parameters on its supported list for your major version. Running PostgreSQL in your own account allows any extension and any setting, including a custom build, with AceMQ carrying the change risk.

  • The version clock

    A managed service does not remove the community end-of-life date. Amazon RDS Extended Support lets a major version keep running past the RDS end of standard support for an additional cost, available for up to three years, and a database past that date with Extended Support disabled is upgraded automatically (AWS documentation, checked 26 October 2026). At Tier 3 you choose the upgrade date.

  • Who owns the incident

    A provider supports its platform. Query plans, bloat, locks and connection exhaustion stay with your team on every managed service. At Tier 3 and 4 a PostgreSQL engineer owns those too, and we also support databases that stay on RDS or Aurora at Tier 1 or 2.

Vendor behaviour changes, so the full side-by-side with dates is kept on one page. Managed PostgreSQL options compared

Upgrades and HA

Upgrades from PostgreSQL 13 or 14, and the HA underneath

PostgreSQL gets its last community release five years after the first, and the clock is short for older majors. We manage the database upgrade and deploy the new version with a tested fallback. Managed PostgreSQL includes planning and running the move.

  • The dates (postgresql.org, checked 26 Oct 2026)

    PostgreSQL 13 had its final release on 13 November 2025. PostgreSQL 14 follows on 12 November 2026. PostgreSQL 15 ends on 11 November 2027, 16 on 9 November 2028, 17 on 8 November 2029 and 18 on 14 November 2030. Each major gets a final minor release and is then unsupported.

  • pg_upgrade or logical replication

    pg_upgrade moves the data files to a later major without a dump and restore, supports sources from 9.2 and later, and needs both servers stopped, with a --check run beforehand and an optional --link mode that is faster but leaves the old cluster unusable once the new one starts. Logical replication can replicate between major versions and is the route when the cutover window is short. We pick per database and rehearse on a copy first.

  • Choosing the target major

    The target is the newest major your extensions, drivers and application have been tested against. PostgreSQL 17 is supported until November 2029 and 18 until November 2030. Extensions such as PostGIS or pg_partman have their own version matrix, so the extension check comes before the date.

  • Patroni HA with a tested fallback

    Patroni is a template for high-availability PostgreSQL clusters. We design the high availability cluster, keep the distributed store healthy, run switchover tests, and keep the old primary available as a fallback until the new major has run production traffic. Where a major cannot move yet, PostgreSQL 11 to 14 can be kept patched through OSSeva.

Not ready to hand over operations yet? The 1 to 4 week HA review comes first on the support page. PostgreSQL support and HA review

Price drivers

What drives the price of managed PostgreSQL

AceMQ does not publish a price list. A managed PostgreSQL quote is built from these inputs, and the written quote returns within 1 hour of your request.

  • Clusters and nodes

    How many PostgreSQL clusters you run, how many nodes each has, and whether they are primary and replica pairs or Patroni clusters across zones.

  • Data size and recovery targets

    Database size and WAL volume, and the recovery point and recovery time objectives you need, which set the backup and restore work.

  • Cover hours

    The price follows the cover you need, from business hours to 24/7 on-call with response targets from 15 minutes, by plan. Tell us which databases are production.

  • Tier 3 or Tier 4

    At Tier 3 you pay your cloud provider for infrastructure and AceMQ for operations. At Tier 4 the infrastructure is part of the AceMQ quote. A major-version upgrade, if one is due, is scoped in the quote.

Not a fit for

When managed PostgreSQL from AceMQ is the wrong tool

We would rather say so up front.

  • Self-service database consoles

    AceMQ is a specialist service with named engineers, not a self-service console where you click to provision a database. If you want pay-as-you-go instances with no contract, a cloud provider's service fits better.

  • Migrating from Oracle or SQL Server

    Moving an Oracle or SQL Server database onto PostgreSQL is a separate project and is run through OSSeva, AceMQ's extended-support platform, not through this service. Once the database is on PostgreSQL we can operate it.

  • A single small, non-critical database

    A scratch database with no uptime target is covered by the community and a current version. The service pays for itself where PostgreSQL holds revenue or regulated data.

Running several engines? One contract can also cover Redis, Kafka, MySQL and more. Database support across engines

Escalation Path

Your first hour of a PostgreSQL outage

Calls land with an engineer who reads pg_stat_activity and WAL positions fluently, so the first ten minutes go to the database, not to background.

  1. From 15 min (by plan)first responseEmergencyProduction down: the primary will not accept writes, the data volume is full, transaction ID wraparound has begun
  2. 1 hourfirst responseCriticalSerious degradation: connections maxed out, a replica far behind, a replication slot retaining WAL, queries timing out after a plan flip
  3. 4 hoursfirst responseHighAutovacuum falling behind on a hot table, checkpoint latency spikes, synchronous commits stalling on a slow standby
  4. Next Dayfirst responseStandardQuestions on pooler setup, index maintenance, backup and point-in-time recovery design, upgrade sequencing

Plans set the clock: a database that has stopped accepting writes is not queued behind a planning question.

Want the same PostgreSQL engineers every time something breaks? Ask for a quote or send us a message.

Contact Us

Support In Practice

PostgreSQL recoveries and tuning work

PostgreSQL support work from AceMQ. Each card links to the full write-up: the database estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

All use cases

Support options

Four tiers of PostgreSQL support.

AceMQ offers PostgreSQL support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for databases your DBAs run, proactive monitoring that finds bloat, lag and backup gaps first, managed PostgreSQL on your own infrastructure, and fully managed PostgreSQL on AceMQ infrastructure. Current releases are supported 24/7, PostgreSQL 14 can be upgraded as a project with an HA review first, and PostgreSQL 11 to 14 can be kept patched through OSSeva.

  • Tier 1

    PostgreSQL 24/7 Support & Incident Management

    Your team owns the database, we take escalations

    Best for: Teams with in-house DBAs or developers who need a senior PostgreSQL engineer for incidents beyond their experience.

  • Tier 2

    PostgreSQL 24/7 Support with Proactive Monitoring

    Routine reviews of vacuum, replication and backups

    Best for: Teams that would rather catch slot growth, bloat and wraparound age on a schedule than during a page at night.

  • Tier 3

    Managed PostgreSQL on Your Infrastructure

    We operate PostgreSQL on your servers

    Best for: Organizations that keep databases on their own hardware, VMs or Kubernetes and want operations handled by specialists.

  • Tier 4

    Fully Managed PostgreSQL on AceMQ Infrastructure

    AceMQ takes over PostgreSQL operations as a service

    Best for: Teams whose product depends on PostgreSQL but who do not want to hire and retain database operators.

FAQ

PostgreSQL managed services questions

Still have questions about PostgreSQL? Email an Expert

What is managed PostgreSQL (managed Postgres)?

Managed PostgreSQL, also called a managed Postgres database, means someone else operates your PostgreSQL databases: monitoring, failover, backups, patching, upgrades and on-call. Cloud providers such as Amazon RDS and Aurora, Google Cloud SQL and Azure Database for PostgreSQL run the instance in their service. AceMQ offers two models. We operate PostgreSQL on your own infrastructure, so the data and the account stay yours, or we host a dedicated cluster on ours. In both, a PostgreSQL specialist also owns queries, vacuum health and connection pooling.

Managed PostgreSQL vs RDS: what is the difference?

RDS runs PostgreSQL instances inside AWS's service, with Multi-AZ, backups and minor-version patching handled for you. Your team still owns schema design, query plans, autovacuum, connection counts and the timing of major upgrades. AceMQ's managed PostgreSQL covers those as well, and runs the database in your account (Tier 3) or on a dedicated cluster we host (Tier 4). Choose RDS when the workload is standard and procurement favours one cloud. Choose this when you need extensions or settings RDS blocks, strict residency, a version a provider has retired, or a named engineer. The trade-offs are set out in Managed PostgreSQL options compared.

How is managed PostgreSQL different from AceMQ's PostgreSQL support?

Support is an SLA over a database your team runs: you hold the pager and call us when something breaks. Managed services means we run it: monitoring, failover, backups, upgrades and on-call are ours. Teams with a capable DBA team usually want support (Tiers 1 and 2). Teams that want PostgreSQL to stop being their problem want managed services (Tiers 3 and 4).

Do you run Patroni?

Yes. Patroni is a template for high availability PostgreSQL clusters and keeps its state in a distributed configuration store such as etcd, Consul, ZooKeeper or Kubernetes. We build and operate Patroni clusters, monitor the store as part of the cluster, and test switchover on a schedule. If your estate runs repmgr or a cloud service's own failover, we operate that instead of forcing a change.

Can you manage PostgreSQL on-prem?

Yes. Tier 3 runs in your data centre, on virtual machines, bare metal or Kubernetes, including air-gapped estates, using your access controls and change process. Tier 4 is the alternative when you would rather not run infrastructure at all.

Can you take over an existing PostgreSQL estate?

Yes. We start with an assessment of version and patch position, replication and failover, backups and restore history, autovacuum and transaction ID age, extensions and monitoring gaps. We remediate the active risks and then take the pager.

Can you upgrade us from PostgreSQL 13 or 14?

Yes, as a project inside the service. PostgreSQL 13 had its final community release on 13 November 2025 and PostgreSQL 14 gets its last on 12 November 2026. We test extensions and drivers against the target major, pick pg_upgrade or logical replication per database, rehearse on a copy of production and keep the old primary as a fallback until the new major has run production traffic. PostgreSQL 11 to 14 can be kept patched through OSSeva while the move is planned.

Which cloud providers can you manage PostgreSQL on?

We operate PostgreSQL in your own AWS account, Azure subscription or Google Cloud project, on virtual machines or Kubernetes, and on premises. Databases that stay on Amazon RDS, Aurora, Cloud SQL or Azure Database for PostgreSQL can be covered at Tier 1 or Tier 2, where AceMQ supports the workload but the provider runs the instance.

How fast do you respond when PostgreSQL breaks?

From 15 minutes on the top plans, at any hour. Take a Sev 1 where an abandoned replication slot has filled the data volume: an engineer joins a bridge, reads pg_replication_slots, frees space safely and drops the slot, then writes up the root cause. P2 is 1 hour, P3 4 hours, P4 next business day.

Do you also manage Redis, Kafka or MongoDB?

Redis and Kafka, yes: both run on the same four tiers, as separate managed services. MongoDB, MySQL, Elasticsearch and other databases are covered by AceMQ support under the same contract, so a mixed estate can have one SLA and one escalation path.

Can we start with one PostgreSQL engagement before committing?

Yes. A health check, a vacuum and bloat cleanup, an upgrade rehearsal or a backup restore test can each be scoped as a single job. If incidents continue, an annual agreement adds 24/7 response and engineers who already know your schema and replication topology.

How do you price PostgreSQL support?

Contracts generally fall between $24,000 and $72,000 a year (USD). We count clusters and replicas, check which version and platform you run, ask how critical the write path is, and match a response plan to it. Share those and a quote arrives within 1 hour.

Let's talk

Stop Running PostgreSQL. Choose Where It Lives.

Reactive cover, proactive reviews, or AceMQ running PostgreSQL for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.

A senior PostgreSQL engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a PostgreSQL Architect