Amazon MSK pricing and alternatives for enterprise Kafka
Apache Kafka with Connect and a schema registry, sized to your topic estate 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
Amazon MSK (Amazon Managed Streaming for Apache Kafka) pricing is one input. OSStend runs upstream Apache Kafka for enterprises that outgrow a managed service's documented limits or need Kafka outside AWS. The broker count and partition plan are designed for the estate, and AceMQ engineers run the cluster 24/7. Amazon MSK stays the simpler choice for Kafka that lives on AWS and fits its limits.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
Amazon MSK and OSStend at a glance
Amazon MSK is AWS's managed Kafka service, run inside an AWS account. OSStend runs the upstream Apache Kafka and designs the cluster around the workload, in our cloud, your cloud account or your data center.
| OSStend | Amazon MSK | |
|---|---|---|
| What you run | Upstream Apache Kafka with Kafka Connect and a schema registry | AWS's managed Kafka service, with Standard and Express brokers, serverless clusters, MSK Connect and MSK Replicator (AWS docs) |
| Where it runs | Our cloud, your AWS, Azure or Google Cloud account, your data center | AWS only |
| Brokers per cluster | Broker count and partition plan designed for the estate | 30 on ZooKeeper-based clusters, 60 on KRaft-based clusters (AWS docs) |
| Pricing | Price drivers on pricing; sized per design | Set by AWS; see its pricing page |
Source: AWS MSK quotas, checked 30 Oct 2026. The MSK pricing page is linked, not summarised.
Why teams look for an alternative to Amazon MSK
The reasons that come up are documented limits, a single cloud and the cost of a large cluster. The limits are in AWS's own quota page, so they are stated here as the documentation states them.
| Area and managed service | Documented limit | What OSStend does instead | Source |
|---|---|---|---|
| Cluster sizeAmazon MSK | 30 brokers per cluster on ZooKeeper-based clusters and 60 on KRaft-based clusters. The documentation describes a process for requesting higher quotas where one applies. | What OSStend does insteadBroker count and partition plan designed for the estate. | AWS docs, checked 30 Oct 2026 ↗ |
| Configuration and version changesAmazon MSK | To update the configuration or the Apache Kafka version of a cluster, the number of partitions per broker must first be under the documented limits. | What OSStend does insteadThe partition plan is part of the signed-off design, and upgrade timing is agreed with the customer. | AWS docs, checked 30 Oct 2026 ↗ |
- One cloud.
- MSK runs on AWS only. An estate on Azure, Google Cloud or in a data center needs another service there, and a second vendor to go with it.
- Cost at scale.
- Teams with large, steady throughput compare the AWS bill with dedicated Kafka sized to the load.
- Control of the design.
- Some topic estates need a broker count, partition plan or upgrade timing that a service's plan does not give. The managed service limits research lists such limits across engines.
A fair snapshot of Amazon MSK
MSK is the natural Kafka for teams that already live on AWS. If the cluster fits the documented limits and stays in one AWS account, there is little reason to move.
- ✓It offers several shapes in one family: Standard and Express brokers, serverless clusters, MSK Connect and MSK Replicator (AWS docs, checked 30 Oct 2026).
- ✓It supports IAM access control, so Kafka clients can use the same identity model as the rest of an AWS estate (AWS docs, checked 30 Oct 2026).
- ✓It sits inside your AWS account, networking and billing, which keeps procurement simple.
Where MSK is the better choice: Kafka that stays on AWS, clusters that fit the documented limits, and teams that want the cluster to be an AWS line item rather than a separate contract.
Full comparison: OSStend and Amazon MSK
OSStend is listed first. The MSK column states what AWS documents, with the date checked, and describes the rest without numbers.
| Factor | OSStend | Amazon MSK |
|---|---|---|
| Good fit | Large topic estates; Kafka outside AWS or across clouds; teams that want a design they can price | Kafka that stays on AWS and fits the documented limits |
| Poor fit | Small clusters on defaults, free tiers, self-serve sign-up | Estates on other clouds or in a data center; clusters that grow past the documented limits |
| Where it runs | Our cloud, your cloud account, your data center, Kubernetes or OpenShift | AWS only |
| Tailoring | Broker count, partition plan, Connect and schema registry layout designed for the estate | Within the documented quotas (AWS docs) |
| 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) | AWS publishes its own SLA |
| Pricing model | Price drivers: size, storage, SLA tier, where it runs. See pricing | Set by AWS |
Source: AWS MSK quotas, checked 30 Oct 2026. Other MSK cells are descriptive.
How OSStend does it
OSStend designs the Kafka cluster for your topic estate, moves it with mirroring and runs it with 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, so the cluster can stay where your networking and keys already are. Because it is upstream open source, the licence and the price of what you run do not depend on one vendor. If you run Debezium on MSK Connect, managed Debezium puts engineers on the Debezium side, and Debezium vs AWS DMS compares it with AWS's migration service.
Contact us if
- ✓Your Kafka estate is large or growing and the cluster size or partition plan is a constraint.
- ✓You need Kafka on more than one cloud, or in a data center.
- ✓You want RabbitMQ and Kafka under one contract and one on-call team.
Not a fit if
- ✕Your Kafka stays on AWS and fits MSK's limits: MSK is simpler.
- ✕You want a free tier, a card sign-up or a serverless service with no design step.
Amazon MSK pricing: list prices and what ours depends on
AWS publishes MSK pricing per broker hour and per GB of storage; the table shows four broker types and the storage rate. OSStend prices the design, and the drivers are the broker count and size, storage and retention, the service level tier and where the cluster runs.
| Amazon MSK Provisioned, on demand | Price |
|---|---|
| kafka.t3.small Standard broker, per hour | $0.0456 |
| kafka.m7g.large Standard broker, per hour | $0.204 |
| kafka.m5.large Standard broker, per hour | $0.21 |
| express.m7g.large Express broker, per hour | $0.408 |
| Standard broker storage, per GB-month | $0.10 |
US East (N. Virginia), USD. Source: AWS MSK pricing, checked 1 Nov 2026; the m7g.large, m5.large, Express and storage rates also appear in the page's worked examples, and the t3.small rate comes from the AWS Price List file for MSK published 14 Oct 2026. Data ingress on Express brokers, MSK Serverless, MSK Connect and data transfer are priced separately.
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 throughput, retention and connector count and price the same shape on both sides, starting from the AWS MSK pricing page. OSStend's drivers are on pricing. The quotas that decide which broker count you need are set out beside other services in the managed service limits research.
Fair notes on other options
Besides OSStend, teams leaving MSK usually look at a commercial Kafka platform or another managed open source vendor.
- Confluent.
- The commercial Kafka platform, with several deployment shapes. See the Confluent comparison.
- Instaclustr.
- Runs Kafka with Kafka Connect in its cloud, your own account or on-prem (Instaclustr, Oct 2026; checked 30 Oct 2026).
How to choose
Choose by where Kafka must run and whether the documented limits bind. Staying on MSK is right when they do not.
- If Kafka stays on AWS and fits MSK's limits, stay on MSK.
- If the estate spans clouds or a data center, choose OSStend or another vendor that runs there.
- If the broker count or partition plan is the constraint, choose a design you control: OSStend.
- If you also run RabbitMQ, OSStend covers both on one contract.
Moving off Amazon MSK
The new cluster is built to the signed-off design, mirrored from MSK and verified before clients switch. Both stay live until cutover.
Review
Topics, partitions, retention, ACLs, connectors, schemas and client versions on the MSK cluster.
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 with the mirroring tools Apache Kafka documents (Kafka docs), while MSK stays live.
Cut over
Producers and consumers move in stages once the new side is verified. MSK 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.
- Research · Original dataManaged service limits index, checked 9 Nov 2026A managed service limits index: 13 documented limits of Amazon MQ, MSK, ElastiCache, Neon, Supabase and Instaclustr, each with its source link and date.
- 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.
- ComparisonDebezium vs AWS DMS: change data capture comparedDebezium vs AWS DMS for change data capture: sources, targets, operations, log handling and when each fits. Read from both vendors' documentation, 18 Nov 2026.
Price your Kafka design with an engineer
45 minutes: your MSK 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