Confluent Pricing 2026: What a Confluent Cloud Cluster Costs Running 24/7
Confluent pricing starts at $0 a month on Basic and about $385 a month on Standard, but a Standard cluster that runs 24/7 pays $547.50 a month for one eCKU before any data moves. Confluent’s own pricing table says the ~$385 assumes the cluster is active about 70% of the time.
Pricing verified November 2026 · AWS us-east-1 · public list prices, pay-as-you-go
KEY FACTS
- Four serverless tiers: Basic starts at $0, Standard at ~$385, Enterprise at ~$895 and Freight at ~$2,300 a month.
- The 24/7 price is higher: one Standard eCKU is $0.75 × 730 hours = $547.50 a month, and the 99.99% SLA needs two eCKUs, $1,095.00 in compute.
- Storage is billed on three copies: Confluent bills the replicated volume, about 3x what you write.
- Basic is small: one Basic eCKU covers 20 client connections, 30 partitions and 5 MBps of writes.
- At 1 MB/s, a Standard cluster costs $711.26 a month with Confluent’s own estimator assumptions. Selfhost.dev runs the same workload on three
t4g.largebrokers across three zones for $224.87, plus S3 requests.- Method: list prices, pay-as-you-go, 730 hours a month, consumers in the same AWS region.
Selfhost.dev, a managed database platform on AWS, runs Kafka-compatible brokers with topic data in S3, so every Confluent bill below sits next to a Selfhost.dev bill for the same setup and region.
Table of Contents
How much does Confluent Cloud cost per month?
A Confluent Cloud Standard cluster running 24/7 at 1 MB/s costs $711.26 a month in AWS us-east-1, against Confluent’s quoted starting price of about $385. Basic costs $163.76 for the same traffic if the cluster fits one eCKU. Selfhost.dev runs the workload on three t4g.large brokers across three zones for $224.87, plus S3 requests.
An eCKU, or Elastic Confluent Unit for Kafka, is Confluent’s unit of cluster capacity: Basic, Standard, Enterprise and Freight clusters bill by the number of eCKUs used each hour.
How every bill in this post is priced (checked 18 November 2026)
- AWS us-east-1, list prices, pay-as-you-go, running 24/7, 730 hours a month
- Write rate of 1 MB/s (binary megabytes, the unit Confluent bills in)
- Each message read by three consumer groups and compressed 4:1, the defaults behind Confluent’s own Cost Estimator
- 7 days of retention
- Up to 250 partitions and 1,000 client connections, so one Standard eCKU covers the cluster’s limits
- Consumers run in the same AWS region as the cluster
- Units: MB/s, GB and TB are binary (MiB/s, GiB, TiB), the units Confluent bills in. Selfhost.dev states its egress rate per GB without naming the unit, so the one egress figure is shown under both readings
- Sources: Confluent rates from Confluent’s pricing page and docs; Selfhost.dev prices from its public calculator; S3 request costs measured on our own test clusters and marked as estimates
| Option (1 MB/s, us-east-1) | Quoted starting price | Real monthly cost, 24/7 | Uptime SLA / availability |
|---|---|---|---|
| Confluent Basic, 1 eCKU (up to 20 connections, 30 partitions, 5 MBps of writes) | $0 | $163.76 | 99.5% |
| Confluent Standard, 1 eCKU | ~$385 | $711.26 | 99.9% |
| Confluent Standard, 2 eCKUs | ~$385 | $1,258.76 | 99.99% |
Selfhost.dev managed Kafka, 1 broker (t4g.medium, dev and test only) | $40.31 all-in before topic data | $44.91 | No published SLA; one availability zone |
Selfhost.dev managed Kafka, 3 brokers across 3 zones (t4g.large) | $210.09 + IPv4 | $224.87 + S3 requests | No published SLA; survives the loss of one zone |
Basic working: first eCKU free, traffic $128.32 + replicated storage $35.44 = $163.76; a second eCKU (over 20 connections, 30 partitions or 5 MBps of writes) adds $102.20. Standard working is in the worked bills below.
Selfhost.dev broker sizes are our recommendation for each workload (t4g.large up to 5 MB/s, t4g.xlarge at 20 MB/s); 5 and 20 MB/s have not been load-tested.
What is matched and what differs.
- Matched: region, workload, retention and list prices on both sides.
- Capacity: Confluent bills elastic eCKUs; Selfhost.dev managed Kafka bills fixed instances, so the broker count and size are chosen at create.
- Included in the Selfhost.dev totals: one public IPv4 per broker at $4.93 a month.
- Not included: S3 requests, which bill on usage. On our test clusters they cost about $21 a month at 1 MB/s at AWS rates, before our margin, which puts an illustrative 1 MB/s total near $245.87.
- Availability: three brokers run one per availability zone with data in S3, a multi-zone design like Confluent Standard’s.
Why is Confluent Cloud pricing higher than the starting price?
Confluent Cloud pricing runs above its starting price for four reasons: the ~$385 Standard figure assumes 70% uptime, storage is billed on three replicated copies, Basic’s free eCKU covers only 20 client connections or 30 partitions, and volume discounts begin at 250 TB of monthly traffic. Each one is in Confluent’s own pricing page or documentation.
Why does the ~$385 Confluent Standard price assume 70% uptime?
Confluent’s ~$385 Standard price assumes the cluster is active about 70% of the time, according to the note under its pricing table. A Standard cluster serving traffic all month pays the full eCKU rate: $0.75 × 730 hours = $547.50 for one eCKU, and $1,095.00 in compute for the two eCKUs the 99.99% SLA requires.
Confluent’s pricing table states it plainly: “Assumes 70% utilization, i.e., clusters are active ~70% of the time.” The arithmetic follows: $547.50 × 0.70 = $383.25, which rounds to the published ~$385. A cluster only bills nothing at zero consumption across every dimension, which means no topics and no partitions, so a production cluster never reaches it.
Is Confluent Cloud storage billed before or after replication?
Confluent Cloud bills storage after replication, on about three times the data you write. The pricing page labels $0.08 per GB-month “pre-replication”, but the billing docs and billing FAQ charge the post-replication volume. At 1 MB/s with 7 days kept, Confluent storage costs $35.44 a month, not $11.81. Selfhost.dev stores the same topic data once in S3 for $4.60.

