<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kamal G</title>
    <description>The latest articles on DEV Community by Kamal G (@kamal_g_671df6421e).</description>
    <link>https://dev.to/kamal_g_671df6421e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211013%2F2a260372-8e41-4003-9b68-6e09b896b774.png</url>
      <title>DEV Community: Kamal G</title>
      <link>https://dev.to/kamal_g_671df6421e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kamal_g_671df6421e"/>
    <language>en</language>
    <item>
      <title>Crunchy Bridge vs ClickHouse Managed Postgres for AI Agents</title>
      <dc:creator>Kamal G</dc:creator>
      <pubDate>Fri, 13 Nov 2026 07:36:29 +0000</pubDate>
      <link>https://dev.to/database-engineering/crunchy-bridge-vs-clickhouse-managed-postgres-ai-agents-performance-and-pricing-202a</link>
      <guid>https://dev.to/database-engineering/crunchy-bridge-vs-clickhouse-managed-postgres-ai-agents-performance-and-pricing-202a</guid>
      <description>&lt;p&gt;AI agent applications need a database to persist state, handle concurrent requests, and retrieve context while an agent works. Frequent checkpoints and context queries make database latency part of an agent's response time, and the same service usually holds the application's users, permissions, and transactional data.&lt;/p&gt;

&lt;p&gt;This guide compares ClickHouse Managed Postgres and Crunchy Bridge across dimensions that matter for AI agent applications: transactional performance, retrieval, agent tooling, and development workflows. It also covers storage and scaling, availability, recovery, pricing, analytics integration, and migration.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;TL;DR&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Choose ClickHouse Managed Postgres when you need fast transactional throughput on local NVMe, integrated operational tooling, or a path into ClickHouse analytics. The Xata acquisition aims to add scale-to-zero and copy-on-write branching. Choose Crunchy Bridge when you need independent storage sizing, broad PostgreSQL extension support, or multi-cloud deployment.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Local NVMe gives ClickHouse Managed Postgres a direct storage path. PostgresBench shows substantially higher throughput for ClickHouse at the larger tested configuration and comparable throughput at the smaller one.
&lt;/li&gt;
&lt;li&gt;ClickHouse offers asynchronous or synchronous-quorum standbys. Bridge uses a hidden HA standby on eligible plans.
&lt;/li&gt;
&lt;li&gt;Both support vector retrieval, pooled connections, APIs, CLIs, and isolated database copies. ClickHouse adds read-only MCP access to PostgreSQL data and diagnostics. Bridge offers configurable pooling modes.
&lt;/li&gt;
&lt;li&gt;ClickHouse scales through NVMe instance configurations. Bridge can grow storage independently of compute.
&lt;/li&gt;
&lt;li&gt;ClickHouse integrates PostgreSQL with a separate ClickHouse analytical service. Compare the full architecture, including standbys, backups, replicas, and analytical capacity.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;ClickHouse Managed Postgres vs Crunchy Bridge at a glance&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;ClickHouse Managed Postgres runs &lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;production PostgreSQL workloads&lt;/a&gt; on local NVMe within ClickHouse Cloud. Its managed replication path connects Postgres to a separately provisioned ClickHouse analytical service. ClickHouse’s acquisition of Xata aims to add scale-to-zero and copy-on-write branching to the service.&lt;/p&gt;

&lt;p&gt;Crunchy Bridge is Crunchy Data's managed PostgreSQL service across AWS, Google Cloud, and Azure. It runs transactional applications and agent backends, with independent storage sizing and broad PostgreSQL tooling.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Dimension&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;th&gt;Crunchy Bridge&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Best-fit workloads&lt;/td&gt;
&lt;td&gt;AI agent and application backends with performance-critical workloads, integrated operational tooling, or growing analytical demand&lt;/td&gt;
&lt;td&gt;AI agent and application backends needing flexible storage sizing, broad PostgreSQL tooling, or multi-cloud deployment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage&lt;/td&gt;
&lt;td&gt;Local NVMe bundled with the VM configuration&lt;/td&gt;
&lt;td&gt;AWS gp3 sized independently of compute&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage growth&lt;/td&gt;
&lt;td&gt;Storage grows through VM configuration changes&lt;/td&gt;
&lt;td&gt;Storage grows independently of compute&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;HA&lt;/td&gt;
&lt;td&gt;No standby, one asynchronous standby, or two synchronous-quorum standbys&lt;/td&gt;
&lt;td&gt;No standby, or one hidden hot standby on eligible non-Hobby plans&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pooling&lt;/td&gt;
&lt;td&gt;PgBouncer transaction pooling&lt;/td&gt;
&lt;td&gt;PgBouncer transaction and session modes. Unavailable on Hobby&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Retrieval&lt;/td&gt;
&lt;td&gt;pgvector, full-text and BM25 options. pg_clickhouse pushes vector and search queries to ClickHouse for retrieval beyond PostgreSQL scale&lt;/td&gt;
&lt;td&gt;pgvector, full-text and BM25 options&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Isolated development copies&lt;/td&gt;
&lt;td&gt;Restore-based branches. Copy-on-write branching planned through the Xata acquisition&lt;/td&gt;
&lt;td&gt;Restore-based forks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Diagnostics and agent tools&lt;/td&gt;
&lt;td&gt;Remote MCP, ClickHouse Agents,  &lt;a href="https://github.com/ClickHouse/clickhousectl" rel="noopener noreferrer"&gt;clickhousectl&lt;/a&gt; CLI, query Insights, metrics and logs&lt;/td&gt;
&lt;td&gt;Database Insights, &lt;code&gt;cb scope&lt;/code&gt;, metrics and log export&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Standard backup retention&lt;/td&gt;
&lt;td&gt;One day on Basic, seven days on Scale&lt;/td&gt;
&lt;td&gt;Ten days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing&lt;/td&gt;
&lt;td&gt;Complete NVMe VM configurations plus selected standbys&lt;/td&gt;
&lt;td&gt;Separate instance and storage rates. HA doubles the cluster price&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytics&lt;/td&gt;
&lt;td&gt;Read replicas and integrated replication to a separate ClickHouse service&lt;/td&gt;
&lt;td&gt;Read replicas and external analytical replication or query access&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Bridge's &lt;a href="https://docs.crunchybridge.com/concepts/postgres-versions" rel="noopener noreferrer"&gt;PostgreSQL version policy&lt;/a&gt; lists versions 15 through 18. New version 15 provisioning has been limited since May 11, 2026, with availability ending May 10, 2027. ClickHouse's &lt;a href="https://clickhouse.com/docs/products/managed-postgres/openapi" rel="noopener noreferrer"&gt;OpenAPI guide&lt;/a&gt; identifies 17 as the default and demonstrates provisioning 18. Select the required version and extensions for the target cloud and region.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;PostgreSQL storage and scaling: local NVMe vs network storage&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;ClickHouse Managed Postgres stores data on &lt;a href="https://clickhouse.com/docs/products/managed-postgres/overview" rel="noopener noreferrer"&gt;server-local NVMe drives&lt;/a&gt; attached to the database server. Crunchy Bridge on AWS uses gp3 block storage, with disk capacity sized independently of compute.&lt;/p&gt;

&lt;p&gt;Local NVMe removes the network-storage hop from disk reads and writes. Disk-bound transactions benefit from that shorter path. Queries served from memory depend more on CPU, indexes, and concurrency. For agent applications, storage behavior affects checkpoints and context queries that hit disk.&lt;/p&gt;

&lt;p&gt;ClickHouse packages storage with the selected VM. To &lt;a href="https://clickhouse.com/docs/products/managed-postgres/scaling" rel="noopener noreferrer"&gt;resize an instance&lt;/a&gt;, ClickHouse restores a new instance, lets it catch up, and does a controlled failover. Storage autoscaling also moves the database to a configuration with more capacity, so growth follows the available VM sizes. The Xata acquisition aims to bring scale-to-zero to ClickHouse Managed Postgres.&lt;/p&gt;

&lt;p&gt;Crunchy Bridge &lt;a href="https://docs.crunchybridge.com/how-to/resize" rel="noopener noreferrer"&gt;attempts online storage growth&lt;/a&gt; before falling back to a replacement machine when cloud-provider restrictions prevent it. Storage increases also apply to the HA standby. Changing instance size or tier uses a new machine and briefly interrupts connections. The connection string stays the same, but your application has to reconnect.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;ClickHouse Managed Postgres vs Crunchy Bridge: performance benchmarks&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;ClickHouse's PostgresBench measures transactional throughput using pgbench's TPC-B-like workload. Its &lt;a href="https://github.com/ClickHouse/PostgresBench" rel="noopener noreferrer"&gt;source code and methodology&lt;/a&gt; make the tests reproducible. The published results compare complete service configurations, including their storage and HA settings. They don't measure end-to-end agent latency or vector retrieval.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;HA-disabled throughput at two instance sizes&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;The &lt;a href="https://raw.githubusercontent.com/ClickHouse/PostgresBench/main/data.generated.js" rel="noopener noreferrer"&gt;HA-disabled tests&lt;/a&gt; use 256 clients, 16 threads, prepared queries, and three 600-second runs per service in AWS us-east-2. The listed configurations run PostgreSQL 18.3 with provider-default settings. The values below are three-run means.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;HA-disabled configuration&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres (TPS)&lt;/th&gt;
&lt;th&gt;Crunchy Bridge (TPS)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;16 vCPUs, 64 GB RAM, about 500 GB data&lt;/td&gt;
&lt;td&gt;26,105&lt;/td&gt;
&lt;td&gt;10,954&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4 vCPUs, 16 GB RAM, about 100 GB data&lt;/td&gt;
&lt;td&gt;6,013&lt;/td&gt;
&lt;td&gt;6,320&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;TPS means transactions per second.&lt;/p&gt;

&lt;p&gt;At 16 vCPUs and 64 GB RAM, ClickHouse Managed Postgres delivered substantially higher throughput in the HA-disabled benchmark. At 4 vCPUs and 16 GB RAM, the services deliver comparable throughput, with Crunchy Bridge about 5% higher in this test. Equal CPU and memory counts don't imply identical processors, storage, or prices. The relevant result depends on the instance size and transaction mix your application will use.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Throughput and latency with HA enabled&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse's &lt;a href="https://clickhouse.com/blog/postgresbench-ha" rel="noopener noreferrer"&gt;PostgresBench HA comparison&lt;/a&gt; tests 16 vCPUs, 64 GB RAM, and about 500 GB of data. Its table publishes the following results, including single-node baselines drawn from the HA-disabled test set.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service and configuration&lt;/th&gt;
&lt;th&gt;Published throughput (TPS)&lt;/th&gt;
&lt;th&gt;Average latency (ms)&lt;/th&gt;
&lt;th&gt;p99 latency (ms)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;ClickHouse Managed Postgres, single node&lt;/td&gt;
&lt;td&gt;26,328&lt;/td&gt;
&lt;td&gt;9.70&lt;/td&gt;
&lt;td&gt;13.20&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ClickHouse Managed Postgres, one asynchronous standby&lt;/td&gt;
&lt;td&gt;24,667&lt;/td&gt;
&lt;td&gt;10.37&lt;/td&gt;
&lt;td&gt;24.17&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ClickHouse Managed Postgres, two synchronous-quorum standbys&lt;/td&gt;
&lt;td&gt;20,720&lt;/td&gt;
&lt;td&gt;12.34&lt;/td&gt;
&lt;td&gt;33.49&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Crunchy Bridge, single node&lt;/td&gt;
&lt;td&gt;11,113&lt;/td&gt;
&lt;td&gt;23.00&lt;/td&gt;
&lt;td&gt;41.68&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Crunchy Bridge, HA with one standby, labeled asynchronous by ClickHouse&lt;/td&gt;
&lt;td&gt;11,135&lt;/td&gt;
&lt;td&gt;23.00&lt;/td&gt;
&lt;td&gt;41.89&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The 26,328 TPS ClickHouse baseline comes from an individual run, while 26,105 TPS above is the three-run mean. The two tables draw on overlapping benchmark data. The latency column reports averages.&lt;/p&gt;

&lt;p&gt;ClickHouse's synchronous-quorum configuration waits for standby acknowledgement before completing a commit. In this test, it delivered lower throughput and higher p99 latency than the single-node configuration. Compare performance using the durability mode your application requires. Bridge's similar single-node and HA results describe its tested configuration. They don't prove its contractual durability guarantee. The publication measures HA's performance cost. It doesn't supply a failure-injection or recovery assessment.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Agent and developer workflows: retrieval, pooling, branching, and MCP&lt;/strong&gt;
&lt;/h2&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Example: a support agent's database workload&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Take a support agent that reads account and conversation history, retrieves relevant context, saves checkpoints, and updates a support ticket. Both services can keep the account, ticket, and current agent state in Postgres, with pgvector or keyword queries supplying context.&lt;/p&gt;

&lt;p&gt;Teams analyze recorded runs and tool outcomes to improve the application. The agent may also query historical business data while composing a response. If those scans interfere with live transactions, route suitable reads to a replica or replicate history to a separate analytical service. Operators use database diagnostics to investigate slow queries and resource pressure.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;LangGraph checkpointing and PostgreSQL state persistence&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;LangGraph &lt;a href="https://docs.langchain.com/oss/python/langgraph/checkpointers" rel="noopener noreferrer"&gt;checkpoints at super-step boundaries&lt;/a&gt; and records task-level pending writes for fault tolerance. Its persistence modes include synchronous, asynchronous, and exit-only. The &lt;a href="https://github.com/langchain-ai/langgraph/blob/main/libs/checkpoint-postgres/README.md" rel="noopener noreferrer"&gt;PostgreSQL saver&lt;/a&gt; uses Psycopg 3, and manually supplied connections require &lt;code&gt;autocommit=True&lt;/code&gt; and &lt;code&gt;dict_row&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Other agent frameworks and custom tool loops differ in how they execute work, but frequent state reads, writes, and context lookups create similar database demands. Checkpoint frequency, state size, concurrency, and transaction behavior determine how much database capacity each application needs.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;PgBouncer connection pooling and session compatibility&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Both services provide PgBouncer transaction pooling. Crunchy Bridge also supports session pooling. PgBouncer isn't available on Hobby plans. Bridge's &lt;a href="https://docs.crunchybridge.com/how-to/pgbouncer" rel="noopener noreferrer"&gt;pooler setup&lt;/a&gt; requires the &lt;code&gt;crunchy_pooler&lt;/code&gt; extension in each database using the pooled endpoint.&lt;/p&gt;

&lt;p&gt;Transaction pooling reuses PostgreSQL backends across client transactions, letting many short-lived application or function connections share a smaller backend pool. Session advisory locks and LISTEN need a session-preserving connection. Sending NOTIFY works in transaction mode. Protocol-level prepared statements require compatible PgBouncer settings and driver behavior. SQL-level &lt;code&gt;PREPARE&lt;/code&gt; carries a separate limitation.&lt;/p&gt;

&lt;p&gt;ClickHouse's &lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;connection limits example&lt;/a&gt; illustrates 2,500 pooler clients sharing 500 PostgreSQL backends. Pooling accommodates connection bursts, while concurrent database work still depends on backend capacity. Confirm both limits for the selected plan, then test the saver, prepared statements, retries, and reconnects through your application's endpoint.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Vector and hybrid search: pgvector, HNSW, and BM25&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Both services support pgvector and PostgreSQL full-text search. ClickHouse Managed Postgres includes &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;pgvector 0.8.6 with IVFFlat and HNSW&lt;/a&gt;. Crunchy Bridge provides &lt;a href="https://docs.crunchybridge.com/extensions-and-languages/vector" rel="noopener noreferrer"&gt;pgvector on all clusters&lt;/a&gt;, including HNSW support. Check the installed extension version on the target cluster for either service.&lt;/p&gt;

&lt;p&gt;Vector similarity retrieves semantically related context. Keyword and fuzzy matching help with exact terms, identifiers, and misspellings. ClickHouse Managed Postgres also supports &lt;a href="https://clickhouse.com/resources/engineering/scale-vector-search-postgres" rel="noopener noreferrer"&gt;VectorChord and BM25 retrieval&lt;/a&gt;. Bridge offers &lt;a href="https://docs.crunchybridge.com/extensions-and-languages/pg_textsearch" rel="noopener noreferrer"&gt;BM25 through &lt;code&gt;pg_textsearch&lt;/code&gt;&lt;/a&gt; on PostgreSQL 17 and 18, requiring a current cluster image and preload configuration. Applications combine and rank vector and keyword results in SQL or application code. When retrieval workloads outgrow PostgreSQL capacity, teams using ClickHouse Managed Postgres can store vectors and search indexes in ClickHouse and query them through PostgreSQL via pg_clickhouse. ClickHouse handles vector and text search at scales beyond what PostgreSQL extensions support, while the application retains its PostgreSQL interface.&lt;/p&gt;

