ClickHouse Managed Postgres Pricing: $23/mo, for Now
Verified on August, 2026
ClickHouse Managed Postgres costs $23.19 a month in ap-south-1 (Mumbai). Without the beta discount that same machine is $46.38, and three of the four lines on the bill have not been switched on yet.
Key Facts
- The price is $23.19/mo in ap-south-1 for 1 vCPU, 8 GB RAM, and 59 GB NVMe, or $35.74/mo for the same configuration in us-east-1. Both include the 50% beta discount.
- Three of the four bill lines are switched off. Ingestion, backups, and data transfer are all free in beta. Only the machine is metered, and it is half price.
- The same vendor prices the same region in opposite directions. Managed Postgres is 35% cheaper in ap-south-1, while its analytics engine is 8% more expensive there and egress is 20% more expensive. No region is cheap for both.
- Loading your data has a price. ClickPipes Postgres CDC bills $0.10/GB for the initial load and $0.20/GB for continuous replication, so migrating a 500 GB Postgres database costs about $50 (₹4,786).
- There is no volume discount. Pricing is linear in both regions, so 64 vCPU costs exactly 64 times as much as 1 vCPU.
- Basic caps at 8 GB of RAM. The tier applies to your entire ClickHouse Cloud organization, so outgrowing it raises the organization floor from $66.52/mo to $499.38/mo.
Most teams arrive at ClickHouse Managed Postgres pricing the same way. Postgres runs the application, ClickHouse runs the analytics, something copies rows between them at three in the morning, and ClickHouse has now offered to run all three.
The prices above are the ones their calculator returns today. What follows is the rate card behind them, because ClickHouse publishes no per-configuration prices anywhere in text and sends every visitor to a calculator instead.
How we priced this. Every ClickHouse figure is either quoted from their own documentation or read from their pricing calculator, with the region and configuration named. Where we model a cost that applies after general availability, we apply a rate ClickHouse already publishes and say so.
Selfhost.dev sells managed Postgres and managed ClickHouse, so we have a stake in this comparison. That is exactly why the assumptions are on the page. Check the arithmetic rather than trusting us.
Table of Contents
What is ClickHouse Managed Postgres?
ClickHouse Managed Postgres is a hosted PostgreSQL service sold by ClickHouse, built to sit beside their analytics engine rather than replace it. It runs on NVMe-backed machines, replicates into ClickHouse through ClickPipes CDC, and ships the pg_clickhouse extension for querying both engines over one connection. It has been in public beta since 27 May 2026.
| ClickHouse Managed Postgres at a Glance | |
|---|---|
| What it is | Managed PostgreSQL on NVMe-backed VMs, inside a ClickHouse Cloud organisation |
| Replication into ClickHouse | Native, via ClickPipes Postgres CDC |
| Cross-engine queries | pg_clickhouse, a Postgres extension |
| Status | Public beta since 27 May 2026, metered from 15 June 2026 |
| Tiers | Basic, Scale, Enterprise |
The reason it needs its own pricing article, separate from ClickHouse Cloud’s, is that the two halves are billed on unrelated models. This one charges for a machine. The analytics side charges per compute unit-hour.
How much does ClickHouse Managed Postgres cost?
The entry configuration costs $23.19 a month in ap-south-1 region and $35.74 in us-east-1. Both include the 50% beta discount. ClickHouse prices Managed Postgres per whole machine, not per resource: “pricing is based on the full VM configuration, CPU, memory, and storage, rather than separate compute and disk charges.” That, and every other quote in this article, comes from their Managed Postgres pricing documentation.
| vCPU | RAM | Storage | Mumbai (ap-south-1) | us-east-1 |
|---|---|---|---|---|
| 1 | 8 GB | 59 GB | $23.19 | $35.74 |
| 2 | 16 GB | 118 GB | $46.38 | $71.48 |
| 4 | 32 GB | 237 GB | $92.75 | $142.96 |
| 8 | 64 GB | 474 GB | $185.51 | $285.93 |
| 16 | 128 GB | 950 GB | $371.02 | $571.85 |
| 64 | 512 GB | 3,800 GB | $1,484.06 | $2,287.41 |
The ratio between the two regions is identical from 1 vCPU to 64.
ClickHouse offers “over 50 configurations” up to 96 vCPUs, 768 GB of RAM and 60 TB of NVMe. None of those prices appear in text on their site, which is why the table above exists.
One number worth flagging: their own beta announcement puts the entry configuration at “approximately $32/month.” We could not reproduce that in either region. Price your own region rather than the announcement.
Managed Postgres and ClickHouse Cloud are billed on different models. This charges for a machine; the analytics side charges per compute unit-hour, and what the analytics half costs running around the clock is a separate calculation.
ClickHouse does not print a per-configuration rate card, so you cannot check any of this against your own workload on their site. Ours is public. See the whole bill, not the headline price, no signup needed.
Does ClickHouse Managed Postgres get cheaper at scale?
No. Pricing scales linearly. Every configuration costs the same per unit of capacity.
One unit is 1 vCPU, 8 GB of RAM and 59 GB of NVMe: $23.19 a month in ap-south-1, $35.74 in us-east-1. Every rung is a multiple of it. Sixty-four units should cost $1,484.16, and the calculator returns $1,484.06, a ten-cent gap that is rounding rather than a discount.
A bigger machine buys more capacity at the same rate, never a better one.
Two caveats. The pattern holds within a hardware family, so the 64 vCPU box with 256 GB of RAM sits on a different vCPU-to-memory ratio and breaks the multiple. And it describes calculator prices, not a negotiated contract.
What do the Basic and Scale tiers cost?
The tier is not a Postgres plan. It is your whole ClickHouse Cloud organization’s tier, and it caps what you are allowed to buy. Basic stops at 8 GB of RAM and 118 GB of storage, which covers only the bottom of the rate card. ClickHouse publishes no per-tier price for an identical machine.
| Feature | Basic | Scale |
|---|---|---|
| Compute ceiling | Up to 8 GB RAM | Up to 96 vCPU and 768 GB RAM |
| Storage ceiling | Up to 118 GB local NVMe | Up to 60 TB |
| Share of the 50+ configurations | Only those at or below the ceiling | All of them |
| Backup retention | 1 day | 7 days |
| ClickPipes CDC compute | $0.10/hr 0.5 CU (1 vCPU, 4 GB) per service | $0.20/hr 1 CU (2 vCPU, 8 GB) per service |
| Same rate per CU-hour | $0.20 | $0.20 |
| Machine price for an identical configuration | Not published ClickHouse states pricing varies by organization tier | Not published |
| ClickHouse Cloud organization starts from | $66.52/mo | $499.38/mo |
Enterprise is the third tier. It inherits Scale’s limits with enhanced support and has no published price.
That reframes the entry price. The $23.19 configuration sits inside Basic, and Basic has almost no headroom above it. Of the fifty-plus configurations ClickHouse offers, only the handful at or below 8 GB of RAM and 118 GB of storage are available on it.
So the ninth gigabyte of RAM is not a database decision. It is an organization decision. Moving the organization to Scale to buy a 16 GB Postgres also moves the analytics half of the stack, where the floor rises from $66.52 a month to $499.38.
One caveat, because it matters: that figure is the starting price of a Scale ClickHouse service, not a documented fee for holding a Scale organization. It lands on teams running both engines, which is this product’s entire audience.
The CDC compute line deserves a correction to how it is usually reported. Scale bills $0.20 an hour against Basic’s $0.10, but it also gives you twice the pipe, 1 CU against 0.5 CU. Per CU-hour both tiers charge the same $0.20. The tier changes the size of the smallest pipe you can buy, not the rate.
What is not knowable from their documentation is whether the same box costs more on Scale than on Basic. ClickHouse says pricing varies by tier and prints no comparison. If your organization is already on Scale, price your configuration with that tier selected rather than trusting the figures above.
What is free only during the beta, and what changes at GA?
Three of the four lines on a Managed Postgres bill are currently set to zero. ClickHouse’s calculator splits it into storage and compute, data ingestion via ClickPipes, backups, and data transfer. The first carries a 50% discount badge. The other three are marked “Free in Beta.”
| Line item | Today | At general availability |
|---|---|---|
| Storage and compute | 50% beta discount applied | Discount ends |
| Data ingestion (ClickPipes) | Free in Beta | Not stated |
| Backups | Free in Beta | “Additional backup charges may apply at GA for retention periods beyond a limit that is still being defined” |
| Data transfer | Free in Beta | “Network egress pricing will be introduced after GA” |
Those quotes are ClickHouse’s own words. The discount is documented in the same place: “All plans currently include 50% Beta pricing.” The service was free outright until metering began on 15 June 2026.
Those three rows are not expandable in the calculator, so it will not tell you what any of them will cost. What it tells you is that the rows are built.
Removing a 50% discount doubles a price:
| Region | Today | With the discount removed |
|---|---|---|
| Mumbai | $23.19 | $46.38 |
| us-east-1 | $35.74 | $71.48 |
That second column is arithmetic on ClickHouse’s own discount, not a price they have announced. ClickHouse has not published a post-GA rate card for Managed Postgres, so nobody can tell you what it will cost, including us.
Everywhere this article models a post-GA cost, it applies a rate ClickHouse already publishes elsewhere and names it. For egress, the nearest reference is their analytics product, documented at $0.1152/GB for AWS US and priced at $0.1384/GB in ap-south-1.
Three of those four rows are meters, and two bill per gigabyte. That matters more than the discount does. A fixed monthly machine price is something you can forecast a year out. A per-gigabyte charge is something you discover, because it moves with how much data your users pull and how much your tables change, and neither is a number most teams predict accurately a month ahead.
Right now all three meters read zero, so the bill looks perfectly stable.
That stability is a property of the beta, not of the pricing model. When the meters switch on, the predictable part of the bill stays the same size and the unpredictable part grows from nothing.
The gap between a quiet month and a busy one is what we call bill variance, and on this product it is currently impossible to calculate.
Three meters with no published rate is not something you can budget around. Ours are all published, and in the console you can watch them tick against the estimate. Open our console and see the meter agree with the number. No commitment, billed by the hour.
How much does ClickPipes Postgres CDC cost?
CDC is included at no extra cost on Managed Postgres during the beta. It is not free anywhere else. ClickPipes Postgres CDC is a generally available product with a published rate card.
| Line | Rate |
|---|---|
| Initial load and resync | $0.10 / GB |
| Continuous replication | $0.20 / GB |
| Compute, Basic tier | $0.10 / hour 0.5 compute units (1 vCPU, 4 GB RAM) per service |
| Compute, Scale tier | $0.20 / hour 1 compute unit (2 vCPU, 8 GB RAM) per service |
| Streaming ingestion, for comparison | $0.04 / GB Kafka, Kinesis and object storage pipes |
Continuous replication costs five times what streaming ingestion costs. ClickHouse charges $0.04 per GB for a Kafka or object-storage pipe and $0.20 per GB for Postgres CDC. Managed Postgres uses the CDC flavour.
Loading your existing database in is itself a charge. A 500 GB Postgres moved across, then 100 GB a month of changes kept in sync:
| Line | Calculation | Cost |
|---|---|---|
| Initial load, 500 GB | 500 × $0.10/GB | $50.00 one-off |
| Continuous replication, 100 GB per month | 100 × $0.20/GB | $20.00 per month |
| First month, data charges only | $50.00 + $20.00 | $70.00 |
Compute is excluded because ClickHouse publishes the hourly rate per service but does not state whether it accrues while a pipe is idle, and inventing a number there is the kind of guess this article avoids.
One detail from their documentation that nobody appears to have noticed: ClickHouse lists MySQL and MongoDB CDC as free during their public betas, and Postgres CDC as generally available with standard billing. The connector this product depends on is the one that already has a meter on it. Whether Managed Postgres CDC bills at these rates after the beta is not something ClickHouse has said. These are the rates every other customer pays today.
Which makes this the least forecastable line in the bill. Your CDC cost tracks how much your data changes, and change rate is the one number almost nobody predicts a month ahead. If you would rather not have a meter on it, there are other ways to move data from Postgres into ClickHouse.
What limits change your ClickHouse Managed Postgres bill?
Four constraints move the bill more than the headline price does: how small you can go, how long backups are kept, whether storage can be sized on its own, and where you deploy.
What is the cheapest ClickHouse Managed Postgres configuration?
$23.19 a month in ap-south-1, for 1 vCPU, 8 GB of RAM and 59 GB of NVMe on the memory-optimized profile. Nothing in the list goes below 4 GB of RAM, and nothing in it is free. The smallest-memory option is not the cheapest. CPU-optimized at 2 vCPU and 4 GB costs $30.40, so halving the RAM and doubling the vCPU costs 31% more.
How long does ClickHouse Managed Postgres keep backups?
One day on Basic, seven on Scale, per their documentation: “Backups with retention of 1 day” and “Backups with retention of 7 days.” One day of retention means a problem you notice on Wednesday cannot be recovered from Monday. Whether longer retention is purchasable on Basic or requires the tier move is not documented, so we will not claim it either way.
Can you size storage independently of compute?
No. Storage is fixed to each configuration, which follows from pricing the whole machine rather than its parts. Wanting 468 GB means taking the storage-optimized 2 vCPU, 16 GB box at $120.82, whether or not you need the CPU. That falls hardest on the workload this product targets. A Postgres feeding an analytics pipeline usually needs far more disk than CPU, and here you cannot buy one without the other.
Do hardware profiles and region change the price?
Both do, and the profiles are not price tiers. They are resource bundles, so the same vCPU count lands in three different places. At 2 vCPU in Mumbai:
- Memory-optimized: $46.38
- Storage-optimized: $120.82
- CPU-optimized: cheapest of the three, priced above
X86-64 is unavailable on CPU-optimized, which is ARM only.
Region is the blunter lever. ap-south-1 is 35% cheaper than us-east-1 at every configuration size, which for most of this ladder is a larger saving than any sizing decision you will make.
Where does the money in a ClickHouse Managed Postgres bill actually go?
Not mostly into the Postgres. This product exists to sit beside an analytics engine, so the honest unit of comparison is the pair. On the pair, the Postgres line is the smaller share of the bill. It is also the only share carrying a discount.
The Postgres half is 50% off during the beta. The analytics half is not discounted at all. The two also move in opposite directions by region.
| Item | Mumbai against us-east-1 |
|---|---|
| Managed Postgres | 35% cheaper at every configuration size |
| ClickHouse Cloud analytics compute | 8% dearer |
| Public internet egress | 20% dearer $0.1152/GB in AWS US against $0.1384/GB in Mumbai |
So there is no region that is cheap for both halves of this stack. Deploying in ap-south-1 saves 35% on the transactional side, costs more on the analytics side, and costs more again on every gigabyte leaving the region.
The larger half deserves its own arithmetic rather than a paragraph here, and it already has one: what the analytics half costs running around the clock, including the difference between an always-on service and the active-hours figure a calculator presents on load.
If you are budgeting for both engines, the Postgres number is the smaller half of the problem. See which half of the bill you have not priced yet.
When should you choose ClickHouse Managed Postgres, and when should you not?
Choose it when the analytics integration is the point. Look elsewhere when the bill needs to be forecastable, when you need to go smaller than 4 GB, or when the database has to live in your own cloud account.
| Choose ClickHouse Managed Postgres if | Look elsewhere if |
|---|---|
| You are already on ClickHouse Cloud and analytics is the centre of gravity. | You need less than 4 GB of RAM. |
| You want CDC you do not have to build, run, or monitor. | You need real backup retention on the cheapest tier. |
| You would genuinely use cross-engine querying from Postgres. | You need the database inside your own AWS account. |
| The next twelve months matter more than month thirteen. | You need a bill you can forecast past general availability. |
The last row on the left is not a joke. Half price is half price, and if runway is what you are optimising, a beta discount is a real advantage.
Two strengths deserve stating plainly. CDC and pg_clickhouse are included at no extra cost during the beta, which is the single best reason to buy this product. And pg_clickhouse is not a token integration.
ClickHouse reports it as “the fastest PostgreSQL extension, outperforming all other Postgres analytics extensions” on ClickBench, running near-native ClickHouse speeds across all 42 queries. Worth noting, ClickBench is ClickHouse’s own benchmark. Not everything pushes down, though. The team puts full TPC-H pushdown at fourteen of twenty-two queries.
| Alternative | Best for | Trade-off |
|---|---|---|
| Selfhost.dev | Both engines on fixed per-instance pricing, in your own AWS account if you want. | No managed CDC and no pg_clickhouse, so cross-engine work is yours to wire. |
| Neon | Branching and serverless workflows on Postgres. | Storage priced well above block storage, and no analytics engine beside it. See what serverless Postgres costs in production. |
| AWS RDS | Deep AWS investment and compliance requirements. | A managed markup on every instance, and no analytics engine. |
| Layerbase | Small workloads on a flat monthly price. | Hobby to small scale, no configuration matching ClickHouse’s ladder, and no managed CDC. |
For the wider market rather than these four, we keep a running comparison of how managed Postgres prices at every size.
One number per provider, rather than a model: nine Neon alternatives priced on one database, 2 vCPU and 8 GB with 100 GB of storage, from $79 to $195 a month. Every rate behind those totals is published.
How does Selfhost.dev price managed Postgres differently?
The same 1 vCPU and 8 GB configuration with 60 GB of storage runs $46.81 a month in ap-south-1 and $61.46 in us-east-1, plus about $5 for the public IPv4 added at deploy. Billed hourly against prepaid credits, with no tiers.
| ClickHouse Managed Postgres | Selfhost.dev | |
|---|---|---|
| What the machine costs | $46.38/mo at GA Modelled from today’s price. $46.38 is today’s $23.19 with the 50% beta discount removed. Mumbai, 1 vCPU / 8 GB. | $46.81/mo, measured Mumbai, same spec. |
| What egress costs | $0 today No rate published for GA. | $0.15/GB, published |
| What backups cost | $0 today “Charges may apply at GA” | $0.05/GB per month, published |
| Can you size storage on its own? | No, bundled to the machine. | Yes, from 1 GB. |
| What storage you get | Local NVMe, faster. | Network gp3, separately sized. |
| When credit runs out | Metered account. | Resources pause, restart on top-up. |
| What comes with Postgres | Native CDC, pg_clickhouse. |
pgvector, TimescaleDB, 161 MCP tools. |
| Can you calculate next month’s bill today? | Not fully Three rates are unpublished. | Yes Every rate is published. |
We are not claiming a flat bill. We meter egress and backup storage too. The difference is not that our bill has no variable component. Ours is public. That is the entire difference: you can multiply our rates by your own traffic this afternoon, and theirs are switched off with no published number behind them.
Storage being sized on its own matters for the workload this category serves. A Postgres feeding an analytics pipeline is data-heavy and compute-light, and here you can buy the disk without the CPU to go with it. If the database must stay inside your own cloud account for residency reasons, that runs as a managed database in your own AWS account.
Where they are the better buy, plainly.Their CDC is managed and currently free, and ours is assembled from the standard ways to move Postgres data into ClickHouse. They have pg_clickhouse, and we have no equivalent. Their local NVMe is faster than our gp3. And on the smallest ap-south-1 configuration they are cheaper than us even after the beta ends, $46.38 against $46.81. If a small Postgres is all you need and you want the pipeline handled, buy theirs.
You should not have to deploy something to find out what it costs. Deploy a Postgres you already know the price of, billed by the hour, so if it turns out to be the wrong box, an hour is all you have paid for.
What should you budget for ClickHouse Managed Postgres?
Budget for roughly twice what the calculator shows today, then for three meters currently reading zero.
Choose it if you are already on ClickHouse Cloud, if managed CDC is worth real money, and if the next twelve months matter more than month thirteen. On those terms it is a good product at a genuinely low price.
Choose something else if you need less than 4 GB of RAM, if one day of backup retention is not enough, if the database has to live in your own cloud account, or if you need a number you can defend in a budget meeting after general availability.
The honest summary of ClickHouse Managed Postgres pricing is that the figure on the page is a beta price on the smaller half of a two-part bill. The larger half is not discounted, it moves the other way by region, and it is knowable. Price both halves before committing to either.
The reason teams stay on a bill they cannot forecast is that switching sounds like a project. It does not have to be yours. Send us what you run and get your numbers back, line by line. A Selfhost.dev engineer does the mapping, free, whether or not you switch.
Frequently Asked Questions
Is ClickHouse Managed Postgres free?
No. The service was free until usage metering began on 15 June 2026. All plans now carry a 50% beta discount, which puts the entry configuration of 1 vCPU, 8 GB RAM and 59 GB NVMe at $23.19 a month in ap-south-1 and $35.74 in us-east-1. Nothing in the configuration list is free.
Will ClickHouse Managed Postgres get more expensive?
Yes, in three ways ClickHouse documents. The 50% beta discount ends, “network egress pricing will be introduced after GA,” and “additional backup charges may apply at GA.” Removing the discount alone doubles the entry configuration. ClickHouse has not published a post-GA rate card, so the exact total is not yet knowable.
Does ClickHouse Managed Postgres charge for egress?
Not during the beta. ClickHouse’s documentation states that “network egress pricing will be introduced after GA” without naming a rate. The nearest published reference is their analytics product, where public internet egress is documented at $0.1152/GB for AWS US and priced at $0.1384/GB in ap-south-1.
How much does ClickPipes Postgres CDC cost?
ClickHouse charges $0.10 per GB for the initial load or a resync, then $0.20 per GB for continuous replication, plus dedicated compute per service at $0.10 an hour on Basic or $0.20 on Scale. Their documentation lists MySQL and MongoDB CDC as free in public beta and Postgres CDC as generally available with standard billing.
What is the cheapest ClickHouse Managed Postgres configuration?
$23.19 a month in ap-south-1, for 1 vCPU, 8 GB of RAM and 59 GB of NVMe on the memory-optimized profile. CPU-optimized at 2 vCPU and 4 GB costs more, at $30.40. Nothing in the list goes below 4 GB of RAM. Still comparing? The only rate that matters is the one you can look up. Start a Postgres whose bill you can total in advance.
Based on this page: ·
On now or still deciding?
What's the bill you're looking at?
Roughly how much a month, all in?
Matched to RDS, we bill 3.0x less in ap-south-1 (Mumbai) and 2.1x less in us-east-1.
2 vCPU / 4 GB with 20 GB: $24.54/mo in Mumbai, $35.27/mo in us-east-1, against an estimated $73.75/mo on RDS.
See a real RDS bill, before and after →Neon meters compute hours and sleeps. We bill one fixed hourly rate and never sleep.
{price} Same number in a quiet month and a launch month.
Price your size →Two ways off the Supabase bill and you can keep the Supabase stack.
Self-host Supabase on a project server from about $0.02/hr or move just the database to a dedicated Postgres. {price}
How self-hosted Supabase works here →An enterprise client is moving production ClickHouse to us at up to 60% less.
Worked example: off ClickHouse Cloud Scale to always-on managed ClickHouse, $891.86 to $364.03 a month, 59%.
See the ClickHouse bill, before and after →A PaaS bills per service. A project server is one bill for everything on it.
Worked example: a studio consolidated client hosting onto project servers, $390.00 to $82.66 a month, 78%.
See that bill, before and after →A managed database for as low as $5 a month. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price} Postgres and MySQL price the same.
Price your size →A managed database for as low as $5 a month. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price}
Price your size →A managed database for as low as $5 a month. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price} Pay-as-you-go credits, top up from $5, no plan tiers.
Price your size →Most setups map onto two shapes: dedicated databases on AWS and a project server for everything else.
{price} Project servers from about $0.02/hr.
Price your size →Under $200 a month, the calculator beats a human reply. Price it there first.
What's it for?
Where do your users mostly sit?
Dedicated managed Postgres or MySQL, with point-in-time restore, pooling and Multi-AZ failover when you want it.
{region} If you need scale-to-zero or instant branching, Neon fits better than we do.
What managed Postgres includes →Managed ClickHouse for events at volume or TimescaleDB on managed Postgres for time-series next to your app data.
Worked example: off ClickHouse Cloud Scale, $891.86 to $364.03 a month, 59%. {region}
See the ClickHouse bill, before and after →pgvector on managed Postgres: one database instead of a second vendor.
{region} TimescaleDB is one click away on the same instance if you also have time-series.
When a dedicated vector DB is worth it →A project server from about $0.02/hr: push to GitHub and it deploys, several apps and their databases on one box.
Auto-deploy on push, PR previews, custom domains. The $5 welcome credit covers the start of it, no card and you can pause it to $0.
How Projects work →Project servers: many sites per server, one bill.
Worked example: a studio consolidated client hosting, $390.00 to $82.66 a month, 78%.
See that bill, before and after →Most things fit dedicated databases on AWS plus a project server for the apps.
{region}
See it in the live demo →What are you trying to do?
Which editor?
We migrate you, free, on every plan size.
An engineer runs it with you: match the instance, replicate or dump and restore, test the restore, cut over.
See one migration, step by step →The Supabase stack, one click, on a server of your own.
One click from the template, on a project server from about $0.02/hr. Nothing to build or wire up.
The Supabase deploy guide →Paste one config and your editor can run the whole backend.
Run it once, sign in when the browser opens and all 189 tools register.
An hourly instance you pause when done.
Restore a snapshot into a second instance, point staging at it, pause it when idle.
Price a small instance →Push to GitHub and it's live: auto-deploy, PR previews, custom domains.
A project server from about $0.02/hr runs several apps and their databases.
Deploy guides by framework →The one that matters most:
A managed database for as low as $5 a month. Project servers from about $0.02 an hour.
The smallest dedicated Postgres, a t4g.nano with 1 GB, is about $5.34 a month in ap-south-1 (Mumbai) and about $6.41 in us-east-1 and the $5 welcome credit covers its first days. Pay-as-you-go credits, top up from $5, no tiers.
Price your size →When production needs help, you talk to the engineers who run it and a founder reads every request.
Outages, restores, performance issues and migrations reach the people operating the platform. No response-time promise or uptime percentage we cannot prove.
How support and recovery work →Failover, point-in-time restore and backups cover the common ways a database fails.
Multi-AZ failover is a toggle on every engine, Postgres and MySQL add point-in-time restore and all engines get automated backups, live metrics and alerts.
The reliability and recovery details →We migrate you, free. An engineer plans and runs the move with you.
Match the instance, replicate or dump and restore, test the restore, cut over. Any plan size, no extra cost.
See one migration, step by step →Run it in your own AWS account with BYOC, in the region you need.
Encryption in transit and at rest on every managed instance. We do not hold SOC 2 or HIPAA today and we will say so before you spend an hour.
What we can and cannot certify →Fair enough. The live demo is the fastest way to see it.
Or claim $5 to start, no card needed.
Watch the live demo →Our founder
You've already sent us your setup from this browser. A founder will reply to it; no need to send it twice.
Got it. I'll reply to within two working days, from my own inbox.
Noted. One note when it changes, nothing else.
Run managed Postgres, your way.
Dedicated PostgreSQL on AWS with PITR, connection pooling, Multi-AZ, pgvector and BYOC. From about $5/mo and it pauses at a zero balance so there are no surprise invoices. Limited-time offer: get $5 in free credit at signup, no card needed.
Based on this page: ·
On now or still deciding?
What's the bill you're looking at?
Roughly how much a month, all in?
Matched to RDS, we bill 3.0x less in ap-south-1 (Mumbai) and 2.1x less in us-east-1.
2 vCPU / 4 GB with 20 GB: $24.54/mo in Mumbai, $35.27/mo in us-east-1, against an estimated $73.75/mo on RDS.
See a real RDS bill, before and after →Neon meters compute hours and sleeps. We bill one fixed hourly rate and never sleep.
{price} Same number in a quiet month and a launch month.
Price your size →Two ways off the Supabase bill and you can keep the Supabase stack.
Self-host Supabase on a project server from about $0.02/hr or move just the database to a dedicated Postgres. {price}
How self-hosted Supabase works here →An enterprise client is moving production ClickHouse to us at up to 60% less.
Worked example: off ClickHouse Cloud Scale to always-on managed ClickHouse, $891.86 to $364.03 a month, 59%.
See the ClickHouse bill, before and after →A PaaS bills per service. A project server is one bill for everything on it.
Worked example: a studio consolidated client hosting onto project servers, $390.00 to $82.66 a month, 78%.
See that bill, before and after →A managed database for as low as $5 a month. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price} Postgres and MySQL price the same.
Price your size →A managed database for as low as $5 a month. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price}
Price your size →A managed database for as low as $5 a month. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price} Pay-as-you-go credits, top up from $5, no plan tiers.
Price your size →Most setups map onto two shapes: dedicated databases on AWS and a project server for everything else.
{price} Project servers from about $0.02/hr.
Price your size →Under $200 a month, the calculator beats a human reply. Price it there first.
What's it for?
Where do your users mostly sit?
Dedicated managed Postgres or MySQL, with point-in-time restore, pooling and Multi-AZ failover when you want it.
{region} If you need scale-to-zero or instant branching, Neon fits better than we do.
What managed Postgres includes →Managed ClickHouse for events at volume or TimescaleDB on managed Postgres for time-series next to your app data.
Worked example: off ClickHouse Cloud Scale, $891.86 to $364.03 a month, 59%. {region}
See the ClickHouse bill, before and after →pgvector on managed Postgres: one database instead of a second vendor.
{region} TimescaleDB is one click away on the same instance if you also have time-series.
When a dedicated vector DB is worth it →A project server from about $0.02/hr: push to GitHub and it deploys, several apps and their databases on one box.
Auto-deploy on push, PR previews, custom domains. The $5 welcome credit covers the start of it, no card and you can pause it to $0.
How Projects work →Project servers: many sites per server, one bill.
Worked example: a studio consolidated client hosting, $390.00 to $82.66 a month, 78%.
See that bill, before and after →Most things fit dedicated databases on AWS plus a project server for the apps.
{region}
See it in the live demo →What are you trying to do?
Which editor?
We migrate you, free, on every plan size.
An engineer runs it with you: match the instance, replicate or dump and restore, test the restore, cut over.
See one migration, step by step →The Supabase stack, one click, on a server of your own.
One click from the template, on a project server from about $0.02/hr. Nothing to build or wire up.
The Supabase deploy guide →Paste one config and your editor can run the whole backend.
Run it once, sign in when the browser opens and all 189 tools register.
An hourly instance you pause when done.
Restore a snapshot into a second instance, point staging at it, pause it when idle.
Price a small instance →Push to GitHub and it's live: auto-deploy, PR previews, custom domains.
A project server from about $0.02/hr runs several apps and their databases.
Deploy guides by framework →The one that matters most:
A managed database for as low as $5 a month. Project servers from about $0.02 an hour.
The smallest dedicated Postgres, a t4g.nano with 1 GB, is about $5.34 a month in ap-south-1 (Mumbai) and about $6.41 in us-east-1 and the $5 welcome credit covers its first days. Pay-as-you-go credits, top up from $5, no tiers.
Price your size →When production needs help, you talk to the engineers who run it and a founder reads every request.
Outages, restores, performance issues and migrations reach the people operating the platform. No response-time promise or uptime percentage we cannot prove.
How support and recovery work →Failover, point-in-time restore and backups cover the common ways a database fails.
Multi-AZ failover is a toggle on every engine, Postgres and MySQL add point-in-time restore and all engines get automated backups, live metrics and alerts.
The reliability and recovery details →We migrate you, free. An engineer plans and runs the move with you.
Match the instance, replicate or dump and restore, test the restore, cut over. Any plan size, no extra cost.
See one migration, step by step →Run it in your own AWS account with BYOC, in the region you need.
Encryption in transit and at rest on every managed instance. We do not hold SOC 2 or HIPAA today and we will say so before you spend an hour.
What we can and cannot certify →Fair enough. The live demo is the fastest way to see it.
Or claim $5 to start, no card needed.
Watch the live demo →Our founder
You've already sent us your setup from this browser. A founder will reply to it; no need to send it twice.
Got it. I'll reply to within two working days, from my own inbox.
Noted. One note when it changes, nothing else.