Confluent’s billing FAQ answers the question directly. Under “Why am I charged for storage when I have a replication factor of three?” it says: “Confluent Cloud charges for the total post-replication volume of data stored.” The billing dimensions page adds that billed storage “is typically about three times the volume you write.”
The working for the 1 MB/s bill: 0.25 MiB/s after 4:1 compression × 604,800 seconds = 147.66 GiB kept, × 3 copies × $0.08 = $35.44.
Brokers that keep topic data in S3 store each byte once. S3 provides the durability of that copy, broker availability comes from running three brokers across zones, and neither is a published uptime SLA. why replication factor 1 is safe when topic data lives in S3 covers what happened when we killed a broker on that setup.
How many eCKUs does a Confluent Basic cluster need?
A Confluent Basic cluster needs one eCKU for every 20 client connections, 30 partitions or 5 MBps of writes, whichever limit it reaches first. The first Basic eCKU is free and each extra eCKU costs $0.14 × 730 hours = $102.20 a month. An app with 40 connections pays for two.
Confluent bills each hour on the highest eCKU count used in that hour (cluster limits), so a short spike in connections sets the price for the whole hour. Standard eCKUs are far larger: 1,000 client connections, 250 partitions and 25 MBps of writes each.
Do Confluent volume discounts apply to small teams?
Confluent’s volume discounts do not reach small teams on pay-as-you-go. Standard data in and out costs $0.050 per GB up to 250 TB of total monthly traffic, and the lower rates down to $0.035 apply above that. Confluent’s discount table adds that discounts are not automatically applied and arrive when a new committed term is signed.
A 1 MB/s workload moves about 2.5 TB a month, roughly 1% of the first discount band. The published range of $0.035 to $0.050 per GB is a volume ladder, not a regional spread.
Your actual Kafka bill depends on throughput, broker size, retention and deployment region. We’ve preloaded the three-broker configuration used in this comparison so you can change the workload and see how the monthly price changes: price this exact cluster, no signup
When is Confluent Cloud worth the price?
Confluent Cloud is worth the price when the platform around Kafka matters more than the broker bill: 80+ fully managed connectors, managed Apache Flink, Stream Governance, multi-cloud clusters on AWS, Azure and Google Cloud, and a published 99.99% uptime SLA from two eCKUs. Basic also suits development inside its 20-connection limit.
- If your pipelines depend on managed connectors, Confluent runs 80+ of them, billed per task-hour and per GB. That saves building and operating Kafka Connect yourself.
- If you need stream processing next to the broker, Confluent bills managed Flink per CFU-minute on the same account.
- If you run on more than one cloud, Confluent places clusters on AWS, Azure and Google Cloud under one bill.
- If very high throughput with relaxed latency is the job, Freight writes straight to object storage at $0.014 to $0.030 per GB of traffic, with latency of about 1 to 2 seconds.
- If a contractual 99.99% SLA is a hard requirement, Standard and Enterprise publish one from two eCKUs.
If none of those apply, the bill is mostly brokers, storage and traffic, and Kafka-compatible alternatives that keep your client code price those parts differently.
How much does Confluent Kafka cost at 1, 5 and 20 MB/s?
Confluent Cloud Standard costs $711.26 a month at 1 MB/s, $1,366.29 at 5 MB/s and $3,822.66 at 20 MB/s, on one eCKU running 24/7 in AWS us-east-1. Selfhost.dev costs $224.87, $243.18 and $510.64 on three brokers across three zones, plus S3 requests. The 99.99% SLA adds $547.50 to every Confluent row.
Every figure below uses the assumptions in the box above. Data in and out follows Confluent’s estimator: each MB written is read three times and compressed 4:1, so billed traffic equals the uncompressed write volume. Confluent’s Cost Estimator uses the same fan-out and compression but returns a savings percentage against self-run Apache Kafka, not a monthly bill, and it does not price storage. The tables below finish that calculation.
Confluent pricing example at 1 MB/s
| Option | Compute | Data in + out | Storage | Total / month |
|---|---|---|---|---|
| Confluent Standard, 1 eCKU (99.9%) | $547.50 | $128.32 | $35.44 | $711.26 |
| Confluent Standard, 2 eCKUs (99.99%) | $1,095.00 | $128.32 | $35.44 | $1,258.76 |
Selfhost.dev, 3 × t4g.large across 3 zones, consumers in AWS us-east-1 | $213.47 | $0.00 on Selfhost.dev | $11.40 | $224.87 + S3 requests (about $21 at AWS cost) |
| Selfhost.dev, same cluster, consumers outside AWS | $213.47 | $230.98 if billed per GiB, $248.01 per decimal GB (1,924.8 GiB of reads × $0.12) | $11.40 | $455.85 (GiB) or $472.88 (decimal GB) + S3 requests |
Confluent working: compute $0.75 × 730 = $547.50. Traffic 1 MiB/s × 2,628,000 s = 2,566.4 GiB × $0.05 = $128.32. Storage 147.66 GiB × 3 copies × $0.08 = $35.44. Selfhost.dev working: brokers $198.69 + three public IPv4 at $4.93 = $213.47; disks $6.80 + 148 GB of topic data in S3 at $0.031 per GB-month = $4.60; from the Selfhost.dev calculator. Outside-AWS reads: three consumer groups × 0.25 MiB/s compressed × 2,628,000 s = 1,924.8 GiB.
Confluent pricing example at 5 MB/s
| Option | Compute | Data in + out | Storage | Total / month |
|---|---|---|---|---|
| Confluent Standard, 1 eCKU (99.9%) | $547.50 | $641.60 | $177.19 | $1,366.29 |
| Confluent Standard, 2 eCKUs (99.99%) | $1,095.00 | $641.60 | $177.19 | $1,913.79 |
Selfhost.dev, 3 × t4g.large across 3 zones | $213.47 | $0.00 on Selfhost.dev | $29.71 | $243.18 + S3 requests (not measured at 5 MB/s) |
Confluent working: traffic 12,832.0 GiB × $0.05 = $641.60. Storage 738.28 GiB × 3 × $0.08 = $177.19. Selfhost.dev working: brokers $198.69 + three IPv4 $14.78 = $213.47; disks $6.80 + 738 GB in S3 $22.91 = $29.71.
Confluent pricing example at 20 MB/s
| Option | Compute | Data in + out | Storage | Total / month |
|---|---|---|---|---|
| Confluent Standard, 1 eCKU (99.9%) | $547.50 | $2,566.41 | $708.75 | $3,822.66 |
| Confluent Standard, 2 eCKUs (99.99%) | $1,095.00 | $2,566.41 | $708.75 | $4,370.16 |
Selfhost.dev, 3 × t4g.xlarge across 3 zones | $412.15 | $0.00 on Selfhost.dev | $98.49 | $510.64 + S3 requests (about $47 at AWS cost) |
Confluent working: traffic 51,328.1 GiB × $0.05 = $2,566.41. Storage 2,953.13 GiB × 3 × $0.08 = $708.75. At 20 MB/s the compressed traffic is 5 MBps in and 15 MBps out, inside one Standard eCKU’s 25 and 75 MBps limits. Selfhost.dev working: brokers $397.37 + three IPv4 $14.78 = $412.15; disks $6.80 + 2,953 GB in S3 $91.69 = $98.49.
What is matched and what differs.
- Matched: write rate, fan-out, compression, retention, region and list prices.
- Capacity: Confluent eCKUs grow on their own; Selfhost.dev brokers are a fixed size chosen at create.
- Sizes:
t4g.largefor 1 and 5 MB/s andt4g.xlargefor 20 MB/s are our recommendation; 5 and 20 MB/s have not been load-tested, andt4g.mediumsuits development and testing only. - S3 requests: billed on usage outside the calculator, at AWS cost plus our margin, mostly a fixed baseline: about $17 a month idle, $21 at 1 MB/s and $47 at 17 to 20 MB/s on our test clusters.
- Traffic in the region: free on Selfhost.dev between clients and brokers, across zones too; AWS may bill your own account about $0.01 per GB when a consumer sits in another zone.
The one trade-off to check before switching. Consumers outside AWS change the Selfhost.dev bill more than any other line: internet egress at $0.12 per GB adds $230.98 a month at 1 MB/s ($248.01 if the GB is decimal), the second Selfhost.dev row above. Confluent’s $0.050 per GB applies to traffic within the same cloud region, and Confluent prices cross-region and cross-cloud traffic separately.
Want to see whether the same setup works for your workload? Open the managed Kafka calculator, adjust your throughput and broker configuration, and get your estimated monthly cost without signing up. Prefilled with the bills above: 1 MB/s · 5 MB/s · 20 MB/s.
What costs extra in Confluent Cloud pricing, from Schema Registry to connectors?
Confluent Cloud includes a Schema Registry free up to 100 schemas with a 99.5% uptime SLA; each schema after that costs $1.46 a month, and a 99.99% Schema Registry costs $730 a month on Stream Governance Advanced. Connectors, Flink and support bill separately. Selfhost.dev managed Kafka includes Schema Registry at no charge.
| Cost item | Confluent Cloud | Selfhost.dev managed Kafka |
|---|---|---|
| Schema Registry, up to 100 schemas | Free (Essentials, 99.5% SLA) | Included, no charge on the recommended t4g.large brokers (needs 8 GB) |
| 200 schemas | 100 extra × $0.002 × 730 = $146.00 a month | Included, no charge |
| Schema Registry with 99.99% SLA | Advanced, $1 an hour = $730 a month | No published SLA; runs on one broker or three |
| Storage | Billed on ~3 replicated copies at $0.08 per GB-month | Topic data in S3, billed once at $0.031 per GB-month |
| Security | TLS, ACLs; RBAC from Standard | TLS, SASL/SCRAM and ACLs by default |
| Stream processing | Flink per CFU-minute; ksqlDB per CSU-hour | Topics readable by managed ClickHouse on the same bill |
| Billing increment | Usage under an hour billed as a full hour | Billed by the hour against prepaid credits |
Every schema version counts toward Confluent’s 100, including soft-deleted versions. Twenty topics with a key and a value schema, each at three versions, already make 120.
Selfhost.dev managed Kafka starts at $40.31 a month for a one-broker development cluster (t4g.medium, AWS us-east-1, before topic data), or $44.91 with 7 days of 1 MB/s data. A production cluster of three t4g.large brokers across three zones carrying 1 MB/s costs $224.87 a month, plus S3 requests. The brokers speak the Kafka 3.9.1 protocol on an AutoMQ engine, keep topic data in S3 and show throughput, partitions and consumer-group lag in the console. Teams that also run analytics can read the same topics into ClickHouse on one bill.
See it before you price it. The console walkthrough shows a Kafka cluster from create to first message in a few minutes, with no account: watch the walkthrough, then compare plans on managed Kafka with topic data in S3.
Why is Confluent Cloud so expensive as a workload grows?
A Confluent Cloud bill climbs when traffic, retention or availability changes, because each one is metered separately. On the 1 MB/s Standard cluster, one more consumer group adds $32.08 a month, moving from 7 to 30 days of retention adds $116.44, and the 99.99% SLA adds $547.50.
| Change to the 1 MB/s Standard cluster | Added each month | Working |
|---|---|---|
| One more consumer group | $32.08 | 641.6 GiB more egress × $0.05 |
| Retention from 7 to 30 days | $116.44 | 632.81 GiB × 3 × $0.08 = $151.88, minus $35.44 |
| 99.99% SLA (second eCKU) | $547.50 | $0.75 × 730 |
| 200 schemas instead of 100 | $146.00 | 100 × $0.002 × 730 |
| Basic cluster passing 20 connections | $102.20 per extra eCKU | $0.14 × 730 |
A usage-based bill moves with every one of those dials, which is the spread Bill Variance measures from a quiet month to a busy one.
The price guarantee has conditions. Confluent advertises that it will beat any hyperscaler on cost. Its terms limit the guarantee to new enterprise customers, exclude add-ons such as connectors, Stream Governance, stream processing and Tableflow, and set the remedy at a $500 gift card or charity donation if Confluent cannot match the price.
Renewals run on committed spend. IBM completed its acquisition of Confluent on 17 March 2026. Confluent’s discounts come from annual commitments to a minimum spend across Kafka, connectors, Flink, Stream Governance and support, so a renewal is when a bill gets re-priced.
Already paying Confluent? Send us your current invoice and we will price the same workload line by line, free: get a line-by-line audit of your Confluent bill. New accounts also start with $5 of credit, about four days of a one-broker test cluster in the calculator’s estimate.
What is Confluent Platform pricing for the self-managed version?
Confluent Platform, the self-managed version, has no public price list; licences are quoted through Confluent sales. Third-party trackers put annual Platform subscriptions between $50,000 and $500,000 or more, depending on cluster size, features and support level. Confluent Cloud is the only Confluent product with a public rate card.
- Vendr, a software purchasing tracker, reports Platform subscriptions from $50,000 to $500,000 or more a year (third-party data).
- Factor House reports a similar $50,000 to $500,000+ range, licensed per environment (third-party).
- A 2020 r/apachekafka thread quotes a $90,000-a-year minimum for an on-premises cluster of three brokers (a six-year-old forum report).
Confluent Platform offers a 30-day free trial of its enterprise features. If you run Kafka on your own servers today, Confluent Cloud and managed Kafka-compatible services both remove the broker operations that a Platform licence still leaves with you.
Frequently asked questions
Is Confluent Kafka free or paid?
Confluent Cloud is not free beyond its trial. New sign-ups receive $400 of credit to use in their first 30 days. After that, Basic clusters bill $0 only at zero consumption, meaning no topics, partitions or connections, and every cluster with traffic pays for data in, data out and replicated storage at list prices.
Is Confluent owned by IBM?
Yes. IBM completed its acquisition of Confluent on 17 March 2026, and Confluent’s pricing page now carries “Confluent, an IBM company”. Confluent Cloud’s public rates did not change at the close: Standard is still $0.75 per eCKU-hour, $0.050 per GB of traffic and $0.08 per GB-month of storage.
Is Confluent Cloud the same as Kafka?
Confluent Cloud is a managed service built on Apache Kafka, run by Confluent on its Kora engine, so Kafka clients connect to it unchanged. Apache Kafka itself is free open-source software. Confluent Cloud adds managed operations, connectors, Flink and governance, and bills eCKUs, traffic and replicated storage for the service.
What is a CKU in Confluent Cloud pricing?
A CKU, or Confluent Unit for Kafka, is the fixed capacity unit for Dedicated clusters; an eCKU is the elastic version Confluent bills on Basic, Standard, Enterprise and Freight. Each hour bills the highest eCKU count used. One Standard eCKU allows 25 MBps of writes, 1,000 client connections and 250 partitions, at $0.75 an hour.
Is Confluent’s Schema Registry free?
Confluent’s Schema Registry is free on the Essentials package up to 100 schemas, with a 99.5% uptime SLA. Each schema above 100 costs $0.002 an hour, or $1.46 a month, so 200 schemas cost $146.00 a month. A 99.99% Schema Registry needs Stream Governance Advanced, from $1 an hour.
How does Confluent pricing compare to Amazon MSK?
Amazon MSK bills brokers by the hour instead of eCKUs and traffic. Three kafka.m7g.large brokers cost $0.204 × 730 × 3 = $446.76 a month in us-east-1 before storage, against $547.50 for one Confluent Standard eCKU before traffic and storage. MSK Serverless starts at $0.75 per cluster-hour.
What is Confluent enterprise pricing?
Confluent enterprise pricing means two different things. The Enterprise cluster tier costs $1.75 to $2.25 per eCKU-hour, so one eCKU running 24/7 costs $1,277.50 to $1,642.50 a month before traffic and storage, against a quoted ~$895 at 70% uptime. Enterprise contracts and Confluent Platform licences are quoted by sales.
What is a cheaper alternative to Confluent Cloud for a small workload?
For 1 MB/s in AWS us-east-1, Selfhost.dev managed Kafka costs $224.87 a month plus S3 requests on three Kafka-compatible t4g.large brokers across three zones, against $711.26 for Confluent Cloud Standard. Amazon MSK costs $446.76 for three kafka.m7g.large brokers before storage. Confluent Basic costs $163.76 if the cluster fits one eCKU.
Confluent Cloud or Selfhost.dev managed Kafka: which to choose