&lt;p&gt;Upstream pgvector stores &lt;a href="https://github.com/pgvector/pgvector" rel="noopener noreferrer"&gt;4 × dimensions + 8 bytes per vector&lt;/a&gt;. One million 1,536-dimensional vectors take about 6.15 GB of raw vector values before row, index, and WAL overhead. Size the database for this retrieval data alongside checkpoints and application records. Then test recall, latency, and tenant-filtered retrieval while representative state writes run.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Extension&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;th&gt;Crunchy Bridge&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;pg_trgm&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;Available&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/extensions-and-languages" rel="noopener noreferrer"&gt;Available&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PostGIS&lt;/td&gt;
&lt;td&gt;Available&lt;/td&gt;
&lt;td&gt;Available, including PostGIS Raster&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;pg_cron&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Available&lt;/td&gt;
&lt;td&gt;Available in preload configuration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;pg_stat_statements&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Available&lt;/td&gt;
&lt;td&gt;Available in preload configuration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ClickHouse query access&lt;/td&gt;
&lt;td&gt;Available: &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;&lt;code&gt;pg_clickhouse&lt;/code&gt; preinstalled&lt;/a&gt;
&lt;/td&gt;
&lt;td&gt;Available: &lt;a href="https://docs.crunchybridge.com/extensions-and-languages" rel="noopener noreferrer"&gt;&lt;code&gt;clickhouse_fdw&lt;/code&gt;&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Database branching, forks, and provisioning tools&lt;/strong&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Workflow&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;th&gt;Crunchy Bridge&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;API automation&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/openapi" rel="noopener noreferrer"&gt;OpenAPI management API&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/api" rel="noopener noreferrer"&gt;Bridge management API&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Command-line automation&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/blog/clickhousectl-v0-2-0-postgres-clickpipes-more" rel="noopener noreferrer"&gt;&lt;code&gt;clickhousectl&lt;/code&gt; CLI&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/quickstart/cli" rel="noopener noreferrer"&gt;&lt;code&gt;cb&lt;/code&gt; CLI&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Infrastructure as code&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/terraform" rel="noopener noreferrer"&gt;Postgres Terraform resource in alpha&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/concepts/terraform" rel="noopener noreferrer"&gt;Bridge Terraform provider&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Isolated database copy&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/branching" rel="noopener noreferrer"&gt;ClickHouse database branches&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/how-to/point-in-time-recovery" rel="noopener noreferrer"&gt;Crunchy Bridge PITR forks&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dedicated read scaling&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/read-replicas" rel="noopener noreferrer"&gt;ClickHouse read replicas&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/how-to/replicas" rel="noopener noreferrer"&gt;Bridge read replicas&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Branches and forks restore a base backup and replay WAL into an independent deployment. They work for migration rehearsals, index experiments, and debugging against realistic data. For short-lived tests, account for provisioning time and the cost of a separate running database. Production-derived copies also need masking and access controls. Copy-on-write branching is planned for ClickHouse Managed Postgres through the Xata acquisition.&lt;/p&gt;

&lt;p&gt;Read replicas serve lag-tolerant reads separately from the writer. ClickHouse replicas use archived-WAL shipping by default, and support can configure lower-lag replication options. Bridge replicas have independently chosen compute and the primary's storage size, with cross-region and cross-provider deployments supported. Keep reads on the primary when an agent must see the latest committed checkpoint. HA standbys aren't the same as these application read endpoints.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;PostgreSQL monitoring and MCP integration&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse Managed Postgres brings service metrics, &lt;a href="https://clickhouse.com/docs/products/managed-postgres/monitoring/query-insights" rel="noopener noreferrer"&gt;Query Insights&lt;/a&gt;, and PostgreSQL logs into ClickHouse Cloud. Its &lt;a href="https://clickhouse.com/docs/products/cloud/features/ai-ml/remote-mcp" rel="noopener noreferrer"&gt;ClickHouse Cloud remote MCP server&lt;/a&gt; gives compatible agents read-only PostgreSQL queries, service metrics, and slow-query investigation. Running PostgreSQL queries through MCP requires OAuth. API-key authentication can't run that query tool.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/blog/clickhouse-agents-managed-postgres" rel="noopener noreferrer"&gt;ClickHouse Agents for Managed Postgres&lt;/a&gt; provides an interface for exploring data and investigating performance across Postgres and ClickHouse. Teams use it to dig into retrieval queries, state updates, and resource pressure when agent steps or application requests slow down.&lt;/p&gt;

&lt;p&gt;Crunchy Bridge provides &lt;a href="https://docs.crunchybridge.com/insights-metrics" rel="noopener noreferrer"&gt;Database Insights and &lt;code&gt;cb scope&lt;/code&gt;&lt;/a&gt;, system metrics, and log export. Teams can investigate long-running queries, index use, bloat, vacuum activity, and connections when diagnosing slow agent steps or application requests.&lt;/p&gt;

&lt;p&gt;Application agents read and write through PostgreSQL drivers or custom tool integrations on either service, using the permissions assigned to those integrations. ClickHouse's remote MCP adds read-only data exploration and database diagnostics on top.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;High availability, backups, and PostgreSQL upgrades&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;HA keeps a standby available for primary failure. Backups and point-in-time recovery (PITR) restore earlier database state. Agent applications need both a recovery time objective (RTO) for acceptable downtime and a recovery point objective (RPO) for acceptable data loss.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;HA modes and commit-path trade-offs&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/high-availability" rel="noopener noreferrer"&gt;ClickHouse Managed Postgres HA&lt;/a&gt; offers no standby, one asynchronous standby, or two synchronous-quorum standbys. With no standby, recovery can take longer. Asynchronous commits don't wait for the standby, so recent committed transactions can be lost if the primary fails before replication catches up. With two synchronous standbys, a commit waits for acknowledgement from at least one.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.crunchybridge.com/concepts/high-availability" rel="noopener noreferrer"&gt;Crunchy Bridge HA&lt;/a&gt; uses a hidden hot standby sized like the primary. On failure, Bridge promotes it and creates a replacement standby. Existing sessions drop even though the connection string stays the same. Standard and Memory-optimized clusters with HA carry a &lt;a href="https://docs.crunchybridge.com/concepts/support" rel="noopener noreferrer"&gt;99.95% uptime SLA&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Bridge's public HA description doesn't specify synchronous acknowledgement or a numeric RPO/RTO. ClickHouse labels its tested Bridge configuration asynchronous. Confirm Bridge's commitment for the selected deployment before treating the two services' HA durability guarantees as equivalent.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Backup retention and point-in-time recovery (PITR)&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Both services automate physical backups and archive WAL every 60 seconds or 16 MB, whichever comes first.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Recovery capability&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;th&gt;Crunchy Bridge&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Standard backup retention&lt;/td&gt;
&lt;td&gt;One day on Basic, seven days on Scale&lt;/td&gt;
&lt;td&gt;Ten days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PITR destination&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/backup-and-restore" rel="noopener noreferrer"&gt;Restore into a new instance&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://docs.crunchybridge.com/concepts/backups" rel="noopener noreferrer"&gt;Restore into a new fork&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extended retention&lt;/td&gt;
&lt;td&gt;Longer retention requires support&lt;/td&gt;
&lt;td&gt;Daily, weekly, monthly, and yearly backups configurable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;30-day continuous PITR&lt;/td&gt;
&lt;td&gt;Confirm availability and pricing with support. No standard 30-day PITR price is published&lt;/td&gt;
&lt;td&gt;Extended restore points don't provide continuous PITR throughout the 30-day period&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Bridge's extended backups keep enough WAL to recover each selected snapshot, rather than the full intervening history. Specify daily restore points or continuous PITR when requesting a longer retention policy.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Maintenance and upgrades&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse uses failover-based upgrades with &lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;configurable scheduling&lt;/a&gt;, typically interrupting service for a few seconds.&lt;/p&gt;

&lt;p&gt;Crunchy Bridge provides a &lt;a href="https://docs.crunchybridge.com/concepts/maintenance" rel="noopener noreferrer"&gt;three-hour maintenance window&lt;/a&gt;, with none configured by default. Its &lt;a href="https://docs.crunchybridge.com/guides/major-version-upgrades" rel="noopener noreferrer"&gt;major-version upgrade&lt;/a&gt; uses a hidden upgrade standby and a write halt. A successful upgrade can't roll back in place. Post-upgrade analyze and backup add I/O work.&lt;/p&gt;

&lt;p&gt;Applications must reconnect and handle interrupted transactions after either service's lifecycle events.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Pricing comparison and total deployment cost&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;ClickHouse Managed Postgres prices complete VM configurations, while Crunchy Bridge prices compute and storage separately. Region, service tier, capacity, and HA requirements determine the base deployment cost. Replicas, development databases, backups, support, and analytics add to the full bill.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Pricing models and cost drivers&lt;/strong&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Price driver&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;th&gt;Crunchy Bridge&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Primary capacity&lt;/td&gt;
&lt;td&gt;A &lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;complete VM configuration&lt;/a&gt; bundles CPU, memory, and local NVMe storage&lt;/td&gt;
&lt;td&gt;A &lt;a href="https://docs.crunchybridge.com/concepts/plans-pricing" rel="noopener noreferrer"&gt;compute plan and separately sized storage&lt;/a&gt; determine the primary's cost&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage growth&lt;/td&gt;
&lt;td&gt;More storage requires selecting another NVMe VM configuration&lt;/td&gt;
&lt;td&gt;Storage can grow independently of compute&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;High availability&lt;/td&gt;
&lt;td&gt;Selected standby VMs add to the primary configuration's cost&lt;/td&gt;
&lt;td&gt;HA doubles the cluster price, including compute and storage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Backup storage&lt;/td&gt;
&lt;td&gt;An allowance covers backup storage up to provisioned disk capacity. Excess bytes bill separately&lt;/td&gt;
&lt;td&gt;Standard backups are included. &lt;a href="https://docs.crunchybridge.com/changelog" rel="noopener noreferrer"&gt;Extended backups add charges based on storage size&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Replicas and development copies&lt;/td&gt;
&lt;td&gt;Additional deployments consume their own provisioned resources&lt;/td&gt;
&lt;td&gt;Additional deployments consume their own provisioned resources&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Support&lt;/td&gt;
&lt;td&gt;Included support and response commitments depend on the organization tier&lt;/td&gt;
&lt;td&gt;Standard support is included. &lt;a href="https://docs.crunchybridge.com/concepts/support" rel="noopener noreferrer"&gt;Paid support tiers&lt;/a&gt; add response and escalation commitments&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytics&lt;/td&gt;
&lt;td&gt;Replication from Managed Postgres to ClickHouse is free. Analytical compute and storage bill separately&lt;/td&gt;
&lt;td&gt;Include the selected connector and analytical destination's costs&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How to compare total PostgreSQL deployment costs&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Compare deployments that meet the same throughput, latency, usable-storage, and recovery requirements. ClickHouse's bundled NVMe configurations and Bridge's independent storage sizing affect how each deployment grows as agent state, retrieval indexes, and application records accumulate.&lt;/p&gt;

&lt;p&gt;Include applicable network transfer, support, and additional databases or analytical services. ClickHouse bills data transfer at &lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;ClickHouse Cloud rates&lt;/a&gt;. For longer backup retention, specify whether your application needs periodic restore points or continuous point-in-time recovery.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;PostgreSQL read replicas and ClickHouse analytics integration&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Agent traces, tool-call audits, and token-cost records can start in Postgres. A separate analytical service lets teams scale analytical queries and historical retention separately from the database serving transactions and current agent state.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;AI agent analytics: execution traces and business history&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Teams analyze recorded runs, tool outcomes, evaluations, latency, token usage, and costs to improve an agent application. Application instrumentation supplies the traces and relationships among model and tool calls. The database stores and queries those records.&lt;/p&gt;

&lt;p&gt;Application agents also query historical events and business aggregates while answering questions or completing tasks.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;ClickPipes replication and PostgreSQL analytics alternatives&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;The &lt;a href="https://clickhouse.com/docs/products/managed-postgres/clickhouse-integration" rel="noopener noreferrer"&gt;ClickPipes setup for Managed Postgres&lt;/a&gt; connects Postgres to an existing or new ClickHouse service. Use an initial load to copy existing rows, change data capture (CDC) to capture ongoing changes, or both. A primary key or supported replica identity is required.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Analytical path&lt;/th&gt;
&lt;th&gt;Query execution&lt;/th&gt;
&lt;th&gt;Setup and consistency&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;ClickHouse Managed Postgres → ClickHouse&lt;/td&gt;
&lt;td&gt;ClickHouse engine on separate compute and storage within the same platform&lt;/td&gt;
&lt;td&gt;Integrated ClickPipes setup with asynchronous replication and eventual consistency&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Crunchy Bridge → external analytics&lt;/td&gt;
&lt;td&gt;Selected destination's query engine, including ClickHouse&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://docs.crunchybridge.com/how-to/logical-replication" rel="noopener noreferrer"&gt;Logical replication&lt;/a&gt; and an external connector. Consistency depends on the path&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Dedicated PostgreSQL read replica on either service&lt;/td&gt;
&lt;td&gt;PostgreSQL engine on separate replica compute&lt;/td&gt;
&lt;td&gt;Application routes reads. Replication lag affects freshness&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Foreign-table query access&lt;/td&gt;
&lt;td&gt;Remote ClickHouse for supported operations&lt;/td&gt;
&lt;td&gt;ClickHouse's &lt;code&gt;pg_clickhouse&lt;/code&gt; or Bridge's &lt;code&gt;clickhouse_fdw&lt;/code&gt;. Query access differs from replication&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;PostgreSQL read replicas move lag-tolerant reads off the writer while keeping PostgreSQL's query engine. A separate ClickHouse service runs analytical queries on a columnar engine with its own compute, storage, and replicated copy. ClickHouse integrates the replication setup and management within its platform. Bridge can also feed or query an external analytical system.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Replication lag, PostgreSQL source overhead, and query pushdown&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickPipes uses a 60-second default sync interval for its Managed Postgres-to-ClickHouse integration. Measure end-to-end lag separately: scheduling, source activity, transfer, and apply work all affect freshness. Replication runs asynchronously, so the analytical copy stays eventually consistent.&lt;/p&gt;

&lt;p&gt;Updates and deletes use versioned rows and deletion markers, with asynchronous deduplication. &lt;a href="https://www.postgresql.org/docs/current/logicaldecoding-explanation.html" rel="noopener noreferrer"&gt;Replication slots retain WAL&lt;/a&gt; on the source. Decoding, snapshots, and network transfer also consume source resources. Moving analytical queries to ClickHouse separates query execution but leaves that replication work in Postgres. If the application uses TRUNCATE to clear tables, plan how to clear the analytical copy too: &lt;a href="https://clickhouse.com/docs/integrations/clickpipes/postgres/faq" rel="noopener noreferrer"&gt;ClickPipes doesn't replicate that operation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;pg_clickhouse&lt;/code&gt; provides remote query execution and a foreign data wrapper. It doesn't replicate data. Pushdown depends on the &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions/pg_clickhouse/reference" rel="noopener noreferrer"&gt;supported pg_clickhouse operations&lt;/a&gt;. Use EXPLAIN to confirm which operations run in ClickHouse before relying on remote execution to relieve the PostgreSQL workload. Use Postgres for reads that need current transactional state.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Analytics integration costs: replication, compute, and storage&lt;/strong&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Cost component&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres → ClickHouse&lt;/th&gt;
&lt;th&gt;Crunchy Bridge → external analytics&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Source database&lt;/td&gt;
&lt;td&gt;Primary, HA, backups, and any read replicas&lt;/td&gt;
&lt;td&gt;Primary, HA, backups, and any read replicas&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Replication&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;Free replication from Managed Postgres to ClickHouse&lt;/a&gt;, through ClickPipes or WalShadow&lt;/td&gt;
&lt;td&gt;Connector-specific charges. When using ClickPipes, &lt;a href="https://clickhouse.com/docs/products/cloud/reference/billing/clickpipes/clickpipes-for-cdc" rel="noopener noreferrer"&gt;general CDC billing&lt;/a&gt; includes data and connector compute&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Source network&lt;/td&gt;
&lt;td&gt;Applicable transfer charges for the selected route&lt;/td&gt;
&lt;td&gt;Applicable transfer charges for the selected route&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytical service&lt;/td&gt;
&lt;td&gt;Separately provisioned ClickHouse compute and storage on the Cloud bill, including required retention and support&lt;/td&gt;
&lt;td&gt;Selected destination's compute and storage, including required retention and support&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;General ClickPipes connector rates don't apply to the free replication path from Managed Postgres to ClickHouse. Budget analytical capacity separately from the transactional service on either architecture.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Migrating between Crunchy Bridge and ClickHouse Managed Postgres&lt;/strong&gt;
&lt;/h2&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Moving from Crunchy Bridge to ClickHouse Managed Postgres&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;The &lt;a href="https://clickhouse.com/docs/products/managed-postgres/migrations/clickpipes" rel="noopener noreferrer"&gt;ClickPipes migration wizard&lt;/a&gt; migrates data from Crunchy Bridge into the transactional ClickHouse Managed Postgres service, using an initial load and optional CDC. Replication into the ClickHouse analytical service is a separate workflow.&lt;/p&gt;

&lt;p&gt;Before starting, check PostgreSQL versions, extensions, roles, schema objects, replica identity, and network access.&lt;/p&gt;

&lt;p&gt;For the CDC migration path, complete the initial load, stop source writes, let replication catch up, validate the target, pause replication, reset sequences, and switch application connections. Verify application reads and writes before removing source replication slots and retiring the old deployment.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Moving from ClickHouse Managed Postgres to Crunchy Bridge&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Crunchy Bridge supports &lt;a href="https://docs.crunchybridge.com/migrate" rel="noopener noreferrer"&gt;dump/restore and PostgreSQL replication&lt;/a&gt; migration paths. Dump/restore suits a planned write outage. Replication reduces the data-transfer work left for cutover when the source configuration supports it.&lt;/p&gt;

&lt;p&gt;Check roles, extensions, schema objects, and sequence state in this direction too. With replication, stop source writes before final catch-up and validation, then switch connections. Update any ClickHouse-specific provisioning scripts and diagnostic integrations to use Bridge's APIs, CLI, and monitoring tools before retiring the ClickHouse deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Which PostgreSQL service fits an AI agent application?&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;ClickHouse Managed Postgres is the stronger fit for agent and application backends where transactional throughput, integrated diagnostics, or ClickHouse analytics matter most. The Xata acquisition aims to add scale-to-zero and copy-on-write branching. Local NVMe handles the transactional work, selectable HA controls the standby topology, and the ClickHouse integration provides a path to analytical queries on separate resources.&lt;/p&gt;

&lt;p&gt;Crunchy Bridge is the stronger fit when you need storage that grows independently of compute, broad PostgreSQL extension and configuration support, or deployment across AWS, Google Cloud, and Azure. Its API, CLI, forks, and monitoring support application development and operations.&lt;/p&gt;

