Confluent Cloud pricing, and running Kafka without it
Apache Kafka with Connect and a schema registry, designed around your workload and run 24/7 in our cloud, your cloud account or your data center.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Apache Kafka
Confluent Cloud is Confluent's fully managed Apache Kafka service. OSStend runs upstream Apache Kafka with Kafka Connect and a schema registry in your own cloud account, its own cloud or your data center, for enterprises that want open source Kafka without the cost and ownership questions around Confluent. Brokers and partitions are designed for the estate, mirroring keeps both sides live during the move, and AceMQ engineers run it 24/7.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
Confluent and OSStend at a glance
Confluent is a commercial platform built around Kafka, sold as a cloud service and as self-managed software. OSStend runs the upstream Apache Kafka for you and tailors the cluster to the workload.
| OSStend | Confluent | |
|---|---|---|
| What you run | Upstream Apache Kafka with Connect and a schema registry | Confluent's commercial Kafka platform |
| Where it runs | Our cloud, your AWS, Azure or Google Cloud account, your data center | Confluent Cloud, Confluent Platform, Confluent Private Cloud and WarpStream BYOC (Confluent) |
| Who runs it | Named AceMQ engineers, 24/7 | Confluent, for its cloud service |
| Migration | Mirroring keeps both sides live; OSStend owns the cutover | Your team plans and runs it |
| Pricing | Price drivers on pricing; sized per design | Set by Confluent; its pricing page lists Cloud tiers from $0 (Basic), about $385 (Standard) and about $895 (Enterprise) a month (Confluent pricing) |
Sources: Confluent pricing, checked 17 Nov 2026. "From" prices are the page's "starting at" figures for Confluent Cloud; usage adds to them.
Confluent Cloud pricing: eCKUs, storage and networking
Confluent Cloud bills a cluster type's hourly rate per eCKU (elastic capacity unit), plus data in and out and data stored. Confluent's page lists the rates below, and its own note says the starting monthly costs assume 70% utilization.
| Cluster type | Starting cost a month | Per eCKU-hour | Data in or out, per GB | Stored, per GB-month | Uptime SLA |
|---|---|---|---|---|---|
| Basic | $0 | First eCKU free, then $0.14 | $0.05 | $0.08 | 99.5% |
| Standard | About $385 | $0.75 | $0.035 to $0.050 | $0.08 | 99.9% on 1 eCKU, 99.99% on 2 or more |
| Enterprise | About $895 | $1.75 to $2.25 | $0.020 to $0.050 | $0.08 | 99.9% on 1 eCKU, 99.99% on 2 or more |
| Freight | $2,300 | $2.25, minimum 2 eCKUs | $0.014 to $0.030 | $0.03 | 99.99% |
| Dedicated | Not stated; contact Confluent | Not stated | Not stated | Not stated | Not stated |
Source: Confluent pricing, checked 17 Nov 2026. Confluent states the prices are pre-replication and vary by cloud region. Arithmetic, not a Confluent figure: one Standard eCKU at $0.75 for about 70% of a 730-hour month is roughly $383, which is how the page's "about $385" reads.
Where Confluent Cloud is the better choice: a small or spiky workload that fits Basic or Standard, a team that wants Confluent's managed connectors and platform features, and anyone who prefers a usage bill to sizing brokers. Dedicated Kafka in your own cloud is worth pricing when throughput and retention are large and steady. To compare, price the same shape on both sides: see what the price depends on.
Why teams compare Confluent Cloud with Kafka in their own cloud
Two reasons come up: cost at scale, and the ownership change. IBM completed its acquisition of Confluent in March 2026, and some teams want to know what that means for bundling and future price changes.
- Ownership.
- Techzine reported the completed IBM acquisition in March 2026 (Techzine, checked 30 Oct 2026). Commentary on what it means for customers exists, for example from the Kafka tooling vendor Conduktor; a vendor blog is one view, not a forecast.
- Cost at scale.
- Teams with large, steady throughput compare their platform bill with the price of dedicated Kafka sized to the load.
- Place.
- Some estates need Kafka in a data center or an account that Confluent's cloud service does not cover.
A fair snapshot of Confluent
Confluent is the Kafka company's commercial platform, and it covers more deployment shapes than a single cloud service. For teams that want the full platform and accept the cost, it remains a strong choice.
- ✓It offers Confluent Cloud, Confluent Platform, Confluent Private Cloud and WarpStream BYOC (Confluent, checked 17 Nov 2026).
- ✓It has deep Kafka expertise and a large platform around the core broker.
- ✓If your applications use features that exist only in Confluent's platform, moving needs a replacement plan. The design review lists them before anything is built.
Full comparison: OSStend and Confluent
OSStend is listed first. The Confluent column states product facts from its public pages with the date checked.
| Factor | OSStend | Confluent |
|---|---|---|
| Good fit | Kafka estates that need a topology, broker count or place a platform plan does not give; cost-sensitive large clusters | Teams that want Confluent's full platform and accept the cost |
| Poor fit | Teams that depend on Confluent-only features, free tiers, self-serve sign-up | Teams that want plain open source Kafka run to their own design |
| Where it runs | Our cloud, your cloud account, your data center, Kubernetes or OpenShift | Confluent Cloud, Confluent Platform, Confluent Private Cloud and WarpStream BYOC (Confluent) |
| Tailoring | Broker count and partition plan designed for the estate; KRaft-mode clusters; Connect and schema registry included | Within the platform's plans and settings |
| Migration | Mirroring keeps both clusters live; OSStend runs and owns the cutover | Your team plans and runs it |
| Service levels | Written SLA per plan (see service levels) | Confluent Cloud lists uptime SLAs by tier: 99.5% on Basic; 99.9% on one eCKU or 99.99% on two or more on Standard and Enterprise; 99.99% on Freight (Confluent pricing, checked 17 Nov 2026) |
| Pricing model | Price drivers: size, SLA tier, where it runs. See pricing | Cloud tiers with starting prices; usage adds to them (Confluent pricing) |
Sources: Confluent pricing, checked 17 Nov 2026, and Techzine, checked 30 Oct 2026. The "within the platform's plans" tailoring cell is descriptive.
How OSStend does it
OSStend runs upstream Apache Kafka. The cluster is designed for your topic estate, moved with mirroring and run by named engineers. The first step is a 45-minute workload review with an engineer: the current setup is reviewed, the design is sketched, and a price follows for that design.
Managed Kafka includes Kafka Connect and a schema registry, and can run in your own AWS account. Because it is upstream open source, no vendor can change the licence or the price of what you run. Debezium connectors for change data capture are run through managed Debezium.
Contact us if
- ✓Your Kafka bill grows faster than your traffic and you want a design you can price.
- ✓You need Kafka in your own cloud account or a data center.
- ✓You want RabbitMQ and Kafka on one contract and one on-call team.
Not a fit if
- ✕Your applications depend on Confluent-only features and you plan to keep them.
- ✕You want a free tier, a card sign-up or a fully serverless service with no design step.
What dedicated Kafka costs instead: what the price depends on
Confluent sets its own prices; OSStend prices the design. The drivers are the broker count and size, storage and retention, the service level tier and where the cluster runs.
Prices are quoted per design, after the workload review, so the figure is for the cluster you need rather than a plan size. Send the engine, rough size and where it must run, and the engineer prices that design.
To compare, take your throughput, retention and connector count and price the same shape on both sides. Details are on pricing.
Fair notes on other options
Besides OSStend, teams moving off Confluent usually consider Amazon MSK, another managed Kafka vendor or a Kafka-compatible engine.
- Amazon MSK.
- AWS documents 30 brokers per cluster on ZooKeeper and 60 on KRaft, and a maximum number of partitions per broker above which the configuration cannot be changed (AWS docs, checked 30 Oct 2026). It runs on AWS only.
- Instaclustr.
- Lists Apache Kafka and Kafka Connect on its platform page and shows AWS, Azure, Google Cloud and on-prem as providers (platform and pricing pages, checked 1 Nov 2026). RabbitMQ is not on that list.
- Kafka-compatible engines
- such as Redpanda are a different product from Apache Kafka, and suit teams ready to change engine.
How to choose
Choose by what you depend on and what you must control. Staying put is right when the platform features are in use and the price is accepted.
- If you use Confluent-only features and accept the cost, stay on Confluent.
- If you want upstream Kafka to your own design, in your account or data center, choose OSStend.
- If you run only on AWS and fit MSK's limits, compare Amazon MSK.
- If you run RabbitMQ next to Kafka, OSStend covers both on one contract.
Migration path from Confluent
The new cluster is built to the signed-off design, mirrored from the Confluent cluster, and verified before clients switch. Both stay live until cutover. The detail is in the Confluent to Apache Kafka migration guide.
Review
Topics, partitions, retention, connectors, schemas and any Confluent-only features in use.
Design
Broker count, partition plan, Connect and schema registry layout, and where the cluster runs.
Mirror
Topics and offsets are mirrored to the new cluster while Confluent stays live.
Cut over
Producers and consumers move in stages once the new side is verified. Confluent stays available for rollback.
Related pages
- PricingDatabase as a service pricing: dedicated, tailoredDatabase as a service pricing from OSStend: dedicated, tailored clusters priced by engine, size, SLA tier and location. Enterprise only, with no free tier.
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- KafkaManaged Kafka in your cloud or data centerManaged Kafka with the broker count, partition plan, KRaft, Connect and schema registry designed for your estate, run 24/7 in your cloud or your data center.
- Change data captureManaged Debezium: change data capture run 24/7Managed change data capture with Debezium on Kafka Connect or Debezium Server, run 24/7 in OSStend's cloud, your cloud account or your data center.
- Alternative7 Instaclustr alternatives by engine (2026)Seven Instaclustr alternatives for Kafka, PostgreSQL, OpenSearch and ClickHouse, with list prices checked 8 Nov 2026 and where OSStend fits.
- AlternativeAmazon MSK pricing and alternatives in 2026Amazon MSK pricing is only part of the picture. See the documented broker and partition limits, and an alternative: Apache Kafka sized to your workload.
Price your Kafka design with an engineer
45 minutes: your Confluent estate is reviewed and the Kafka design is sketched.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review