Choose Confluent Cloud if managed connectors, Flink, multi-cloud placement or a contractual 99.99% SLA carry your architecture. Those are real reasons to pay $547.50 or more per eCKU, and Basic stays a fair place to prototype inside its limits.
Choose Selfhost.dev if your Kafka bill is mostly brokers, storage and traffic, and your consumers run in AWS. The same 1 MB/s workload costs $224.87 a month plus S3 requests on three t4g.large brokers across three zones, with Schema Registry included and topic data billed once in S3.
Run the cluster you just priced. The $5 sign-up credit covers about four days of a one-broker test cluster, with no card: deploy managed Kafka in the console.
Keep reading: Kafka alternatives that keep your client code · Kafka replication factor: when 1 is safe · ClickHouse Kafka engine: secure setup and 5 silent failures
Sources (checked 18 November 2026)
- Confluent pricing page: https://www.confluent.io/pricing/
- Billing dimensions: https://docs.confluent.io/cloud/current/billing/dimensions/overview.html
- Billing FAQ: https://docs.confluent.io/cloud/current/billing/billing-faq.html
- Manage Billing: https://docs.confluent.io/cloud/current/billing/overview.html
- Cluster types and limits: https://docs.confluent.io/cloud/current/clusters/cluster-types.html
- Stream Governance packages: https://docs.confluent.io/cloud/current/stream-governance/packages.html
- Schema Registry pricing: https://docs.confluent.io/cloud/current/get-started/schema-registry.html
- Price guarantee terms: https://www.confluent.io/legal/price-guarantee-challenge-terms-and-conditions/
- IBM closing announcement: https://newsroom.ibm.com/2026-03-17-ibm-completes-acquisition-of-confluent,-making-real-time-data-the-engine-of-enterprise-ai-and-agents
- Amazon MSK pricing: https://aws.amazon.com/msk/pricing/
- Selfhost.dev pricing calculator: https://selfhost.dev/pricing/
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 managed server: a European 8 GB server is $0.03/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 →Managed PostgreSQL from $8.10 a month in Mumbai. 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 →Managed PostgreSQL from $8.10 a month in Mumbai. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price}
Price your size →Managed PostgreSQL from $8.10 a month in Mumbai. 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 in Europe.
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 in Europe: 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 needed; it bills by the hour.
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. A European 8 GB server is $0.03/hr. Nothing to build or wire up.
Self-hosted Supabase in one click →Paste one config and your editor can run the whole backend.
Run it once, sign in when the browser opens and all 269 tools register.
An hourly instance you stop when you are done.
Restore a snapshot into a second instance, point staging at it and stop it when idle: only its storage bills while it is stopped.
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 in Europe runs several apps and their databases.
Deploy guides by framework →The one that matters most:
Managed PostgreSQL from $8.10 a month in Mumbai. Project servers from about $0.02 an hour in Europe.
The smallest dedicated Postgres, a 1 GB t4g.micro with 1 GB of storage, is $8.10 a month in ap-south-1 (Mumbai) and $10.55 in us-east-1; the $5 welcome credit goes toward it. 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 Postgres, MySQL, Redis and ClickHouse and a cluster you pick at create on OpenSearch; Postgres and MySQL add point-in-time restore and every engine gets 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 at rest on every managed instance; client TLS is a switch on PostgreSQL, MySQL and ClickHouse and always on for OpenSearch. 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 the database you just read about.
Dedicated managed PostgreSQL, MySQL, Redis, ClickHouse, OpenSearch or Kafka on AWS, run for you. PostgreSQL and MySQL from $8.10/mo and Redis from $5.34/mo in Mumbai (ap-south-1), ClickHouse and OpenSearch from a 4 GB instance; pay only for what you run, with 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 managed server: a European 8 GB server is $0.03/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 →Managed PostgreSQL from $8.10 a month in Mumbai. 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 →Managed PostgreSQL from $8.10 a month in Mumbai. Dedicated Postgres or MySQL on AWS, with restore, pooling and Multi-AZ failover when you want it.
{price}
Price your size →Managed PostgreSQL from $8.10 a month in Mumbai. 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 in Europe.
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 in Europe: 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 needed; it bills by the hour.
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. A European 8 GB server is $0.03/hr. Nothing to build or wire up.
Self-hosted Supabase in one click →Paste one config and your editor can run the whole backend.
Run it once, sign in when the browser opens and all 269 tools register.
An hourly instance you stop when you are done.
Restore a snapshot into a second instance, point staging at it and stop it when idle: only its storage bills while it is stopped.
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 in Europe runs several apps and their databases.
Deploy guides by framework →The one that matters most:
Managed PostgreSQL from $8.10 a month in Mumbai. Project servers from about $0.02 an hour in Europe.
The smallest dedicated Postgres, a 1 GB t4g.micro with 1 GB of storage, is $8.10 a month in ap-south-1 (Mumbai) and $10.55 in us-east-1; the $5 welcome credit goes toward it. 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 Postgres, MySQL, Redis and ClickHouse and a cluster you pick at create on OpenSearch; Postgres and MySQL add point-in-time restore and every engine gets 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 at rest on every managed instance; client TLS is a switch on PostgreSQL, MySQL and ClickHouse and always on for OpenSearch. 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.