&lt;p&gt;Match the standby configuration to acceptable data loss and downtime, then compare the complete deployment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Evaluation checklist:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reproduce representative transactions with the required durability settings, schema, connection count, and region.
&lt;/li&gt;
&lt;li&gt;Exercise the agent framework through its pooled or direct endpoint.
&lt;/li&gt;
&lt;li&gt;Check required extensions and index operations on the selected cluster.
&lt;/li&gt;
&lt;li&gt;Include HA, backups, egress, support, and any analytical service in the cost model.
&lt;/li&gt;
&lt;li&gt;Rehearse restores, failover, and application reconnection.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Frequently asked questions about ClickHouse Managed Postgres and Crunchy Bridge&lt;/strong&gt;
&lt;/h2&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Which service fits an AI agent application better?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse Managed Postgres suits agent backends where throughput and integrated tooling are priorities. Crunchy Bridge suits workloads that need flexible storage sizing, broad PostgreSQL tooling, or multi-cloud deployment. Both support state persistence and retrieval. Their storage, workflow, and recovery choices determine fit.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Does PgBouncer transaction pooling work with LangGraph's PostgreSQL saver?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Compatibility depends on the deployed saver, driver, pooler settings, and session requirements. Manually supplied saver connections require &lt;code&gt;autocommit=True&lt;/code&gt; and &lt;code&gt;dict_row&lt;/code&gt;. Test checkpoint writes, resume, and retries through the intended endpoint. Session advisory locks and LISTEN need a session-preserving connection. Sending NOTIFY works in transaction pooling. Bridge also offers session pooling. The connection-compatibility section explains the endpoint choice.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Do both services support pgvector and HNSW indexes?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Yes. ClickHouse Managed Postgres lists pgvector 0.8.6 with IVFFlat and HNSW. Bridge offers pgvector on all clusters and supports HNSW. Confirm the installed extension version, then test tenant filters, recall, and behavior under concurrent writes on the target cluster. Both also provide keyword and BM25 retrieval options.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Does ClickHouse Managed Postgres support MCP?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Yes. The ClickHouse Cloud remote MCP server provides read-only PostgreSQL queries, service metrics, and slow-query tools. Running PostgreSQL queries through MCP requires OAuth. Cloud API-key authentication doesn't work for those queries. These MCP tools let compatible agents explore data and investigate PostgreSQL performance. Application writes need a separate database integration.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How do database branching and forks compare?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse branches and Bridge forks create independent deployments by restoring backups and replaying WAL. Copy-on-write branching is planned for ClickHouse Managed Postgres through the Xata acquisition. Both work for staging, migration rehearsals, and debugging against realistic data. Account for creation time, running-database cost, masking, and cleanup in development-copy workflows.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Which runs faster: ClickHouse Managed Postgres or Crunchy Bridge?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;In the published HA-disabled PostgresBench tests, ClickHouse delivers substantially higher throughput at the larger configuration. The services deliver comparable results at the smaller configuration, with Crunchy Bridge about 5% higher in that test. These results measure pgbench-style transactions. Measure completed checkpoints or tasks, transaction latency, and pool queue time with your application's queries and required HA configuration. Keep three-run means and published HA figures distinct.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Does ClickHouse Managed Postgres cost less than Crunchy Bridge?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;The lower-cost option depends on the resources needed to meet your application's performance and recovery requirements. ClickHouse bundles CPU, memory, and NVMe storage in each VM configuration. Bridge prices compute and storage separately. Compare the pricing models and deployment requirements, including HA, replicas, backup policy, network transfer, support, and analytical capacity.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Can Crunchy Bridge replicate data to ClickHouse for analytics?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Yes. Bridge supports logical replication into external systems, including a connector path to ClickHouse. ClickHouse Managed Postgres integrates that setup within ClickHouse Cloud and provides free replication from its own Postgres service. Analytical compute and storage bill separately. Both paths require attention to freshness and source load.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How does migration from Crunchy Bridge to ClickHouse Managed Postgres work?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;The ClickPipes migration wizard supports Crunchy Bridge sources. For the CDC migration path, complete the initial load, stop source writes, let replication catch up, validate the target, pause replication, reset sequences, and switch application connections. Verify the application before removing source replication slots. The migration section also covers the reverse direction.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>database</category>
      <category>dataengineering</category>
      <category>postgres</category>
    </item>
    <item>
      <title>Neon vs ClickHouse Managed Postgres: AI Agents, Performance, and Pricing</title>
      <dc:creator>Kamal G</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:20:14 +0000</pubDate>
      <link>https://dev.to/database-engineering/neon-vs-clickhouse-managed-postgres-ai-agents-performance-and-pricing-2gkh</link>
      <guid>https://dev.to/database-engineering/neon-vs-clickhouse-managed-postgres-ai-agents-performance-and-pricing-2gkh</guid>
      <description>&lt;p&gt;Neon and ClickHouse Managed Postgres are managed PostgreSQL services for transactional applications and AI agent backends. ClickHouse’s acquisition of Xata aims to add scale-to-zero and copy-on-write branching to ClickHouse Managed Postgres. An agent run can read conversation history, retrieve context, update a checkpoint, and record tool results. Concurrent runs put frequent reads and writes on the database, and accumulated execution data creates demand for analytics.&lt;/p&gt;

&lt;p&gt;This comparison covers transactional performance, retrieval, agent tooling, development workflows, pricing, analytics integration, availability, recovery, and migration across the two services.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;TL;DR&lt;/strong&gt;
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Choose Neon for applications and AI agent platforms where compute autoscaling, scale-to-zero, and fast copy-on-write branching prove decisive.
&lt;/li&gt;
&lt;li&gt;Choose ClickHouse Managed Postgres for performance-critical AI agent and application workloads, agent-assisted database operations, or a native path to ClickHouse analytics. The Xata acquisition aims to add scale-to-zero and copy-on-write branching.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Neon vs ClickHouse Managed Postgres at a glance&lt;/strong&gt;
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Decision factor&lt;/th&gt;
&lt;th&gt;Neon&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Best-fit workloads&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;AI agent and application backends with variable compute demand, idle periods, and frequent branching&lt;/td&gt;
&lt;td&gt;AI agent and application backends with performance-critical workloads, operational tooling, and growing analytical demand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Transactional storage&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/architecture-overview" rel="noopener noreferrer"&gt;Separated compute and storage&lt;/a&gt;, with write-ahead log (WAL) durability&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/overview" rel="noopener noreferrer"&gt;Local NVMe&lt;/a&gt; attached to the Postgres server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Scaling and idle behavior&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/scale-to-zero" rel="noopener noreferrer"&gt;Scale-to-zero&lt;/a&gt; for compute sizes up to 16 compute units (CU). A connected logical-replication subscriber keeps compute active&lt;/td&gt;
&lt;td&gt;Provisioned compute with manual vertical scaling. Storage autoscales on Scale and Enterprise. Scale-to-zero planned through the Xata acquisition&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Branching&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/branching" rel="noopener noreferrer"&gt;Copy-on-write clones&lt;/a&gt; at metadata speed without parent load&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/branching" rel="noopener noreferrer"&gt;Backup-based branches&lt;/a&gt; restored with WAL replay. Independent deployments available in minutes. Copy-on-write branching planned through the Xata acquisition&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Analytics integration&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;ClickHouse through &lt;a href="https://neon.com/docs/guides/logical-replication-clickhouse" rel="noopener noreferrer"&gt;ClickPipes&lt;/a&gt;, or Databricks through &lt;a href="https://neon.com/docs/guides/logical-replication-databricks" rel="noopener noreferrer"&gt;Lakeflow Connect&lt;/a&gt;
&lt;/td&gt;
&lt;td&gt;Native &lt;a href="https://clickhouse.com/docs/products/managed-postgres/sync-to-clickhouse/clickpipes" rel="noopener noreferrer"&gt;ClickPipes integration&lt;/a&gt; with independently scaled ClickHouse analytics in the same cloud platform. pg_clickhouse preserves PostgreSQL query access&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Pricing model&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;CU-hours, storage, history, branches, and egress&lt;/a&gt; metered separately&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;Bundled CPU, RAM, and NVMe&lt;/a&gt;. Native CDC included on AWS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;High availability&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/high-availability" rel="noopener noreferrer"&gt;Multi-AZ storage&lt;/a&gt; without continuously running standby compute&lt;/td&gt;
&lt;td&gt;Automatic failover with &lt;a href="https://clickhouse.com/docs/products/managed-postgres/high-availability.md" rel="noopener noreferrer"&gt;configured standbys&lt;/a&gt;: two for synchronous replication, one for asynchronous replication&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Migration&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Standard PostgreSQL tools for importing data&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/migrations/neon" rel="noopener noreferrer"&gt;Managed ClickPipes migration&lt;/a&gt; for initial load plus change data capture (CDC)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;PostgreSQL versions, cloud availability, and plans&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Neon&lt;/strong&gt; (branded Lakebase Postgres on Neon) supports &lt;a href="https://neon.com/docs/reference/compatibility" rel="noopener noreferrer"&gt;PostgreSQL 14 through 18&lt;/a&gt; across &lt;a href="https://neon.com/docs/introduction/regions" rel="noopener noreferrer"&gt;eight AWS regions&lt;/a&gt;. Azure no longer accepts new projects. The &lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Neon plans&lt;/a&gt; are Free, Launch, and Scale (Business is legacy).&lt;/p&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/overview" rel="noopener noreferrer"&gt;&lt;strong&gt;ClickHouse Managed Postgres&lt;/strong&gt;&lt;/a&gt; is a production-ready managed PostgreSQL service on AWS and GCP within ClickHouse Cloud. It uses local NVMe storage and supports PostgreSQL 17 and 18, with 17 as the &lt;a href="https://clickhouse.com/docs/products/managed-postgres/openapi" rel="noopener noreferrer"&gt;service-creation API&lt;/a&gt; default. The &lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;ClickHouse organization tiers&lt;/a&gt; are Basic, Scale, and Enterprise. See &lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;cloud and region availability&lt;/a&gt; for deployment locations. Xata acquisition plans to integrate scale-to-zero and copy-on-write branching into the service.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;AI agent requirements: state, retrieval, and operations&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Application agents use the database for state and context during execution. Coding and database agents also need interfaces to provision resources and investigate problems.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Agent requirement&lt;/th&gt;
&lt;th&gt;Neon&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Persist runtime state&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;PostgreSQL persistence for sessions, task progress, memory, and application records, with compute managed separately from storage&lt;/td&gt;
&lt;td&gt;PostgreSQL on local NVMe for frequent checkpoint updates, memory writes, and tool-result recording&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Retrieve context&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;pgvector and &lt;a href="https://neon.com/docs/ai/lakebase-search" rel="noopener noreferrer"&gt;Lakebase Search&lt;/a&gt; for vector, BM25 keyword, and hybrid retrieval&lt;/td&gt;
&lt;td&gt;pgvector, vchord, and &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;BM25 retrieval extensions&lt;/a&gt; for vector, keyword, and hybrid retrieval. For larger-scale retrieval, pg_clickhouse pushes vector and search queries to ClickHouse&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Handle concurrent activity&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Pooling, compute autoscaling, and serverless connectivity for changing worker demand&lt;/td&gt;
&lt;td&gt;Bundled transaction pooling for bursts of short-lived workers and provisioned capacity for sustained activity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Provision agent infrastructure&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;APIs, SDKs, and agent tools for creating databases and branches within product workflows&lt;/td&gt;
&lt;td&gt;API, client library, CLI, and Terraform for programmatic provisioning and management&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Investigate database behavior&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Agent tools, MCP, CLI, and SQL diagnostics for inspection and management&lt;/td&gt;
&lt;td&gt;ClickHouse Agents, MCP, &lt;a href="https://github.com/ClickHouse/clickhousectl" rel="noopener noreferrer"&gt;clickhousectl&lt;/a&gt; CLI, Query Insights, logs, and metrics for SQL investigation and tuning assistance&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Analyze accumulated data&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;PostgreSQL reporting and asynchronous CDC paths to ClickHouse or Databricks&lt;/td&gt;
&lt;td&gt;Native asynchronous replication to independently scaled ClickHouse analytics, with PostgreSQL query access through pg_clickhouse&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A Postgres-only deployment works while state, retrieval, and reporting meet the application's targets. Add dedicated analytical (OLAP) capacity when scans and aggregations create persistent contention or need more resources than the transactional service can spare.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Transactional performance and scaling&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Transactional throughput and query latency shape the performance of application and AI agent backends.&lt;/p&gt;

&lt;p&gt;ClickHouse Managed Postgres targets performance-critical transactions. Local NVMe handles ingestion, updates, and vacuum work while reducing tail latency for disk-bound workloads. Neon separates compute from durable storage, so it can adjust or suspend compute independently as demand changes.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Neon storage, autoscaling, and scale-to-zero&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;In &lt;a href="https://neon.com/docs/introduction/architecture-overview" rel="noopener noreferrer"&gt;Neon's storage architecture&lt;/a&gt;, Safekeepers replicate WAL via Paxos, Pageservers materialize pages, and object storage holds history. A cache miss may require fetching a page from the storage layer.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://neon.com/docs/introduction/scale-to-zero" rel="noopener noreferrer"&gt;Scale-to-zero&lt;/a&gt; applies to computes up to 16 CU. &lt;a href="https://neon.com/docs/introduction/compute-lifecycle" rel="noopener noreferrer"&gt;Compute activation&lt;/a&gt; generally takes a few hundred milliseconds, with cold buffers afterward. &lt;a href="https://neon.com/docs/introduction/autoscaling" rel="noopener noreferrer"&gt;Neon autoscaling&lt;/a&gt; adjusts running compute within a configured range spanning at most 8 CU, without a restart.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;ClickHouse Managed Postgres local NVMe and instance scaling&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/overview" rel="noopener noreferrer"&gt;Local NVMe storage&lt;/a&gt; is physically attached to the Postgres server, so reads that miss the cache avoid a network page request. For agent backends, that storage serves cache-miss context reads and frequent memory or checkpoint updates. Commit latency also depends on the selected zero-, one-, or two-standby configuration.&lt;/p&gt;

&lt;p&gt;ClickHouse Managed Postgres uses manual &lt;a href="https://clickhouse.com/docs/products/managed-postgres/scaling" rel="noopener noreferrer"&gt;vertical scaling&lt;/a&gt;: it provisions a replacement standby from backups, replays WAL to catch up, and performs a controlled failover. The switch interrupts connections for roughly 30 seconds. On Scale and Enterprise, &lt;a href="https://clickhouse.com/docs/products/managed-postgres/scaling" rel="noopener noreferrer"&gt;storage autoscaling&lt;/a&gt; replaces the server when usage reaches 90%.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Neon vs ClickHouse Managed Postgres benchmark results&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse Managed Postgres delivered &lt;strong&gt;3.4x Neon's transactional throughput&lt;/strong&gt; in the tested PostgresBench configuration. Both endpoints had 16 vCPUs and 64 GB RAM in AWS us-east-2, with an approximately 500 GB database and provider-default settings. ClickHouse ran without standbys.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;PostgreSQL version&lt;/th&gt;
&lt;th&gt;Run date&lt;/th&gt;
&lt;th&gt;Mean transactions per second&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/ClickHouse/PostgresBench/blob/067b905b1d09dc6439cb3832de38ecaa408f176b/postgres_by_clickhouse/results/postgres_by_clickhouse_16cpu_64gb_34247.json" rel="noopener noreferrer"&gt;ClickHouse Managed Postgres results&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;18.3&lt;/td&gt;
&lt;td&gt;March 18, 2026&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;26,104.81&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/ClickHouse/PostgresBench/blob/067b905b1d09dc6439cb3832de38ecaa408f176b/neon/results/neon_16cpu_64gb_34247.json" rel="noopener noreferrer"&gt;Neon results&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;18.2&lt;/td&gt;
&lt;td&gt;March 11, 2026&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;7,692.91&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://github.com/ClickHouse/PostgresBench/blob/067b905b1d09dc6439cb3832de38ecaa408f176b/README.md" rel="noopener noreferrer"&gt;PostgresBench&lt;/a&gt; measures transactional throughput, not complete agent-run latency. It does this by measuring mean throughput across three 600-second runs per service using pgbench's TPC-B-like workload with 256 clients, 16 threads, and prepared queries.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Postgres performance in Socialpruf's workload&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Socialpruf's Postgres queries ran faster after its production workload moved from Neon to ClickHouse Managed Postgres.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Outcome&lt;/th&gt;
&lt;th&gt;Workload context&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Roughly &lt;a href="https://clickhouse.com/blog/socialpruf" rel="noopener noreferrer"&gt;30% faster Postgres queries overall&lt;/a&gt;
&lt;/td&gt;
&lt;td&gt;Socialpruf's production workload after migration&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/blog/socialpruf" rel="noopener noreferrer"&gt;Selected Postgres queries improved by up to 5x&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Before-and-after observations for selected queries in the same customer workload&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Test steady-state query latency, Neon's first-query latency after suspension, and connection recovery during ClickHouse Managed Postgres scaling separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Agent and developer workflows: retrieval, branching, and operations&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Branching, retrieval, and connection behavior shape how applications and agents use Postgres. APIs and diagnostic tools also let coding and database agents provision resources, inspect data, and investigate performance.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Capability&lt;/th&gt;
&lt;th&gt;Neon&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Branch mechanism&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/branching" rel="noopener noreferrer"&gt;Copy-on-write clone&lt;/a&gt; from current or historical state, without adding load to the parent&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/branching" rel="noopener noreferrer"&gt;Backup restore plus WAL replay&lt;/a&gt; from a selected point in time into an isolated deployment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Branch availability&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Metadata-level creation&lt;/td&gt;
&lt;td&gt;Most branches become available in minutes. Larger databases take longer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Deployment and use case&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Agent platforms with databases per app or workspace. Isolated branches for agent changes, evaluations, and previews&lt;/td&gt;
&lt;td&gt;Independently sized branches for development, staging, agent evaluations, debugging, and recovery&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Branch billing&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Free and Launch include 10 branches per project. Scale includes 25. &lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Excess branches cost \$1.50/branch-month&lt;/a&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;Instance pricing&lt;/a&gt; for each independently sized deployment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Connection pooling&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Transaction-mode &lt;a href="https://neon.com/docs/connect/connection-pooling" rel="noopener noreferrer"&gt;PgBouncer accepts up to 10,000 client connections&lt;/a&gt;
&lt;/td&gt;
&lt;td&gt;Transaction-mode PgBouncer with &lt;a href="https://clickhouse.com/blog/pgbouncer-clickhouse-managed-postgres" rel="noopener noreferrer"&gt;parallel processes&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Shared extensions&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://neon.com/docs/extensions/pg-extensions" rel="noopener noreferrer"&gt;PostGIS, pgvector, and pg_cron&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;PostGIS, pgvector, and pg_cron&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Retrieval capabilities&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;pgvector and &lt;a href="https://neon.com/docs/ai/lakebase-search" rel="noopener noreferrer"&gt;Lakebase Search&lt;/a&gt; for vector, BM25 keyword, and hybrid retrieval&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;Vector and BM25 extensions&lt;/a&gt; for vector, keyword, and hybrid retrieval: pgvector, vchord, vchord_bm25, and pg_tokenizer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Serverless and edge clients&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://neon.com/docs/serverless/serverless-driver" rel="noopener noreferrer"&gt;HTTP/WebSocket serverless driver&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;PostgreSQL drivers and pooling. &lt;a href="https://clickhouse.com/docs/products/managed-postgres/guides/cloudflare-workers" rel="noopener noreferrer"&gt;Cloudflare Workers through Hyperdrive&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;MCP support&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;a href="https://neon.com/docs/ai/neon-mcp-server" rel="noopener noreferrer"&gt;Hosted MCP server&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/cloud/features/ai-ml/remote-mcp" rel="noopener noreferrer"&gt;Remote MCP server&lt;/a&gt; for Managed Postgres&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Agent and automation interfaces&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/blog/give-your-agent-neon-tools" rel="noopener noreferrer"&gt;API, SDK, and agent tools&lt;/a&gt; and CLI&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/blog/clickhouse-agents-managed-postgres" rel="noopener noreferrer"&gt;ClickHouse Agents&lt;/a&gt;, &lt;a href="https://clickhouse.com/blog/clickhousectl-v0-5-0" rel="noopener noreferrer"&gt;clickhousectl&lt;/a&gt;, &lt;a href="https://clickhouse.com/docs/products/managed-postgres/openapi" rel="noopener noreferrer"&gt;OpenAPI&lt;/a&gt;, &lt;a href="https://github.com/ClickHouse/clickhousectl/blob/main/crates/clickhouse-cloud-api/README.md" rel="noopener noreferrer"&gt;Rust API client&lt;/a&gt;, and &lt;a href="https://clickhouse.com/docs/products/managed-postgres/terraform" rel="noopener noreferrer"&gt;Terraform&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Both services support programmatic provisioning for application and agent platforms. ClickHouse Managed Postgres exposes &lt;a href="https://clickhouse.com/docs/products/managed-postgres/openapi" rel="noopener noreferrer"&gt;service creation and connection credentials&lt;/a&gt; through its API. Applications can create &lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;multiple databases and schemas&lt;/a&gt; within each instance using standard PostgreSQL commands. Its &lt;a href="https://clickhouse.com/docs/products/managed-postgres/branching" rel="noopener noreferrer"&gt;backup-based branches&lt;/a&gt; support isolated migration, index, and retrieval testing from a selected point in time, with each deployment sized independently.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Connections and extension compatibility&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Transaction pooling lets concurrent clients share a smaller set of backend connections. ClickHouse Managed Postgres runs multiple PgBouncer processes behind one endpoint, which helps handle bursts of short-lived clients.&lt;/p&gt;

&lt;p&gt;Neon's pooled client connections share backend limits that depend on compute size: for example, 419 at 1 CU and 4,000 at 9+ CU. ClickHouse Managed Postgres defaults to &lt;a href="https://clickhouse.com/docs/products/managed-postgres/migrations/neon" rel="noopener noreferrer"&gt;500 direct connections&lt;/a&gt;, and PgBouncer multiplexes a larger pool of clients onto those backends.&lt;/p&gt;

&lt;p&gt;Both services support protocol-level prepared statements used by database drivers. Use &lt;a href="https://neon.com/docs/connect/connection-pooling" rel="noopener noreferrer"&gt;direct Postgres connections&lt;/a&gt; for SQL-level prepared statements, session-level advisory locks, and tools such as pg_dump.&lt;/p&gt;

&lt;p&gt;Both services work with standard PostgreSQL drivers and ORMs. The &lt;a href="https://neon.com/docs/serverless/serverless-driver" rel="noopener noreferrer"&gt;Neon serverless driver&lt;/a&gt; connects JavaScript and TypeScript workers over HTTP or WebSockets, including serverless and edge environments. HTTP supports individual queries and non-interactive transactions, while WebSockets support sessions and interactive transactions.&lt;/p&gt;

&lt;p&gt;ClickHouse Managed Postgres supports serverless and edge applications, including &lt;a href="https://clickhouse.com/docs/products/managed-postgres/guides/cloudflare-workers" rel="noopener noreferrer"&gt;Cloudflare Workers through Hyperdrive&lt;/a&gt; with node-postgres for reads and writes.&lt;/p&gt;

&lt;p&gt;Neon's pg_cron jobs run only while compute stays active.&lt;/p&gt;

&lt;p&gt;ClickHouse Managed Postgres preinstalls &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions/pg_clickhouse/reference" rel="noopener noreferrer"&gt;pg_clickhouse&lt;/a&gt; for remote ClickHouse execution, includes pg_stat_ch for query-level telemetry, and provides &lt;a href="https://clickhouse.com/docs/products/managed-postgres/faq" rel="noopener noreferrer"&gt;full database superuser access&lt;/a&gt;. Neither product offers host OS access or unrestricted binary installation.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Vector and keyword retrieval&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse Managed Postgres supports vector retrieval through pgvector and vchord, with vchord_bm25 and pg_tokenizer providing BM25 ranking and text processing. These &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions" rel="noopener noreferrer"&gt;retrieval extensions&lt;/a&gt; let teams build semantic and keyword search alongside transactional application data. When retrieval workloads outgrow PostgreSQL capacity, teams can store vectors and search indexes in ClickHouse and query them through PostgreSQL via pg_clickhouse. ClickHouse handles vector and text search at scales beyond what PostgreSQL extensions support, while the application retains its PostgreSQL interface. Semantic matching finds relevant concepts, while keyword ranking retrieves exact names, identifiers, and codes. Teams configure the indexes and combine vector and BM25 rankings in SQL or application code for &lt;a href="https://docs.vectorchord.ai/vectorchord/use-case/hybrid-search.html" rel="noopener noreferrer"&gt;hybrid retrieval&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Neon's &lt;a href="https://neon.com/docs/ai/lakebase-search" rel="noopener noreferrer"&gt;Lakebase Search&lt;/a&gt; adds vector, BM25 keyword, and hybrid retrieval through lakebase_vector, lakebase_text, and lakebase_tokenizer on PostgreSQL 16 and later. Neon also supports pgvector. Copy-on-write branches preserve search indexes without rebuilding them, so teams can compare retrieval changes against independent copies of the same data.&lt;/p&gt;

&lt;p&gt;For either service, evaluate retrieval with the application's embedding dimensions, filters, update rate, recall target, index memory, and latency objective. Use the results to choose the retrieval configuration.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Agent tooling and database diagnostics&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/blog/clickhouse-agents-managed-postgres" rel="noopener noreferrer"&gt;ClickHouse Agents&lt;/a&gt; inspects schemas, runs read-only SELECT queries, and combines service metrics, slow-query patterns, and query plans to recommend tuning changes. These diagnostics help identify whether slow application requests or agent steps stem from retrieval queries, state updates, or database resource pressure. It can also query Postgres and ClickHouse independently and combine the findings.&lt;/p&gt;

&lt;p&gt;ClickHouse Managed Postgres supports external agents and IDEs through the &lt;a href="https://clickhouse.com/docs/products/cloud/features/ai-ml/remote-mcp" rel="noopener noreferrer"&gt;ClickHouse Cloud remote MCP server&lt;/a&gt;. Agents can query PostgreSQL, inspect service metrics, and investigate slow-query patterns. Enable MCP in the service's Connect panel. Postgres SQL queries require OAuth, and all remote MCP tools provide read-only access.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/monitoring/query-insights" rel="noopener noreferrer"&gt;Query Insights&lt;/a&gt; shows slow query patterns, errors, and waits for ClickHouse Managed Postgres in the ClickHouse Cloud console. &lt;a href="https://clickhouse.com/blog/managed-postgres-notifications-observability-backups" rel="noopener noreferrer"&gt;Searchable PostgreSQL logs&lt;/a&gt; support troubleshooting, and &lt;a href="https://clickhouse.com/docs/products/managed-postgres/monitoring/prometheus" rel="noopener noreferrer"&gt;Prometheus-compatible metrics&lt;/a&gt; connect the service to existing monitoring tools. These features diagnose database behavior. Application instrumentation supplies the agent's prompts, model calls, and complete execution traces.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/blog/clickhousectl-v0-5-0" rel="noopener noreferrer"&gt;clickhousectl&lt;/a&gt; gives machine-readable access to Postgres metrics, logs, and slow-query patterns, and supports creating and managing ClickHouse Managed Postgres infrastructure. Its SQL-over-HTTP interface provides read-only access and uses OAuth. Authorized CLI commands, &lt;a href="https://clickhouse.com/docs/products/managed-postgres/openapi" rel="noopener noreferrer"&gt;OpenAPI&lt;/a&gt; calls, and the &lt;a href="https://github.com/ClickHouse/clickhousectl/blob/main/crates/clickhouse-cloud-api/README.md" rel="noopener noreferrer"&gt;Rust Cloud API client&lt;/a&gt; support programmatic service management. SQL writes use PostgreSQL connections. The &lt;a href="https://clickhouse.com/docs/products/managed-postgres/terraform" rel="noopener noreferrer"&gt;Terraform resource&lt;/a&gt; supports declarative provisioning, resizing, HA settings, replicas, and PITR creation, with narrower coverage than the API.&lt;/p&gt;

&lt;p&gt;Neon's &lt;a href="https://neon.com/blog/give-your-agent-neon-tools" rel="noopener noreferrer"&gt;SDK and agent tools&lt;/a&gt; let platforms embed selected database operations into their own agents. A workflow can create a branch and return its connection string in one operation. The &lt;a href="https://neon.com/cli" rel="noopener noreferrer"&gt;Neon CLI&lt;/a&gt; and &lt;a href="https://neon.com/docs/ai/neon-mcp-server" rel="noopener noreferrer"&gt;hosted MCP server&lt;/a&gt; support provisioning, SQL, migrations, and diagnostics. The hosted MCP server targets development and testing. Application agents use normal PostgreSQL connections or the serverless driver for runtime state and retrieval.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Pricing comparison and total deployment cost&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;The full deployment cost includes the Postgres service, its recovery configuration, and any CDC pipeline and analytical service. Neon bills compute hours, storage, history, branches, and egress separately. ClickHouse Managed Postgres bundles CPU, RAM, and NVMe per instance. On AWS, &lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;ClickHouse Managed Postgres&lt;/a&gt; includes native CDC at no additional charge. ClickHouse bills AWS network transfer and backup storage separately, above the provisioned disk capacity. ClickHouse also bills the analytical service separately.&lt;/p&gt;

&lt;p&gt;An always-active agent backend and a fleet of intermittently used agent-built applications have different cost profiles. With Neon, autoscaling and eligible suspension can reduce compute usage during quiet periods. Account for stored data, retained history, and branch allowances alongside active compute.&lt;/p&gt;

&lt;p&gt;For ClickHouse Managed Postgres, size provisioned instances and standbys for workload performance and recovery needs, and budget separately for any analytical service.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Neon pricing model.&lt;/strong&gt; Neon's &lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Free, Launch, and Scale plans&lt;/a&gt; use the following &lt;a href="https://neon.com/pricing" rel="noopener noreferrer"&gt;rates&lt;/a&gt;. &lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Dimension&lt;/th&gt;
&lt;th&gt;Free&lt;/th&gt;
&lt;th&gt;Launch&lt;/th&gt;
&lt;th&gt;Scale&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Compute&lt;/td&gt;
&lt;td&gt;100 CU-hours/project/month included&lt;/td&gt;
&lt;td&gt;\$0.106/CU-hour&lt;/td&gt;
&lt;td&gt;\$0.222/CU-hour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Postgres storage&lt;/td&gt;
&lt;td&gt;1 GB/project included, subject to total Free limits&lt;/td&gt;
&lt;td&gt;\$0.35/GB-month&lt;/td&gt;
&lt;td&gt;\$0.35/GB-month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Included branches/project&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Public egress/project/month&lt;/td&gt;
&lt;td&gt;5 GB&lt;/td&gt;
&lt;td&gt;500 GB, then \$0.10/GB&lt;/td&gt;
&lt;td&gt;500 GB, then \$0.10/GB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;History window&lt;/td&gt;
&lt;td&gt;6 hours, up to 1 GB of changes/project&lt;/td&gt;
&lt;td&gt;Up to 7 days&lt;/td&gt;
&lt;td&gt;Up to 30 days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra paid branches&lt;/td&gt;
&lt;td&gt;Not available beyond 10 included&lt;/td&gt;
&lt;td&gt;\$1.50/branch-month&lt;/td&gt;
&lt;td&gt;\$1.50/branch-month&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;ClickHouse Managed Postgres pricing model.&lt;/strong&gt; Pricing bundles CPU, RAM, and NVMe across &lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;50+ instance configurations&lt;/a&gt;. Sizes range from 1 vCPU, 8 GB RAM, and 59 GB NVMe to 96 vCPUs, 768 GB RAM, and 60 TB NVMe. Use the &lt;a href="https://clickhouse.com/pricing?service=postgres#pricing-calculator" rel="noopener noreferrer"&gt;ClickHouse Managed Postgres pricing calculator&lt;/a&gt; to compare instance sizes and HA configurations.&lt;/p&gt;

&lt;p&gt;ClickHouse Managed Postgres on AWS includes backup storage up to its provisioned disk capacity. Additional backup storage bills at regional ClickHouse Cloud storage rates. Scaling and maintenance can briefly run old and new instances in parallel, producing overlapping charges.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Worked monthly cost comparison: a 100 GB database&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;A 100 GB database runs for a full month in AWS us-east-1, with no read replicas, extra branches, or analytical destination. Public egress stays within Neon's 500 GB allowance.&lt;/p&gt;

&lt;p&gt;Neon runs for 730 active hours at a fixed 1 CU, which provides &lt;a href="https://neon.com/docs/manage/computes" rel="noopener noreferrer"&gt;4 GB RAM&lt;/a&gt;. The ClickHouse configuration uses an ARM c6gd.large instance.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Configuration or cost&lt;/th&gt;
&lt;th&gt;Neon Launch&lt;/th&gt;
&lt;th&gt;Neon Scale&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres Scale&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Primary compute&lt;/td&gt;
&lt;td&gt;1 CU / 4 GB RAM&lt;/td&gt;
&lt;td&gt;1 CU / 4 GB RAM&lt;/td&gt;
&lt;td&gt;2 vCPUs / 4 GiB RAM, ARM c6gd.large&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage&lt;/td&gt;
&lt;td&gt;100 GB&lt;/td&gt;
&lt;td&gt;100 GB&lt;/td&gt;
&lt;td&gt;118 GiB local NVMe included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Operating time&lt;/td&gt;
&lt;td&gt;730 active hours&lt;/td&gt;
&lt;td&gt;730 active hours&lt;/td&gt;
&lt;td&gt;Full-month calculator estimate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Availability&lt;/td&gt;
&lt;td&gt;Multi-AZ storage, no standby compute&lt;/td&gt;
&lt;td&gt;Multi-AZ storage, no standby compute&lt;/td&gt;
&lt;td&gt;Primary only, 0 standbys&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compute&lt;/td&gt;
&lt;td&gt;\$77.38: 730 x \$0.106&lt;/td&gt;
&lt;td&gt;\$162.06: 730 x \$0.222&lt;/td&gt;
&lt;td&gt;\$95.31, including storage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage charge&lt;/td&gt;
&lt;td&gt;\$35.00: 100 x \$0.35&lt;/td&gt;
&lt;td&gt;\$35.00: 100 x \$0.35&lt;/td&gt;
&lt;td&gt;Included above&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Compute and storage subtotal&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;\$112.38/month&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;\$197.06/month&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;\$95.31/month&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The ARM c6gd.large primary with no standbys has an &lt;a href="https://clickhouse.com/pricing?service=postgres&amp;amp;pg.plan=scale&amp;amp;pg.provider=aws&amp;amp;pg.profile=cpu&amp;amp;pg.architecture=arm&amp;amp;pg.standby=0&amp;amp;pg.region=us-east-1&amp;amp;pg.computeSize=c6gd.large#pricing-calculator" rel="noopener noreferrer"&gt;undiscounted monthly estimate of \$95.31&lt;/a&gt;. With two synchronous standbys, the same instance configuration has an &lt;a href="https://clickhouse.com/pricing?service=postgres&amp;amp;pg.plan=scale&amp;amp;pg.provider=aws&amp;amp;pg.profile=cpu&amp;amp;pg.architecture=arm&amp;amp;pg.standby=2&amp;amp;pg.region=us-east-1&amp;amp;pg.computeSize=c6gd.large#pricing-calculator" rel="noopener noreferrer"&gt;undiscounted monthly estimate of \$285.93&lt;/a&gt;. Neon uses multi-AZ storage without dedicated standby compute. Match the availability topology to the application's recovery objectives when comparing production deployments.&lt;/p&gt;

&lt;p&gt;Neon restore history adds \$0.20/GB-month on Launch and Scale. These subtotals exclude it. The ClickHouse Managed Postgres subtotal excludes AWS network transfer and excess backup-storage charges that begin on November 9, 2026. Analytical compute carries a separate cost for either source. Each configuration provides enough storage for the database. Size compute separately for the application's latency and throughput targets.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;CDC and analytics costs&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Postgres workloads feeding ClickHouse analytics use source compute, CDC, network transfer, and analytical capacity.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Cost component&lt;/th&gt;
&lt;th&gt;Neon → ClickHouse&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres → ClickHouse&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Source compute&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;CU-hour charges continue while a connected replication subscriber prevents suspension&lt;/td&gt;
&lt;td&gt;Provisioned instance charges cover CPU, RAM, and local NVMe&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;CDC charges&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/cloud/reference/billing/clickpipes/clickpipes-for-cdc" rel="noopener noreferrer"&gt;Generic ClickPipes CDC&lt;/a&gt;: \$0.10/GB initial load, \$0.20/GB ongoing changes, plus compute starting at \$0.10/hour on ClickHouse Basic or \$0.20/hour on ClickHouse Scale and Enterprise&lt;/td&gt;
&lt;td&gt;Native CDC included at no additional charge on AWS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Source network egress&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Public egress per project&lt;/a&gt;: 5 GB/month on Free, 500 GB/month on Launch and Scale, then \$0.10/GB on those paid plans&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;ClickHouse Cloud transfer rates&lt;/a&gt; apply on AWS from November 9, 2026. Keep services in the same region to avoid egress costs.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Analytical capacity&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Separately provisioned ClickHouse compute and storage&lt;/td&gt;
&lt;td&gt;Separately provisioned ClickHouse compute and storage&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;ClickHouse analytics bills &lt;a href="https://clickhouse.com/pricing" rel="noopener noreferrer"&gt;separately&lt;/a&gt; and appears alongside ClickHouse Managed Postgres on a consolidated ClickHouse Cloud bill. Include the required HA configuration, retained history, read replicas, and branches in the full deployment cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Native ClickHouse integration and Neon's analytics options&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Teams analyze recorded agent runs, tool outcomes, evaluation results, latency, token usage, and costs. Application instrumentation supplies the traces and relationships among model and tool calls.&lt;/p&gt;

&lt;p&gt;Application agents also use analytical tools to query historical events and business aggregates when answering questions or completing tasks.&lt;/p&gt;

&lt;p&gt;Those scans and aggregations compete with checkpoint updates, retrieval requests, and other application transactions for CPU, memory, and I/O. Independent analytical capacity lets those workloads grow while Postgres maintains the transactional state.&lt;/p&gt;

&lt;p&gt;With ClickHouse Managed Postgres, PostgreSQL remains the transactional system of record. A separately provisioned ClickHouse service runs analytical queries on its own CPU, memory, storage, and caches. Teams scale analytical capacity independently while managing both services through the ClickHouse Cloud control plane and a consolidated bill.&lt;/p&gt;

&lt;p&gt;Socialpruf &lt;a href="https://clickhouse.com/blog/socialpruf" rel="noopener noreferrer"&gt;moved dashboard analytics to ClickHouse&lt;/a&gt; before migrating its transactional Postgres. Its dashboards took 1 to 3 seconds to load before offload. After offload, ClickHouse aggregated millions of rows in milliseconds. The dashboard and aggregation timings measure different operations within Socialpruf's workload.&lt;/p&gt;

&lt;p&gt;Neon can feed ClickHouse or Databricks analytics through CDC connectors while keeping transactional Postgres on Neon.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Analytics path&lt;/th&gt;
&lt;th&gt;Integration and setup&lt;/th&gt;
&lt;th&gt;Destination and operating model&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ClickHouse Managed Postgres → ClickHouse&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/sync-to-clickhouse/clickpipes" rel="noopener noreferrer"&gt;Native ClickPipes integration&lt;/a&gt;. Logical replication enabled, &lt;a href="https://clickhouse.com/docs/integrations/clickpipes/postgres/source/managed-postgres" rel="noopener noreferrer"&gt;network access allowed&lt;/a&gt; by default, and source connection pre-filled&lt;/td&gt;
&lt;td&gt;Separately provisioned ClickHouse analytical service with independent compute and storage. Both services share the ClickHouse Cloud control plane and bill&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Neon → ClickHouse&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/guides/logical-replication-clickhouse" rel="noopener noreferrer"&gt;ClickPipes&lt;/a&gt;, after enabling logical replication and preparing the source&lt;/td&gt;
&lt;td&gt;Separately provisioned ClickHouse analytical service within ClickHouse Cloud. Transactional Postgres stays on Neon&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Neon → Databricks&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/guides/logical-replication-databricks" rel="noopener noreferrer"&gt;Lakeflow Connect PostgreSQL connector&lt;/a&gt;, currently in public preview&lt;/td&gt;
&lt;td&gt;Delta tables in a separate Databricks analytics environment. Transactional Postgres stays on Neon&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;ClickHouse Managed Postgres source setup.&lt;/strong&gt; For manual setup, allow ClickPipes' static IPs in any configured IP filters and provide the instance CA bundle for verified TLS. Connect directly to Postgres rather than through PgBouncer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Neon to ClickHouse via ClickPipes.&lt;/strong&gt; Enable &lt;a href="https://neon.com/docs/guides/logical-replication-neon" rel="noopener noreferrer"&gt;logical replication&lt;/a&gt; for the Neon project, which changes the project-wide WAL setting and restarts computes. Configure permissions, a publication, and direct rather than pooled connectivity, then &lt;a href="https://neon.com/docs/guides/logical-replication-clickhouse" rel="noopener noreferrer"&gt;create the ClickPipe&lt;/a&gt; in ClickHouse Cloud.&lt;/p&gt;

&lt;p&gt;A connected subscriber prevents scale-to-zero. Inactive replication slots without progress can be removed after approximately 40 hours. Neon defaults to 10 replication slots and 10 WAL senders. Neon-to-ClickHouse replication uses generic &lt;a href="https://clickhouse.com/docs/products/cloud/reference/billing/clickpipes/clickpipes-for-cdc" rel="noopener noreferrer"&gt;ClickPipes CDC pricing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lakebase within Databricks.&lt;/strong&gt; Lakebase deployed within Databricks provides &lt;a href="https://docs.databricks.com/aws/en/oltp/projects/lakehouse-integrations" rel="noopener noreferrer"&gt;native lakehouse integration&lt;/a&gt;, including Unity Catalog registration and lakehouse workflows. It runs as a distinct deployment from a Neon-hosted project.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Query ClickHouse through PostgreSQL with pg_clickhouse&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;With configured foreign tables, the &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions/pg_clickhouse/reference" rel="noopener noreferrer"&gt;pg_clickhouse extension&lt;/a&gt; lets applications, ORMs, and dashboards query ClickHouse analytical data through their PostgreSQL connection. ClickPipes moves the data, and pg_clickhouse pushes supported filters, aggregations, and joins to the ClickHouse service. Unsupported operations and parts of mixed plans still execute in Postgres. The two services maintain separate transaction boundaries.&lt;/p&gt;

&lt;p&gt;An agent tool can use this PostgreSQL interface to query historical usage, aggregate business records, or retrieve evaluation summaries from ClickHouse while its current task state stays in Postgres. Read current committed state from Postgres when the tool can't tolerate replication lag.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Replication freshness and source load&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickPipes replication runs asynchronously, so the analytical copy is eventually consistent and can lag committed Postgres changes. The Postgres source handles logical decoding, initial snapshots, &lt;a href="https://www.postgresql.org/docs/current/logicaldecoding-explanation.html" rel="noopener noreferrer"&gt;WAL retention&lt;/a&gt;, and network transfer. &lt;a href="https://clickhouse.com/docs/integrations/clickpipes/postgres/faq" rel="noopener noreferrer"&gt;Replicated delete events&lt;/a&gt; also propagate source deletions to ClickHouse. Retaining analytical data longer requires explicit configuration.&lt;/p&gt;

&lt;p&gt;Monitor replication slots and plan how to resynchronize data after an interruption, especially if the source or destination can idle.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;High availability, read replicas, and recovery&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;For AI agent and application backends, recovery determines which acknowledged writes survive a failure and how quickly clients reconnect. Point-in-time recovery (PITR) restores an earlier database state after an erroneous change. Application code handles reconnects and retries. Database recovery doesn't resume an agent workflow or undo actions in external tools.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Recovery capability&lt;/th&gt;
&lt;th&gt;Neon&lt;/th&gt;
&lt;th&gt;ClickHouse Managed Postgres&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Availability architecture&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/high-availability" rel="noopener noreferrer"&gt;Multi-AZ storage&lt;/a&gt; on all plans. Compute runs in one AZ&lt;/td&gt;
&lt;td&gt;Primary with zero, one, or two &lt;a href="https://clickhouse.com/docs/products/managed-postgres/high-availability.md" rel="noopener noreferrer"&gt;HA standbys&lt;/a&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Standby replication&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Storage durability operates without continuously running standby compute&lt;/td&gt;
&lt;td&gt;One standby uses asynchronous replication. Two use synchronous replication, with at least one standby acknowledging each commit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Failover&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Compute recovery depends on the failure type&lt;/td&gt;
&lt;td&gt;Automatic with configured standbys. Zero standbys provide no continuously maintained failover target. One asynchronous standby may miss recent commits if the primary fails&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Read replicas&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/read-replicas" rel="noopener noreferrer"&gt;Read-only computes&lt;/a&gt; share the primary's durable storage with asynchronous replication and no hard lag SLO. Free permits up to three per project&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/read-replicas.md" rel="noopener noreferrer"&gt;Read replicas&lt;/a&gt; on Scale offload read-heavy application and reporting queries to independent database copies with separate endpoints. HA standbys can't serve reads&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Point-in-time recovery (PITR)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/postgres/backup-restore/branch-restore" rel="noopener noreferrer"&gt;Restores a root branch in place&lt;/a&gt;, preserving its previous state in a backup branch. Child branches don't support instant restore&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://clickhouse.com/docs/products/managed-postgres/backup-and-restore" rel="noopener noreferrer"&gt;Daily full backup plus archived WAL&lt;/a&gt; restores into a new instance, leaving the original available&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Recovery retention&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Free: 6 hours, subject to 1 GB of changes per project. Launch: up to 7 days. Scale: up to 30 days&lt;/td&gt;
&lt;td&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;Basic: one day. Scale and Enterprise: seven days&lt;/a&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Neon compute recovery.&lt;/strong&gt; Typical recovery takes seconds for certain failures, 1 to 2 minutes for node failure, and 1 to 10 minutes for AZ failure. An unresponsive compute endpoint triggers reattachment after five minutes. These timings depend on the failure and don't constitute a single recovery-time guarantee. Applications need reconnect logic, and cache and session state may be lost.&lt;/p&gt;

&lt;p&gt;In May 2025, a &lt;a href="https://neon.com/blog/postmortem-delayed-start-compute-operations" rel="noopener noreferrer"&gt;Neon control-plane failure&lt;/a&gt; in us-east-1 blocked new compute starts and activations for hours while already-running databases continued operating.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read-replica freshness.&lt;/strong&gt; For ClickHouse Managed Postgres read replicas, WAL ships by default when a 16 MB segment fills or 60 seconds pass, whichever comes first. This interval doesn't guarantee when changes become queryable. Neither service's replica architecture guarantees &lt;a href="https://www.postgresql.org/docs/current/warm-standby.html" rel="noopener noreferrer"&gt;read-your-writes at a replica endpoint&lt;/a&gt;. Support can &lt;a href="https://clickhouse.com/docs/products/managed-postgres/read-replicas" rel="noopener noreferrer"&gt;configure lower-lag replicas&lt;/a&gt; by tuning WAL shipping or enabling streaming replication. Streaming adds CPU and network load on the primary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Restore timing.&lt;/strong&gt; Neon's root-branch restores typically take a few seconds, with no fixed completion time.&lt;/p&gt;

&lt;p&gt;Set a recovery point objective (RPO) for the acceptable data-loss window and a recovery time objective (RTO) for acceptable downtime. Match the production configuration to those targets.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Migrating from Neon to ClickHouse Managed Postgres&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Use &lt;a href="https://clickhouse.com/docs/products/managed-postgres/migrations/neon" rel="noopener noreferrer"&gt;ClickPipes migration&lt;/a&gt; to move from Neon to ClickHouse Managed Postgres through an initial load, ongoing CDC replication, and a controlled cutover.&lt;/p&gt;

&lt;p&gt;Standard &lt;a href="https://www.postgresql.org/docs/current/app-pgdump.html" rel="noopener noreferrer"&gt;pg_dump/pg_restore&lt;/a&gt; supports a one-time database-object transfer in both directions. It doesn't copy roles, replication slots, server settings, tablespaces, or runtime statistics.&lt;/p&gt;

&lt;p&gt;Socialpruf &lt;a href="https://clickhouse.com/blog/neon-to-clickhouse-managed-postgres" rel="noopener noreferrer"&gt;migrated 0.5 TB&lt;/a&gt; from Neon to ClickHouse Managed Postgres in a few hours using ClickPipes. The team kept both databases synchronized for a week of testing before completing its production cutover.&lt;/p&gt;

&lt;p&gt;Migration and cutover checklist:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Confirm the target PostgreSQL version, required extensions, and direct versus pooled connection behavior.
&lt;/li&gt;
&lt;li&gt;Prepare the new connection settings and replace the Neon Serverless Driver if the application uses it.
&lt;/li&gt;
&lt;li&gt;Adapt branch automation for independent, backup-restored deployments and review pg_clickhouse queries.
&lt;/li&gt;
&lt;li&gt;After the initial load, stop writes, let CDC catch up, validate the replicated data, and switch application connectivity.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For migration from ClickHouse Managed Postgres to Neon, follow the &lt;a href="https://neon.com/docs/import/migrate-from-postgres" rel="noopener noreferrer"&gt;Neon migration guide&lt;/a&gt; using pg_dump/pg_restore and update the connection settings. Review vendor-specific drivers if the application uses them.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;When to choose Neon or ClickHouse Managed Postgres&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Workload performance.&lt;/strong&gt; Neon suits AI agent and application backends with changing compute demand. ClickHouse Managed Postgres targets performance-critical workloads on local NVMe, where consistent disk-bound latency matters more than elastic scaling.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Context retrieval.&lt;/strong&gt; Both services combine PostgreSQL data with vector and keyword retrieval. ClickHouse Managed Postgres also supports shifting retrieval to ClickHouse through pg_clickhouse when workloads outgrow PostgreSQL. Compare their available indexes, filtering behavior, memory needs, and results on your application's data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Provisioning and branches.&lt;/strong&gt; Both support programmatic provisioning and isolated database environments. Neon creates copy-on-write branches at metadata speed for frequent environment creation. ClickHouse Managed Postgres creates API-provisioned services and independently sized branches for testing, validation, and recovery. Copy-on-write branching is planned through the Xata acquisition.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Agent operations.&lt;/strong&gt; Both provide MCP integration, APIs, client libraries, and CLIs. ClickHouse Agents adds SQL and performance investigation across Postgres and ClickHouse. Terraform supports declarative provisioning.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Durability and recovery.&lt;/strong&gt; ClickHouse Managed Postgres provides automatic failover with configured standbys, including synchronous replication with two standbys. Neon provides multi-AZ storage without continuously running standby compute. Match the configuration to your durability and recovery requirements.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Analytics integration.&lt;/strong&gt; ClickHouse Managed Postgres pairs transactional PostgreSQL with independently scaled ClickHouse analytics in one managed platform, with analytical data accessible through PostgreSQL. Neon can remain the transactional backend while feeding ClickHouse or Databricks through CDC.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Complete cost.&lt;/strong&gt; Neon's autoscaling and eligible idle periods reduce compute usage for variable traffic, but a connected CDC subscriber keeps compute active. ClickHouse Managed Postgres bundles CPU, RAM, and NVMe and includes native CDC at no additional charge on AWS.&lt;/p&gt;

&lt;p&gt;Choose ClickHouse Managed Postgres for performance-critical AI agent and application backends, with agent-assisted database operations and a native path to independently scaled ClickHouse analytics. The Xata acquisition aims to add scale-to-zero and copy-on-write branching. Choose Neon for applications and AI agent platforms where compute autoscaling, scale-to-zero, and fast copy-on-write branching prove decisive today.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Frequently asked questions about Neon and ClickHouse Managed Postgres&lt;/strong&gt;
&lt;/h2&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How do Neon and ClickHouse Managed Postgres support AI agent workloads?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Both services provide PostgreSQL persistence for agent state and context retrieval, plus MCP integration and programmatic provisioning. Neon adds compute autoscaling and fast copy-on-write branches for agent applications and platforms. ClickHouse Managed Postgres combines local NVMe, retrieval extensions, agent-assisted database investigation, and native ClickHouse analytics for execution data and analytical tools.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;What vector and keyword retrieval options does each service provide?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse Managed Postgres supports vector and BM25 keyword retrieval through pgvector, vchord, vchord_bm25, and pg_tokenizer. Teams combine rankings for hybrid retrieval. Neon supports pgvector and Lakebase Search for vector, BM25 keyword, and hybrid retrieval. Both keep retrieval alongside PostgreSQL application data.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Does ClickHouse Managed Postgres outperform Neon?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;ClickHouse Managed Postgres delivered &lt;strong&gt;3.4x Neon's transactional throughput&lt;/strong&gt; in the tested PostgresBench configuration. Both endpoints had 16 vCPUs and 64 GB RAM in AWS us-east-2, with provider-default settings. ClickHouse ran without standbys and maintains the benchmark.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How does Neon pricing compare with ClickHouse Managed Postgres?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Neon meters CU-hours, storage, history, branches, and egress separately. ClickHouse Managed Postgres &lt;a href="https://clickhouse.com/docs/products/managed-postgres/pricing" rel="noopener noreferrer"&gt;bundles CPU, RAM, and local NVMe&lt;/a&gt; per instance and includes native CDC at no additional charge on AWS. Include HA, CDC, analytical capacity, and transfer costs in the deployment budget.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How does database branching differ between Neon and ClickHouse Managed Postgres?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Neon creates &lt;a href="https://neon.com/docs/introduction/branching" rel="noopener noreferrer"&gt;copy-on-write branches&lt;/a&gt; at metadata speed without adding load to the parent. ClickHouse Managed Postgres creates &lt;a href="https://clickhouse.com/docs/products/managed-postgres/branching" rel="noopener noreferrer"&gt;independently sized deployments&lt;/a&gt; from backups and WAL replay, usually in minutes. Larger databases take longer. Copy-on-write branching is planned through the Xata acquisition. Neon's model supports frequent isolated copies for agent changes, evaluations, and previews. ClickHouse Managed Postgres branches support isolated staging, agent evaluations, migration testing, and recovery.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Can teams add ClickHouse analytics while keeping Postgres on Neon?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Yes. &lt;a href="https://neon.com/docs/guides/logical-replication-clickhouse" rel="noopener noreferrer"&gt;ClickPipes replicates Neon data&lt;/a&gt; into a separately provisioned ClickHouse analytical service while transactional Postgres stays on Neon. Moving Postgres to ClickHouse Managed Postgres brings both services under one ClickHouse Cloud control plane and consolidated bill, with native CDC included at no additional charge on AWS. Both paths use asynchronous replication.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Does Neon include native Databricks analytics?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Neon-hosted projects use &lt;a href="https://neon.com/docs/guides/logical-replication-databricks" rel="noopener noreferrer"&gt;Lakeflow Connect&lt;/a&gt; to replicate Postgres changes into Delta tables in a separate Databricks analytics environment. The PostgreSQL connector currently runs in public preview. &lt;a href="https://docs.databricks.com/aws/en/oltp/projects/lakehouse-integrations" rel="noopener noreferrer"&gt;Lakebase within Databricks&lt;/a&gt; provides native Unity Catalog and lakehouse integration as a distinct deployment from a Neon-hosted project. Lakebase Search provides vector and keyword retrieval within Neon and differs from the Databricks analytical environment.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Can applications query ClickHouse through a PostgreSQL connection?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Yes. With configured foreign tables, &lt;a href="https://clickhouse.com/docs/products/managed-postgres/extensions/pg_clickhouse/reference" rel="noopener noreferrer"&gt;pg_clickhouse&lt;/a&gt; lets applications, agent tools, ORMs, and dashboards query ClickHouse through a PostgreSQL connection. It pushes supported filters, aggregations, and joins to a separately provisioned ClickHouse service with its own compute, storage, and metering. Unsupported operations and parts of mixed plans still run in Postgres. The services retain separate transaction boundaries.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Can Neon scale to zero with an active CDC subscriber?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;A connected &lt;a href="https://neon.com/docs/guides/logical-replication-neon" rel="noopener noreferrer"&gt;logical-replication subscriber&lt;/a&gt; keeps the Neon source compute active and prevents scale-to-zero. Source CU-hour charges continue while the subscriber stays connected.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How do teams migrate from Neon to ClickHouse Managed Postgres?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/docs/products/managed-postgres/migrations/neon" rel="noopener noreferrer"&gt;Managed ClickPipes migration&lt;/a&gt; performs an initial load and ongoing CDC. Before cutover, check migration compatibility, including PostgreSQL versions, extensions, drivers, pooling, and branch automation. After the initial load, teams stop writes, let CDC catch up, validate the replicated data, and switch application connections. Transfers back to Neon use standard PostgreSQL dump and restore tools and updated connection settings, following the &lt;a href="https://neon.com/docs/import/migrate-from-postgres" rel="noopener noreferrer"&gt;Neon migration guide&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>database</category>
      <category>clickhouse</category>
      <category>dataengineering</category>
      <category>ai</category>
    </item>
    <item>
      <title>How to read PostgreSQL EXPLAIN output</title>
      <dc:creator>Kamal G</dc:creator>
      <pubDate>Wed, 04 Nov 2026 02:58:21 +0000</pubDate>
      <link>https://dev.to/database-engineering/how-to-read-postgresql-explain-output-4bhd</link>
      <guid>https://dev.to/database-engineering/how-to-read-postgresql-explain-output-4bhd</guid>
      <description>&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Read the plan tree from leaves to root; cost, rows, and width are estimates, not measurements.
&lt;/li&gt;
&lt;li&gt;Start with plain &lt;code&gt;EXPLAIN&lt;/code&gt; when execution consequences are unknown. &lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt; executes the statement and adds observed time, rows, and loops.
&lt;/li&gt;
&lt;li&gt;Before diagnosing a row-count mismatch, check for early stops and loops. A substantial mismatch in a node that ran to completion warrants investigation.
&lt;/li&gt;
&lt;li&gt;One plan does not prove a cause: check statistics, parameters, and representative conditions. Rollback does not undo &lt;code&gt;nextval&lt;/code&gt; sequence advances or resource consumption.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What does a PostgreSQL &lt;code&gt;EXPLAIN&lt;/code&gt; plan show?
&lt;/h2&gt;

&lt;p&gt;A PostgreSQL &lt;code&gt;EXPLAIN&lt;/code&gt; plan shows the planner's chosen strategy as a tree of nodes, each representing one retrieval or processing step, along with estimated cost, row count, and row width for every node.&lt;/p&gt;

&lt;p&gt;Scans sit at the leaves. Joins, sorts, and aggregates appear above them. In text output, the final result is at the top, indented -&amp;gt; lines mark child nodes, and Filter and Index Cond describe nodes rather than forming new ones. Follow rows from leaves to root, but execution order depends on the algorithm: a nested loop rescans its inner child for each outer row, while a hash join builds before probing.&lt;/p&gt;

&lt;p&gt;Start with a plan that has just one node. The documented &lt;a href="https://www.postgresql.org/docs/18/using-explain.html" rel="noopener noreferrer"&gt;sequential scan of the regression-test table tenk1&lt;/a&gt; in PostgreSQL 18 produces:&lt;br&gt;&lt;br&gt;
Seq Scan on tenk1 (cost=0.00..445.00 rows=10000 width=244)&lt;br&gt;&lt;br&gt;
Four fields appear: &lt;strong&gt;0.00&lt;/strong&gt; startup cost, &lt;strong&gt;445.00&lt;/strong&gt; total cost, &lt;strong&gt;10,000&lt;/strong&gt; estimated rows, and &lt;strong&gt;244&lt;/strong&gt; bytes average row width. These figures come from the documented PostgreSQL regression-test database example. They weren't measured in a separate run.&lt;/p&gt;

&lt;p&gt;Run &lt;code&gt;EXPLAIN&lt;/code&gt; (without &lt;code&gt;ANALYZE&lt;/code&gt;) to inspect the tree and fields without executing the statement's planned operations.&lt;/p&gt;

&lt;h2&gt;
  
  
  What do cost, rows, and width actually mean?
&lt;/h2&gt;

&lt;p&gt;Cost, rows, and width are the planner's predictions based on statistics and configurable cost parameters. They aren't measurements of elapsed time, actual I/O, or observed result size.&lt;/p&gt;

&lt;p&gt;The two cost values use a configurable scale, with parameters including &lt;a href="https://www.postgresql.org/docs/current/runtime-config-query.html" rel="noopener noreferrer"&gt;seq_page_cost&lt;/a&gt; (default 1.0) and random_page_cost (default 4.0). An upper node's cost includes its children's costs, so summing a branch double-counts modeled work. Costs compare modeled work under consistent assumptions. They're neither milliseconds nor portable benchmarks across servers, datasets, or PostgreSQL versions.&lt;/p&gt;

&lt;p&gt;Row and width estimates depend on sampled statistics. The planner uses &lt;a href="https://www.postgresql.org/docs/current/planner-stats.html" rel="noopener noreferrer"&gt;pg_class&lt;/a&gt; page and row counts and pg_statistic selectivity information. &lt;code&gt;ANALYZE&lt;/code&gt; gathers these by sampling, so estimates remain approximate even after fresh analysis.&lt;/p&gt;

&lt;p&gt;To move from predictions to observations, compare rows= with actual rows in an analyzed plan to find where estimates first diverge. Check completion and loops before concluding the estimate is wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does &lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt; add, and what should you watch out for?
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt; executes the statement and reports actual time (startup and total, in milliseconds), actual rows, and loops alongside the original estimates.&lt;/p&gt;

&lt;p&gt;When a node runs more than once (such as the inner side of a nested loop), the reported time and rows are &lt;a href="https://www.postgresql.org/docs/18/using-explain.html" rel="noopener noreferrer"&gt;per-execution averages&lt;/a&gt;. Multiply these averages by loops to estimate accumulated node time and rows, not the statement's elapsed time.&lt;/p&gt;

&lt;p&gt;In the documented &lt;a href="https://www.postgresql.org/docs/18/using-explain.html" rel="noopener noreferrer"&gt;LIMIT 2 query against tenk1&lt;/a&gt;, the child Index Scan estimates 10 rows if run to completion, but the parent Limit stops after obtaining 2:&lt;br&gt;&lt;br&gt;
Limit (cost=0.29..14.33 rows=2 width=244) (actual time=0.051..0.071 rows=2.00 loops=1)&lt;br&gt;&lt;br&gt;
  -&amp;gt; Index Scan using tenk1_unique2 on tenk1 (cost=0.29..70.50 rows=10 width=244) (actual time=0.051..0.070 rows=2.00 loops=1)&lt;br&gt;&lt;br&gt;
(Filter conditions and summary lines omitted from the documented excerpt.)&lt;/p&gt;

&lt;p&gt;PostgreSQL &lt;a href="https://www.postgresql.org/docs/18/using-explain.html" rel="noopener noreferrer"&gt;explicitly says this isn't an estimation error&lt;/a&gt;. Before diagnosing a row-count mismatch, check whether a parent node such as Limit stopped the child early.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt; performs &lt;code&gt;INSERT&lt;/code&gt;, &lt;code&gt;UPDATE&lt;/code&gt;, or &lt;code&gt;DELETE&lt;/code&gt; with ordinary side effects. The &lt;a href="https://www.postgresql.org/docs/current/sql-explain.html" rel="noopener noreferrer"&gt;documentation recommends wrapping in a transaction and rolling back&lt;/a&gt;, but &lt;a href="https://www.postgresql.org/docs/current/functions-sequence.html" rel="noopener noreferrer"&gt;sequence values from &lt;code&gt;nextval&lt;/code&gt; aren't reclaimed after rollback&lt;/a&gt;, and resource consumption persists. Use plain EXPLAIN first when execution consequences are unknown.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does a row-count mismatch actually matter?
&lt;/h2&gt;

&lt;p&gt;A substantial mismatch in a node that ran to completion warrants investigation, but one plan can't establish whether the mismatch changed the plan choice or caused the slow query.&lt;/p&gt;

&lt;p&gt;Correlated predicates, skewed distributions, and insufficient distinct-value estimates can produce genuine errors that &lt;a href="https://www.postgresql.org/docs/current/planner-stats.html" rel="noopener noreferrer"&gt;fresh ANALYZE alone may not fix&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;A distinct-value estimate isn't itself an EXPLAIN node-row count. GoCardless &lt;a href="https://gocardless.com/blog/debugging-the-postgres-query-planner" rel="noopener noreferrer"&gt;reported (engineering blog, last edited September 2022)&lt;/a&gt; that PostgreSQL estimated approximately 25,000 distinct payout_id values, while the team's approximate data counts implied almost 3.5 million. The author reports that the distinct-value estimate became stable after the team raised a statistics target to 5,000. Server version, hardware, and hosting aren't established in the account. Check what the statistics represent. The value 5,000 isn't a universal target.&lt;/p&gt;

&lt;p&gt;When investigating a mismatch in a node that ran to completion:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Establish execution context: exact SQL, parameters, and PostgreSQL version.
&lt;/li&gt;
&lt;li&gt;Find where estimated and actual rows first diverge.
&lt;/li&gt;
&lt;li&gt;Inspect &lt;a href="https://www.postgresql.org/docs/current/planner-stats.html" rel="noopener noreferrer"&gt;pg_stats&lt;/a&gt; for the relevant columns (most_common_vals, histogram_bounds, n_distinct).
&lt;/li&gt;
&lt;li&gt;Test a targeted remedy and verify under representative conditions.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What are the limits of one &lt;code&gt;EXPLAIN&lt;/code&gt; plan?
&lt;/h2&gt;

&lt;p&gt;One plan shows what PostgreSQL chose and, with &lt;code&gt;ANALYZE&lt;/code&gt;, what happened during that single execution. It doesn't establish why the plan was slow or that a fix generalizes.&lt;/p&gt;

&lt;p&gt;A literal query investigated manually can produce a different plan from a &lt;a href="https://www.postgresql.org/docs/current/sql-prepare.html" rel="noopener noreferrer"&gt;prepared statement's generic plan&lt;/a&gt;. &lt;code&gt;EXPLAIN EXECUTE&lt;/code&gt; can show the prepared statement's plan. PostgreSQL also &lt;a href="https://www.postgresql.org/docs/18/using-explain.html" rel="noopener noreferrer"&gt;warns against extrapolating small-dataset results to substantially different situations&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Treat the plan as a diagnostic starting point. Combine it with statistics inspection, representative data, and (for intermittent problems) &lt;a href="https://www.postgresql.org/docs/current/auto-explain.html" rel="noopener noreferrer"&gt;auto_explain&lt;/a&gt; logging under controlled overhead.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions about reading PostgreSQL &lt;code&gt;EXPLAIN&lt;/code&gt; plans
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Are &lt;code&gt;EXPLAIN&lt;/code&gt; cost units milliseconds?
&lt;/h3&gt;

&lt;p&gt;No. Costs use a configurable scale. &lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt; reports actual time in milliseconds. Don't treat cost comparisons across servers, datasets, or versions as timing measurements.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does &lt;code&gt;EXPLAIN ANALYZE&lt;/code&gt; change my data?
&lt;/h3&gt;

&lt;p&gt;It executes the statement, so &lt;code&gt;INSERT&lt;/code&gt;, &lt;code&gt;UPDATE&lt;/code&gt;, and &lt;code&gt;DELETE&lt;/code&gt; can change data, and even &lt;code&gt;SELECT&lt;/code&gt; can have side effects when it calls functions such as &lt;code&gt;nextval&lt;/code&gt;. Rolling back a transaction doesn't reclaim &lt;code&gt;nextval&lt;/code&gt; sequence advances or resource consumption. Use plain &lt;code&gt;EXPLAIN&lt;/code&gt; when execution consequences are unknown.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I run &lt;code&gt;ANALYZE&lt;/code&gt; whenever estimated rows differ from actual rows?
&lt;/h3&gt;

&lt;p&gt;Not automatically. Check for early stops and loops first. If a node that ran to completion still shows a substantial mismatch, inspect relevant pg_stats. Fresh &lt;code&gt;ANALYZE&lt;/code&gt; updates sampled statistics but may not resolve the mismatch.  &lt;/p&gt;

</description>
      <category>sql</category>
      <category>database</category>
      <category>devops</category>
      <category>postgres</category>
    </item>
    <item>
      <title>Neon serverless Postgres: architecture, pricing, use cases, and tradeoffs</title>
      <dc:creator>Kamal G</dc:creator>
      <pubDate>Tue, 27 Oct 2026 16:28:48 +0000</pubDate>
      <link>https://dev.to/database-engineering/neon-serverless-postgres-in-2027-architecture-pricing-use-cases-and-tradeoffs-1adc</link>
      <guid>https://dev.to/database-engineering/neon-serverless-postgres-in-2027-architecture-pricing-use-cases-and-tradeoffs-1adc</guid>
      <description>&lt;p&gt;Many conventional PostgreSQL deployments keep compute running continuously and pair it with provisioned storage. Isolated test environments often require snapshots or full copies, although the exact architecture varies by provider.&lt;/p&gt;

&lt;p&gt;Continuously running compute can be a poor fit for intermittent traffic and temporary preview environments.&lt;/p&gt;

&lt;p&gt;Neon separates stateless Postgres compute from a distributed storage layer. This separation enables scale-to-zero compute, rapid database branching, and usage-based pricing.&lt;/p&gt;

&lt;p&gt;The decision to adopt Neon depends on whether the compute lifecycle, copy-on-write branching, and proxy-routed connection model fit your application better than conventional managed Postgres or a broader backend platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Neon fits teams that need fast database branching, preview environments, support for intermittent workloads, or AI/Postgres prototyping.
&lt;/li&gt;
&lt;li&gt;Neon separates stateless compute from durable storage, enabling scale-to-zero and copy-on-write branches.
&lt;/li&gt;
&lt;li&gt;Validate cold starts, SNI routing, PgBouncer transaction pooling, ORM behavior, and branch governance before production use.
&lt;/li&gt;
&lt;li&gt;Compare alternatives when a measured requirement is decisive: AWS-native operations, full infrastructure control, local NVMe with the required replication and durability settings, or a dedicated analytical path after OLTP and reporting contention appears.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is Neon serverless Postgres?
&lt;/h2&gt;

&lt;p&gt;Neon is a fully managed, serverless PostgreSQL database built on a custom &lt;a href="https://neon.com/blog/wal-s3-lakebase-storage-for-the-era-of-agents" rel="noopener noreferrer"&gt;storage architecture&lt;/a&gt;. Its engineering documentation now calls the database Lakebase Postgres. It separates Postgres compute from distributed storage built around &lt;a href="https://www.postgresql.org/docs/16/wal-intro.html" rel="noopener noreferrer"&gt;write-ahead logs (WAL)&lt;/a&gt;, safekeepers, pageservers, and durable object storage.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://neon.com/blog/neon-backend-is-ga" rel="noopener noreferrer"&gt;Neon backend&lt;/a&gt; reached general availability in September 2026 with Object Storage, Functions, Managed Better Auth, and AI Gateway alongside the database. Teams can use those services or external alternatives for adjacent application requirements. The PostgreSQL compute primarily serves transactional workloads.&lt;/p&gt;

&lt;p&gt;Neon manages infrastructure, compute lifecycle, storage durability, and branching. Customers remain responsible for schema design, indexing, query tuning, access control, connection routing, retries, branch data governance, and cost controls.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;selected plan&lt;/a&gt; determines available controls. Free requires suspension after five idle minutes; Launch can disable that timeout; Scale can configure it. Scale also adds IP allowlisting and private networking.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does Neon work?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Neon resource hierarchy and connection paths
&lt;/h3&gt;

&lt;p&gt;Neon environments are structured around these configuration objects and connection paths.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Project:&lt;/strong&gt; The top-level container for a database environment, holding all associated branches, computes, databases, roles, and settings.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Branch:&lt;/strong&gt; An isolated, copy-on-write timeline of the database state. You can create branches from other branches or from a specific point in time in the storage history.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database:&lt;/strong&gt; A standard Postgres database residing inside a branch.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Role:&lt;/strong&gt; A Postgres role for authentication, authorization, and connection management.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compute:&lt;/strong&gt; A Postgres instance attached to a branch. The compute executes queries, manages memory caches, and handles sessions, but holds no permanent durable state.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Endpoint:&lt;/strong&gt; The connection target for a compute. Endpoints are available as direct or pooled connections.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Connection proxy and TLS SNI routing:&lt;/strong&gt; Neon routes PostgreSQL connections through a proxy that identifies the correct tenant compute from the TLS Server Name Indication (SNI). Clients must support SNI. Legacy libpq builds, older Django configurations, and some desktop tools require client upgrades or explicit endpoint ID connection options to prevent "The endpoint ID is not specified" errors.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Direct endpoint:&lt;/strong&gt; The standard PostgreSQL port for administrative operations, schema migrations, pg_dump, long-lived sessions, and workflows requiring session-level Postgres features.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pooled endpoint:&lt;/strong&gt; A PgBouncer-backed connection path using transaction pooling, designed for applications with many short-lived client connections.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HTTP/WebSocket serverless driver paths:&lt;/strong&gt; Custom driver connections for JavaScript, edge, and serverless runtimes where persistent TCP connections are restricted or inefficient.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read replica:&lt;/strong&gt; A read-only compute endpoint attached to a branch to isolate read traffic.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Core Neon architecture components and boundaries
&lt;/h3&gt;

&lt;p&gt;The Neon architecture divides responsibilities between execution and durable state. The Postgres compute node handles query execution, in-memory caching, sessions, and supported extensions.&lt;/p&gt;

&lt;p&gt;Safekeepers receive the WAL stream from the compute node and ensure durable acceptance. Pageservers serve database pages to the compute node on demand and reconstruct page state from the underlying object storage history. Object storage retains the long-term immutable history required by the storage layer.&lt;/p&gt;

&lt;p&gt;Compute nodes maintain the cache and execution responsibility, but all durable state belongs to the networked storage layer.&lt;/p&gt;

&lt;h3&gt;
  
  
  What happens during a Neon transaction?
&lt;/h3&gt;

&lt;p&gt;During a write transaction, the Postgres compute executes the query and streams the resulting WAL to the safekeepers. Commit acknowledgment depends on the storage and WAL durability path, not on a local filesystem fsync.&lt;/p&gt;

&lt;p&gt;Reads check Postgres shared buffers, then Neon's &lt;a href="https://neon.com/docs/extensions/neon#what-is-the-compute-cache" rel="noopener noreferrer"&gt;Local File Cache&lt;/a&gt; where enabled. A miss requires a network request to the pageserver. &lt;a href="https://neon.com/docs/manage/computes#how-to-size-your-compute" rel="noopener noreferrer"&gt;Fixed computes of 18 CU or more&lt;/a&gt; disable the file cache and allocate more memory to shared buffers.&lt;/p&gt;

&lt;p&gt;When you create a branch, the system points a new timeline to an existing point in the storage history. Copy-on-write avoids an immediate full copy. &lt;a href="https://neon.com/pricing" rel="noopener noreferrer"&gt;Branch storage charges&lt;/a&gt; depend on divergence and retention; even an unchanged child branch can incur root-branch storage charges once it falls outside the history window.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Neon's separated compute and storage design enables and constrains
&lt;/h3&gt;

&lt;p&gt;Neon's architecture affects compute lifecycle, branching, storage latency, and connection behavior:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Separated durable storage allows computes to suspend, resize, or restart without moving a physical database volume, so computes can scale to zero.
&lt;/li&gt;
&lt;li&gt;Copy-on-write history allows rapid branch creation, enabling CI/CD pipelines and preview environments to use production-like state quickly.
&lt;/li&gt;
&lt;li&gt;The networked storage path means cache misses require a network request to the pageserver. Teams must test cold-cache latency and disk-heavy queries carefully.
&lt;/li&gt;
&lt;li&gt;Proxy-routed connections demand SNI-capable clients or explicit endpoint identifiers, requiring connection testing for older ORMs, tools, and CI images.
&lt;/li&gt;
&lt;li&gt;PgBouncer transaction pooling does not preserve arbitrary session state or SQL-level PREPARE across transactions; protocol-level prepared statements are supported.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What are Neon's key capabilities?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Database branching for preview environments
&lt;/h3&gt;

&lt;p&gt;Neon creates isolated, copy-on-write branches for development, staging, and migration rehearsals. Branching fits pull request environments, destructive schema migration testing, and reproducing production bugs against accurate data.&lt;/p&gt;

&lt;p&gt;One &lt;a href="https://www.reddit.com/r/Database/comments/1pfqlix/comment/nwek3nv/" rel="noopener noreferrer"&gt;team using Neon&lt;/a&gt; reported that separate development, staging, and test branches reduced friction between developers. An &lt;a href="https://news.ycombinator.com/item?id=47836037" rel="noopener noreferrer"&gt;April 2026 Hacker News commenter&lt;/a&gt; also described returning to Neon for branching after trying another provider.&lt;/p&gt;

&lt;p&gt;The primary constraints involve data governance and cost. Branches containing sensitive production data require strict masking rules or synthetic data substitution. Over time, abandoned branches and retained history increase storage, demanding automated retention policies and cleanup.&lt;/p&gt;

&lt;h3&gt;
  
  
  Scale-to-zero compute and autoscaling
&lt;/h3&gt;

&lt;p&gt;Neon supports fixed-size and autoscaling compute. Eligible idle computes can suspend while durable data remains in storage, stopping compute charges. Scale-to-zero fits intermittent applications, internal tools, and preview databases with extended idle windows.&lt;/p&gt;

&lt;p&gt;The primary constraint is wake-up latency. Resuming a suspended compute takes time, which can trigger client-side connection timeouts. In a &lt;a href="https://www.reddit.com/r/PostgreSQL/comments/1iq90ak/it_takes_12_seconds_for_a_simple_database_hit/" rel="noopener noreferrer"&gt;February 2025 account of a personal Django project on Neon Free&lt;/a&gt;, the author reported a 12-second first request, an improvement after changing providers, and a separate N+1 fix for the admin page. That request time did not isolate database wake-up latency. Measure the suspended-to-first-query path on the selected plan.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://neon.com/docs/guides/scale-to-zero-guide" rel="noopener noreferrer"&gt;Scale-to-zero controls&lt;/a&gt; apply to computes up to 16 CU. Free has a mandatory five-minute idle timeout. Launch retains five minutes but can disable suspension; Scale supports settings from one minute to always on. Larger fixed computes remain active.&lt;/p&gt;

&lt;h3&gt;
  
  
  Connection pooling, PgBouncer, and serverless connection paths
&lt;/h3&gt;

&lt;p&gt;Neon provides multiple connection strategies: direct endpoints, pooled endpoints, and serverless HTTP/WebSocket drivers. Pooled endpoints use PgBouncer in &lt;a href="https://www.pgbouncer.org/features.html" rel="noopener noreferrer"&gt;transaction pooling mode&lt;/a&gt; to handle high-fanout serverless functions and web applications with frequent, short-lived requests.&lt;/p&gt;

&lt;p&gt;SQL-level &lt;code&gt;PREPARE&lt;/code&gt;/&lt;code&gt;EXECUTE&lt;/code&gt; and other session-bound state are not portable across transactions, while Neon's &lt;a href="https://neon.com/docs/connect/connection-pooling" rel="noopener noreferrer"&gt;PgBouncer path supports protocol-level prepared statements&lt;/a&gt;. Use a direct endpoint for stable-session operations and validate the deployed ORM version.&lt;/p&gt;

&lt;p&gt;Runtime placement also matters. In an &lt;a href="https://www.reddit.com/r/reactnative/comments/1qi3czv/comment/o0owffq/" rel="noopener noreferrer"&gt;Expo discussion&lt;/a&gt;, a developer described using Neon across several projects through Expo's server-side API routes. That setup keeps the database connection in server code rather than the mobile client.&lt;/p&gt;

&lt;h3&gt;
  
  
  Read replicas and read-only compute endpoints
&lt;/h3&gt;

&lt;p&gt;Neon offers read-only compute endpoints for routing analytical or heavy read traffic away from the primary write compute. Users still create read-replica compute endpoints, but those computes attach to shared storage without copying the full dataset. WAL reaches replicas asynchronously, so read-after-write behavior must be tested.&lt;/p&gt;

&lt;p&gt;Read replicas fit read-heavy dashboards, API query endpoints, and reporting tasks. Teams must validate read-after-write expectations, replica freshness, cache warm-up behavior, and the cost impact of running additional active compute hours.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Neon used for?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Creating branch-based preview environments
&lt;/h3&gt;

&lt;p&gt;Separate branch computes isolate query execution for pull requests and migration testing without copying the full database. CI/CD automation must create, tag, scrub, and delete those environments reliably; production-derived data still requires masking and access controls.&lt;/p&gt;

&lt;h3&gt;
  
  
  Running intermittent, bursty, and serverless applications
&lt;/h3&gt;

&lt;p&gt;Neon's autoscaling and scale-to-zero mechanisms fit applications with cyclical usage or long idle windows. The cost benefit depends on actual suspension time, and the application must tolerate resume latency and connection retries.&lt;/p&gt;

&lt;h3&gt;
  
  
  AI and RAG prototyping with Postgres and pgvector
&lt;/h3&gt;

&lt;p&gt;AI applications often need disposable environments for experiments with embeddings, retrieval-augmented generation (RAG) pipelines, and vector indexing. Neon supports extensions such as &lt;a href="https://neon.com/docs/extensions/pgvector" rel="noopener noreferrer"&gt;pgvector&lt;/a&gt;, while branching isolates experiments safely.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://clickhouse.com/resources/engineering/scale-vector-search-postgres" rel="noopener noreferrer"&gt;Vector workloads&lt;/a&gt; demand significant memory and cache resources. Teams must test representative embedding volumes, index choices, and query latency under realistic concurrency.&lt;/p&gt;

&lt;h3&gt;
  
  
  Provisioning development and test databases quickly
&lt;/h3&gt;

&lt;p&gt;Disposable databases can reduce the need to manage local Postgres containers or share a staging cluster. Neon's projects, branches, and API-driven endpoints provide repeatable provisioning workflows.&lt;/p&gt;

&lt;p&gt;A &lt;a href="https://www.reddit.com/r/nextjs/comments/1lupqdk/comment/n1zuy08/" rel="noopener noreferrer"&gt;Next.js developer who had used both Neon and Supabase&lt;/a&gt; preferred Neon with Drizzle for keeping schema definitions in the codebase and iterating in TypeScript. Drizzle also works with Supabase.&lt;/p&gt;

&lt;p&gt;Before scaling this pattern, standardize environment naming, credential rotation, developer permissions, and cleanup automation.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should you know before using Neon in production?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Reliability and failure handling in Neon
&lt;/h3&gt;

&lt;p&gt;Neon's separated compute and storage model shifts how failures behave compared to single-host deployments. Compute lifecycle events, storage-path network requests, and point-in-time recovery operate differently than traditional local-disk failovers.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Production concern&lt;/th&gt;
&lt;th&gt;Neon behavior to account for&lt;/th&gt;
&lt;th&gt;Application responsibility&lt;/th&gt;
&lt;th&gt;What to test&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Compute restart, manual resize, or resume&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/manage/computes#what-happens-to-the-compute-when-making-changes" rel="noopener noreferrer"&gt;Restarts and manual size or autoscaling-bound changes&lt;/a&gt; disconnect sessions. Automatic autoscaling preserves them. Resume can delay new connections.&lt;/td&gt;
&lt;td&gt;Reconnect gracefully, retry safe operations, and enforce write idempotency.&lt;/td&gt;
&lt;td&gt;ORM pool recovery, retry limits, cold starts, and manual configuration changes.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Transaction interruption&lt;/td&gt;
&lt;td&gt;A lost connection can leave the client uncertain whether a transaction committed.&lt;/td&gt;
&lt;td&gt;Handle commit uncertainty and implement duplicate-prevention logic.&lt;/td&gt;
&lt;td&gt;Idempotency keys and transaction retry boundaries.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage-path network latency&lt;/td&gt;
&lt;td&gt;Cache misses require networked pageserver requests, surfacing latency during heavy un-cached reads.&lt;/td&gt;
&lt;td&gt;Avoid assuming local-disk latency guarantees for cache misses.&lt;/td&gt;
&lt;td&gt;Cold-cache read latency, heavy sequential scans, and block I/O behavior.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Point-in-time recovery (PITR)&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/postgres/backup-restore/branch-restore" rel="noopener noreferrer"&gt;Instant restore&lt;/a&gt; restores a root branch in place, affecting every database on it. Connection details stay unchanged; the previous state becomes a backup branch. Existing connections are interrupted.&lt;/td&gt;
&lt;td&gt;Select the recovery point, verify restored data, and reconnect clients.&lt;/td&gt;
&lt;td&gt;Restore rehearsals, branch-wide impact, data verification, and connection recovery.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In &lt;a href="https://neon.com/blog/postmortem-delayed-start-compute-operations" rel="noopener noreferrer"&gt;two May 2025 incidents&lt;/a&gt;, Neon reported 5.5 hours of impaired database creation and startup in AWS us-east-1; running databases were unaffected. Neon addressed IP allocation and capacity constraints. The incidents illustrate why startup availability matters separately from running-query availability. Review regional incident history and decide whether production computes should suspend.&lt;/p&gt;

&lt;h3&gt;
  
  
  Security, permissions, and branch data governance
&lt;/h3&gt;

&lt;p&gt;Neon encrypts data in transit and at rest. Among its self-service plans, &lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Scale includes IP allowlisting and private networking&lt;/a&gt;; Launch does not. &lt;a href="https://neon.com/docs/guides/neon-private-networking" rel="noopener noreferrer"&gt;Private networking uses AWS PrivateLink&lt;/a&gt; and requires the application and database to be in the same AWS region.&lt;/p&gt;

&lt;p&gt;PostgreSQL roles, schema privileges, and &lt;a href="https://www.postgresql.org/docs/current/ddl-rowsecurity.html" rel="noopener noreferrer"&gt;row-level security&lt;/a&gt; operate natively. Configuring them remains the customer's responsibility.&lt;/p&gt;

&lt;p&gt;Branch governance requires rules for who can copy production data and how it is masked. In an &lt;a href="https://news.ycombinator.com/item?id=47833744" rel="noopener noreferrer"&gt;April 2026 engineering account&lt;/a&gt;, a team pulled back from production-derived pull-request branches because masking rules could miss new columns or JSON fields; it preferred synthetic data until masking coverage could be enforced. Neon's &lt;a href="https://neon.com/docs/workflows/data-anonymization" rel="noopener noreferrer"&gt;anonymization feature&lt;/a&gt; applies static masking rules to specified tables and columns. Teams still own rule coverage, credentials, permissions, and branch cleanup.&lt;/p&gt;

&lt;h3&gt;
  
  
  Session semantics and ORM integration
&lt;/h3&gt;

&lt;p&gt;Session advisory locks, LISTEN/NOTIFY, temporary tables that must survive across transactions, and other stable-session features belong on a direct endpoint.&lt;/p&gt;

&lt;p&gt;For Prisma, &lt;a href="https://neon.com/docs/guides/prisma" rel="noopener noreferrer"&gt;current Neon guidance&lt;/a&gt; specifies a pooled application URL and a direct URL for CLI schema operations, including &lt;code&gt;prisma migrate&lt;/code&gt; and &lt;code&gt;prisma db push&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;A suspended compute can exceed a client's connection timeout and surface an error such as Prisma P1001. In &lt;a href="https://github.com/prisma/orm/discussions/23589" rel="noopener noreferrer"&gt;2025 replies to a Prisma discussion&lt;/a&gt;, increasing &lt;code&gt;connect_timeout&lt;/code&gt; helped some users but not others. Measure resume latency against the configured timeout, then test bounded retries only for operations that are safe to retry.&lt;/p&gt;

&lt;h3&gt;
  
  
  Monitoring, maintenance, and scale-to-zero blockers
&lt;/h3&gt;

&lt;p&gt;The Neon console provides visibility into CPU, memory, storage, connections, and basic Postgres telemetry. Teams remain responsible for query tuning, index optimization, and slow-query analysis using standard tools like pg_stat_statements.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://neon.com/docs/manage/computes#compute-is-not-suspending" rel="noopener noreferrer"&gt;Repeated connection requests and queries&lt;/a&gt; can prevent scale-to-zero. An idle open connection alone does not keep compute active, but pool validation queries, scheduled jobs, and database health checks can.&lt;/p&gt;

&lt;p&gt;One &lt;a href="https://www.reddit.com/r/devops/comments/1ozelub/i_had_a_157_surprise_bill_and_spent_3_months/" rel="noopener noreferrer"&gt;SaaS founder reported a \$157 monthly bill&lt;/a&gt; and attributed unwanted activity to workflow automation, an AI editor's database integration, and application polling. Audit those clients and queries alongside the autosuspend setting.&lt;/p&gt;

&lt;h3&gt;
  
  
  Adoption requirements and exit constraints
&lt;/h3&gt;

&lt;p&gt;Adopting Neon requires updating database connection strategies to handle direct, pooled, and serverless driver endpoints appropriately. Migration involves standard dump and restore processes, &lt;a href="https://www.postgresql.org/docs/current/logical-replication.html" rel="noopener noreferrer"&gt;logical replication&lt;/a&gt;, or CSV imports, depending on database size and downtime tolerance.&lt;/p&gt;

&lt;p&gt;Postgres schema and data remain portable, while Neon-specific integrations can require rework. In a &lt;a href="https://www.reddit.com/r/replit/comments/1rcxr3i/replit_helium_upgrade_neon_replithosted_broke_our/" rel="noopener noreferrer"&gt;February 2026 Replit development-database migration&lt;/a&gt;, the author reported that data, row-level security policies, and functions survived and TCP connections worked. Code using Neon's HTTP serverless driver needed a replacement. Branching automation and compute-lifecycle assumptions also need review before an exit.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does Neon cost?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Pricing model and cost drivers
&lt;/h3&gt;

&lt;p&gt;As of October 2026, Neon's self-service plans bill by resource consumption with plan-specific allowances and controls. &lt;a href="https://neon.com/blog/new-usage-based-pricing" rel="noopener noreferrer"&gt;Pricing changes since August 2025&lt;/a&gt; mean older invoices reflect different rates or minimums; use the &lt;a href="https://neon.com/pricing" rel="noopener noreferrer"&gt;current pricing page&lt;/a&gt; for estimates.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan area&lt;/th&gt;
&lt;th&gt;What it includes&lt;/th&gt;
&lt;th&gt;Why it matters&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Plan&lt;/td&gt;
&lt;td&gt;
&lt;a href="https://neon.com/docs/introduction/plans" rel="noopener noreferrer"&gt;Self-service plans use usage-based pricing&lt;/a&gt;, while included allowances and features vary by plan.&lt;/td&gt;
&lt;td&gt;Determines feature access, support, and included usage.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compute&lt;/td&gt;
&lt;td&gt;Compute Unit (CU) hour pricing, driven by actual compute size and active time.&lt;/td&gt;
&lt;td&gt;Determines the compute portion of the bill for active and always-on workloads.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Storage and history&lt;/td&gt;
&lt;td&gt;GB-month pricing for stored data, branch deltas, and retained restore history.&lt;/td&gt;
&lt;td&gt;Creates ongoing charges even when compute is suspended.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Additional branches and data transfer&lt;/td&gt;
&lt;td&gt;Included allowances and any additional charges depend on the current plan.&lt;/td&gt;
&lt;td&gt;Matters for branch-heavy workflows, exports, and cross-cloud traffic.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Limits and security&lt;/td&gt;
&lt;td&gt;Branch allowances, compute sizes, monitoring retention, IP allowlisting, and private networking vary by plan.&lt;/td&gt;
&lt;td&gt;Determines whether the required production controls are available.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Compute charges follow actual CU size multiplied by active time. The autoscaling maximum caps possible usage but is not billed capacity; background activity can prevent idle suspension and increase CU-hours.&lt;/p&gt;

&lt;p&gt;Paid-plan allowances also differ from Free. In &lt;a href="https://www.reddit.com/r/PostgreSQL/comments/1ms8kis/comment/okmkr8n/" rel="noopener noreferrer"&gt;May 2026, one Launch customer&lt;/a&gt; reported that Free's compute allowance did not carry over. Check the selected plan's included usage before extrapolating from a Free project.&lt;/p&gt;

&lt;p&gt;Branching is lightweight at creation, but divergent writes and active branch computes incur ongoing fees.&lt;/p&gt;

&lt;h3&gt;
  
  
  Cost examples for bursty and sustained workloads
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Bursty preview-environment scenario:&lt;/strong&gt; For short-lived pull-request branches, calculate the cost from active compute time, compute size, storage, restore history, branch usage, and data transfer. A branch that is active only during testing and then suspends may consume fewer CU-hours than an equivalent always-on staging instance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sustained OLTP scenario:&lt;/strong&gt; A continuously active compute accrues CU-hours without idle savings. Compare its monthly compute and storage costs against a fixed-size managed Postgres instance. In &lt;a href="https://blog.opensecret.cloud/why-we-migrated-from-neon-to-planetscale/" rel="noopener noreferrer"&gt;August 2025, OpenSecret&lt;/a&gt; cited rising usage-based costs among its reasons for moving four databases supporting an always-on application to PlanetScale's fixed-price service.&lt;/p&gt;

&lt;p&gt;For one smaller deployment, a &lt;a href="https://www.reddit.com/r/Database/comments/1pfqlix/comment/nssye20/" rel="noopener noreferrer"&gt;December 2025 account from a user with two active projects&lt;/a&gt; reported a \$38 monthly bill, considered the pricing reasonable, and cautioned that egress could add up.&lt;/p&gt;

&lt;h3&gt;
  
  
  What makes Neon costs rise?
&lt;/h3&gt;

&lt;p&gt;Pool validation queries, pg_cron jobs, or database health checks increase costs when they keep computes active.&lt;/p&gt;

&lt;p&gt;Leaving scale-to-zero disabled for development endpoints, allowing branch sprawl without cleanup policies, and retaining extensive history windows on high-write databases inflate storage and compute bills.&lt;/p&gt;

&lt;p&gt;Large data exports, analytics pipelines, or cross-region application traffic will also drive up network egress charges.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are Neon's limitations and tradeoffs?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Networked storage can increase cold-cache latency
&lt;/h3&gt;

&lt;p&gt;Reads that miss shared buffers and the Local File Cache, where enabled, require a network request to the pageserver. Fixed computes of 18 CU or more rely on larger shared buffers instead of the file cache. End-to-end latency depends on the working set, compute size, query shape, and compared storage system.&lt;/p&gt;

&lt;p&gt;Teams should first test cold-cache latency and disk-heavy queries against workload targets. Consider a configuration or architecture change only when those measurements show that the current approach cannot meet those targets.&lt;/p&gt;

&lt;h3&gt;
  
  
  Serverless lifecycle changes connection and retry assumptions
&lt;/h3&gt;

&lt;p&gt;Applications must handle resume latency, interrupted sessions, and bounded reconnects. Keeping compute active removes suspension-related wake-up delays and idle savings; it does not remove other connection failure modes.&lt;/p&gt;

&lt;p&gt;Troubleshooting accounts identify several possible causes: &lt;a href="https://www.reddit.com/r/Nestjs_framework/comments/1tem71v/typeorm_etimedout_when_connecting_to_neon/om9dh6y/" rel="noopener noreferrer"&gt;connections accumulating during NestJS hot reload in May 2026&lt;/a&gt;, &lt;a href="https://stackoverflow.com/questions/78705101/can-not-connect-to-neon-using-prisma" rel="noopener noreferrer"&gt;network problems addressed with VPN or DNS changes in a Prisma thread&lt;/a&gt;, and &lt;a href="https://stackoverflow.com/questions/79993818/cant-connect-to-neon-database-using-sequelize" rel="noopener noreferrer"&gt;Node.js address selection in August 2026&lt;/a&gt;. Diagnose the connection path and application behavior before attributing an error to Neon.&lt;/p&gt;

&lt;h3&gt;
  
  
  PgBouncer transaction pooling changes session semantics
&lt;/h3&gt;

&lt;p&gt;Neon's built-in pooling multiplexes traffic efficiently but does not preserve arbitrary session state across transactions. Applications can route session-dependent operations to the direct endpoint instead of abandoning those features entirely.&lt;/p&gt;

&lt;h3&gt;
  
  
  Proxy routing and SNI require compatible clients
&lt;/h3&gt;

&lt;p&gt;The ingress routing architecture requires TLS SNI. Legacy libpq installations, older ORMs, CI pipeline containers, and some database GUI tools fail to connect without explicit endpoint parameters.&lt;/p&gt;

&lt;p&gt;Validate all operational scripts and runtime environments before migration.&lt;/p&gt;

&lt;h3&gt;
  
  
  Heavy analytics and always-on workloads may reduce Neon's fit
&lt;/h3&gt;

&lt;p&gt;Heavy aggregations and analytical scans executed on the same PostgreSQL compute compete with transactions for resources. Neon's &lt;a href="https://neon.com/docs/guides/read-replica-data-analysis" rel="noopener noreferrer"&gt;read replicas isolate query execution&lt;/a&gt; on separate computes; moving reporting traffic requires application routing.&lt;/p&gt;

&lt;p&gt;Continuous, always-on production traffic nullifies scale-to-zero savings. When measurements show that reporting load causes transactional requests to miss their latency target, teams should evaluate a dedicated analytical system.&lt;/p&gt;

&lt;h3&gt;
  
  
  Managed service boundaries limit low-level PostgreSQL control
&lt;/h3&gt;

&lt;p&gt;Neon does not provide arbitrary operating system access, custom compiled extensions, deep kernel tuning, or direct filesystem control. Applications requiring niche OS dependencies, highly specialized replication setups, or custom infrastructure architectures should evaluate self-managed PostgreSQL.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does Neon compare with Supabase, Aurora, self-managed PostgreSQL, and ClickHouse Managed Postgres?
&lt;/h2&gt;

&lt;p&gt;Compare &lt;a href="https://clickhouse.com/resources/engineering/neon-alternatives-managed-postgres" rel="noopener noreferrer"&gt;alternative deployment models&lt;/a&gt; based on which specific backend, AWS-native, infrastructure-control, or I/O requirement outranks serverless branching.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Decision baseline&lt;/th&gt;
&lt;th&gt;Prefer it when&lt;/th&gt;
&lt;th&gt;What changes relative to Neon&lt;/th&gt;
&lt;th&gt;Decision trigger&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Supabase&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The team wants Supabase's Postgres, Auth, Storage, Realtime, and Edge Functions workflows.&lt;/td&gt;
&lt;td&gt;Both are backend platforms: Supabase centers its established application-service bundle around each Postgres project, while the &lt;a href="https://neon.com/blog/neon-backend-is-ga" rel="noopener noreferrer"&gt;Neon backend&lt;/a&gt; centers its branching Postgres model and adds Object Storage, Functions, Managed Better Auth, and AI Gateway.&lt;/td&gt;
&lt;td&gt;Choose Supabase when its Postgres, Auth, Storage, Realtime, and Edge Functions workflows are decisive; choose Neon when branchable database and backend primitives plus Neon's compute lifecycle fit the application better.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Amazon RDS or Aurora&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The organization standardizes on AWS operations, procurement, networking, governance, and compliance workflows.&lt;/td&gt;
&lt;td&gt;AWS-native integration, IAM alignment, and established VPC patterns dictate the operational model.&lt;/td&gt;
&lt;td&gt;Choose RDS/Aurora when AWS alignment, existing commitments, or enterprise operational standardization outweigh database branching.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Self-managed PostgreSQL&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The team requires full control over the OS, specialized extensions, storage layout, custom backups, replication, or specialized tuning.&lt;/td&gt;
&lt;td&gt;Operational ownership shifts to the customer, encompassing HA, patching, monitoring, security, and failover mechanics.&lt;/td&gt;
&lt;td&gt;Choose self-managed Postgres when total infrastructure control, legal compliance, or extension requirements outweigh managed-service convenience.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ClickHouse Managed Postgres&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Sustained, performance-critical OLTP calls for always-on compute and local NVMe, or a separate ClickHouse analytical service.&lt;/td&gt;
&lt;td&gt;Local NVMe-backed Postgres offers no standby, one asynchronous standby, or two synchronous standbys. Replication to a separately provisioned ClickHouse service is asynchronous, so the analytical copy is eventually consistent.&lt;/td&gt;
&lt;td&gt;Evaluate local NVMe with the standby configuration the application requires. Choose this model when measured transactional performance or the separate analytics path matters more than serverless branching.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How should you evaluate Neon for your workload?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Define pass/fail criteria:&lt;/strong&gt; Set targets for suspended and warm latency, connection handling, data governance, and monthly costs.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Provision a representative environment:&lt;/strong&gt; Import schema and data, configure runtime and migration roles, and create a test branch.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Select connection paths:&lt;/strong&gt; Use direct endpoints for session-dependent tools, pooled endpoints for short application transactions, and supported HTTP/WebSocket drivers for edge runtimes. Test legacy clients for SNI compatibility.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Validate ORM and migration tooling:&lt;/strong&gt; Follow &lt;a href="https://neon.com/docs/guides/prisma" rel="noopener noreferrer"&gt;Neon's Prisma guidance&lt;/a&gt;: pooled connections for application queries, direct connections for &lt;code&gt;prisma migrate&lt;/code&gt; and &lt;code&gt;prisma db push&lt;/code&gt;. Test the deployed versions.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test lifecycle and recovery:&lt;/strong&gt; Compare suspended and warm query paths, bound safe retries, and rehearse restores. Confirm the plan supports the required suspension settings.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Implement branch governance:&lt;/strong&gt; Automate creation, masking, retention, and deletion. Test replica freshness and cache warm-up if using read replicas.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Establish the escalation owner:&lt;/strong&gt; Confirm support responsibilities across providers. In a &lt;a href="https://www.reddit.com/r/PostgreSQL/comments/1m1n9gy/neondb_support_came_through/" rel="noopener noreferrer"&gt;July 2025 Azure-hosted Neon account&lt;/a&gt;, the author credited Neon's support with resolving the issue after coordination with Azure complicated troubleshooting.
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model costs and decide:&lt;/strong&gt; Include compute size and active time, storage, history, branches, and egress. If continuous activity removes idle savings, re-model the economics against fixed-size managed options. Evaluate alternatives when measured latency, tooling, governance, or cost requirements remain unmet.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Conclusion: Is Neon right for your team?
&lt;/h2&gt;

&lt;p&gt;Neon fits PostgreSQL teams that need branch-based development workflows, fast preview environments, elastic compute, and idle-time savings. It supports AI prototyping and pull-request automation when rapid environment provisioning and an idle-time compute model are priorities.&lt;/p&gt;

&lt;p&gt;The decision changes when your workload demands predictable warm performance, session-heavy Postgres semantics, a &lt;a href="https://clickhouse.com/blog/postgres-on-nvme" rel="noopener noreferrer"&gt;locally attached storage architecture&lt;/a&gt;, extensive OS-level customization, or heavy analytical capabilities that disrupt OLTP latency.&lt;/p&gt;

&lt;p&gt;Proceed if measured connection behavior, data governance, and pricing fit your requirements. Disabling scale-to-zero does not by itself disqualify Neon because fixed-size and autoscaling always-active computes remain available. For sustained, performance-critical OLTP, compare &lt;a href="https://clickhouse.com/docs/products/managed-postgres/overview" rel="noopener noreferrer"&gt;ClickHouse Managed Postgres&lt;/a&gt; using the standby configuration the application requires and representative queries. Evaluate its separately provisioned ClickHouse analytics path when reporting isolation is decisive.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently asked questions about Neon
&lt;/h2&gt;

&lt;h3&gt;
  
  
  What workloads is Neon best for?
&lt;/h3&gt;

&lt;p&gt;Neon fits preview environments, branch-based development, intermittent applications, serverless workloads, and AI/Postgres prototypes when fast provisioning and scale-to-zero reduce cost or operational friction.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Neon suitable for production?
&lt;/h3&gt;

&lt;p&gt;Yes, Neon supports production workloads. Production deployments require appropriate compute sizing, connection routing, retry logic, branch data governance, and cost modeling. Configure autoscaling limits if autoscaling is enabled.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Neon scale to zero?
&lt;/h3&gt;

&lt;p&gt;Yes, eligible computes up to 16 CU can suspend, stopping compute charges while storage and other applicable charges continue. Free requires a five-minute idle timeout; Launch can disable it; Scale can configure one minute to always on. Repeated connection requests and background queries can prevent suspension; an idle open connection alone does not.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I use Neon's direct or pooled connection string?
&lt;/h3&gt;

&lt;p&gt;Use the direct connection for migrations, admin tools, dumps, and session-dependent workflows. Use the pooled PgBouncer connection for high-concurrency applications with short transactions after validating transaction-pooling compatibility.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Neon work well with Prisma?
&lt;/h3&gt;

&lt;p&gt;Yes. &lt;a href="https://neon.com/docs/guides/prisma" rel="noopener noreferrer"&gt;Neon's current Prisma guide&lt;/a&gt; uses a pooled URL for application queries and a direct URL for &lt;code&gt;prisma migrate&lt;/code&gt; and &lt;code&gt;prisma db push&lt;/code&gt;. Test suspended-compute wake-up latency against Prisma's connection timeout, and add bounded retries only for operations that are safe to retry.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Neon suitable for analytics workloads?
&lt;/h3&gt;

&lt;p&gt;Neon supports operational reporting, and read replicas can move analytical queries onto separate compute. Heavy scans on the primary can compete with transactions. Evaluate a &lt;a href="https://clickhouse.com/resources/engineering/clickhouse-vs-postgresql-analytics" rel="noopener noreferrer"&gt;dedicated analytical database&lt;/a&gt; when query latency, concurrency, freshness, or total compute cost remains unsuitable after assessing &lt;a href="https://neon.com/docs/guides/read-replica-data-analysis" rel="noopener noreferrer"&gt;Neon's read-replica approach&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  How can I keep Neon costs under control?
&lt;/h3&gt;

&lt;p&gt;Control costs by deleting unused branches, limiting retained history, auditing background jobs that prevent suspension, setting appropriate autoscaling limits, and comparing always-on compute costs against &lt;a href="https://clickhouse.com/resources/engineering/managed-postgres-for-ai-and-real-time-apps" rel="noopener noreferrer"&gt;fixed managed Postgres options&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is Neon branching safe for production data?
&lt;/h3&gt;

&lt;p&gt;Branching is useful, but branches created from production data require governance. Use masking, access controls, retention policies, and automated cleanup to prevent sensitive data exposure and branch sprawl.&lt;/p&gt;

&lt;h3&gt;
  
  
  When should I not use Neon?
&lt;/h3&gt;

&lt;p&gt;Consider alternatives when a tested requirement cannot be met, such as unsupported OS-level control, session-bound behavior that cannot use direct endpoints, or cold-cache and analytical latency outside the workload's target. Continuous traffic alone is not a disqualifier; it removes scale-to-zero savings but can still use autoscaling.&lt;/p&gt;

&lt;h3&gt;
  
  
  How is Neon different from Aurora Serverless?
&lt;/h3&gt;

&lt;p&gt;Choose Neon when fast branching, preview databases, and scale-to-zero Postgres are decisive for your workflow. Choose Aurora when AWS-native networking, IAM, procurement, or enterprise governance is decisive.&lt;/p&gt;

</description>
      <category>database</category>
      <category>postgres</category>
      <category>devops</category>
      <category>data</category>
    </item>
  </channel>
</rss>
