Chat with us, powered by LiveChat
A Seamless Apache Kafka Alternative,
Saving 50%+ Cloud Bills
Jump to the  Cloud Marketplace with One Click and Start Using AutoMQ Today.
Deployment Type
Peak Bytes In
120 MiB/s
5 GiB/s
Examples
120 MiB/s
240 MiB/s
500 MiB/s
1000 MiB/s
Note
Peak Bytes In metrics are used to determine the maximum capacity of a cluster. When evaluating peak write throughput, the number of replicas should not be considered.For example, if the peak business scenario involves writing 200 MiB/s with three replicas, the peak bytes In metric should still be set to 200 MiB/s.
Avg Bytes In
20 MiB/s
3 GiB/s
Examples
120 MiB/s
240 MiB/s
500 MiB/s
1000 MiB/s
Note
Average Bytes In metrics help calculate the total data written and storage consumption. To evaluate, observe 24-hour business operations and divide the total data written by the time window.For example, if 720 GiB is written over 24 hours, the average bytes In is 720 GiB / 24 hours, or approximately 8.5 MiB/s.
Retention Time
3 Day
365 Day
Note
Data retention time is used to assess cluster storage consumption. It's recommended to evaluate this based on business data characteristics. This metric impacts storage costs.
AutoMQ SaaS
AutoMQ BYOC
TCO, contains IaaS costs and service
6000
USD/month
50
% Savings
Apache Kafka
IaaS Cost Only, excluding operational costs
12000
USD/month
50
% Savings
MSK
Data from Alibaba Cloud, reference link
Data from AWS, reference link
12000
USD/month
Breakdown
Apache Kafka
Alibaba Cloud kafka 2.0
AutoMQ SaaS
VMs:
¥ 100
Instance:
¥ 1,400
AKU:
¥ 1,400
Storage:
¥ 1,400
Storage:
¥ 1,400
Storage:
¥ 1,400
Partition:
1 ¥/unit/month
billed on usage
Data Ingress:
¥ 1,400
Apache Kafka
Alibaba Cloud kafka 2.0
AutoMQ BYOC
VMs:
¥ 100
Instance:
¥ 1,400
Instance:
¥ 1,400
Storage:
¥ 1,400
Storage:
¥ 1,400
OSS Storage:
¥ 1,400
Partition:
1 ¥/unit/month
billed on usage
OSS API:
¥ 1,400
AKU:
¥ 1,400
Apache Kafka
MSK
AutoMQ BYOC
VMs:
$ 100
Instance:
$ 1,400
Instance:
$ 1,400
Storage:
$ 1,400
Storage:
$ 1,400
S3 Storage:
$ 1,400
ISR:
$ 1,400
S3 API:
$ 1,400
AKU:
$ 1,400
Tips
  • The pricing estimation model assumes a 1:1 ratio of production to consumption traffic, with the average write throughput in the production environment being no less than 10% of the peak throughput, and the message storage duration being no less than 3 days.
  • Pricing is based on the Alibaba Cloud Hangzhou region and referenced from Alibaba Cloud's listed prices. Actual costs may vary; please refer to the Alibaba Cloud website for accurate pricing.
  • Apache Kafka uses SSD cloud disks with three replicas, excluding operational labor costs.
  • For Alibaba Kafka 2.0 Professional Edition with SSD cloud disks, partition costs are not considered. SSD cloud disks are recommended for production, considering actual partition costs.
  • ECS and Ali Kafka 2.0 use hourly billing instances. Monthly costs are based on 730 hours per month.
  • 上述对比以美东地域为例,费用参考 AWS 目录价,实际如有出入请以 AWS 官网为准。
  • Apache Kafka 是在公有云上使用GP3 EBS 三副本建设,不考虑运维人员的人力投入成本计算。
  • MSK 是以分层存储版本计算,实际是否满足以产品限制为准。
  • 上述对比场景均考虑三可用区部署,会存在跨可用区传输流量费用。
Tips
  • The pricing estimation model assumes a 1:1 ratio of production to consumption traffic, with the average write throughput in the production environment being no less than 10% of the peak throughput, and the message storage duration being no less than 3 days.
  • AutoMQ BYOC uses OSS for data storage. OSS costs include storage space and API calls. Based on typical scenarios, the API call fee is estimated at 0.000597 RMB per 1GB of data written (with slight variations in API pricing for a few specific regions).
  • Pricing is based on the Alibaba Cloud Hangzhou region and referenced from Alibaba Cloud's listed prices. Actual costs may vary; please refer to the Alibaba Cloud website for accurate pricing.
  • Apache Kafka uses SSD cloud disks with three replicas, excluding operational labor costs.
  • For Alibaba Kafka 2.0 Professional Edition with SSD cloud disks, partition costs are not considered. SSD cloud disks are recommended for production, considering actual partition costs.
  • ECS and Ali Kafka 2.0 use hourly billing instances. Monthly costs are based on 730 hours per month.
  • 上述对比以美东地域为例,费用参考 AWS 目录价,实际如有出入请以 AWS 官网为准。
  • Apache Kafka 是在公有云上使用GP3 EBS 三副本建设,不考虑运维人员的人力投入成本计算。
  • MSK 是以分层存储版本计算,实际是否满足以产品限制为准。
  • 上述对比场景均考虑三可用区部署,会存在跨可用区传输流量费用。
Tips
  • The pricing estimation model assumes a 1:1 ratio of production to consumption traffic, with the average write throughput in the production environment being no less than 10% of the peak throughput, and the message storage duration being no less than 3 days.
  • The pricing estimation model does not take into account the traffic costs incurred by Producer and Consumer cross-AZ, but only analyzes the operational costs on the server side. Therefore, there are no ISR replication transmission costs within MSK and AutoMQ, while Apache Kafka will incur ISR replication transmission costs.
  • AutoMQ BYOC uses S3 for data storage. S3 costs include storage space and API calls. Based on typical scenarios, the API call fee is estimated at 0.0006298 USD per 1GB of data written (with slight variations in API pricing for a few specific regions).
  • Apache Kafka is constructed using GP3 EBS with three replicas, without considering the labor costs of maintenance personnel.
  • MSK is calculated based on the tiered storage version; actual compliance with product limitations should be verified.
  • Price comparison is based on the AWS US East region, with costs referenced from the AWS directory price. Actual costs may vary, so please refer to the official AWS website for accurate pricing.
  • The above comparison is set for deployment in three availability zones, so Apache Kafka will incur cross-availability zone data transfer due to ISR three-replica replication.
  • When calculating monthly costs, each month is considered to have 730 hours.
  • 上述对比以美东地域为例,费用参考 AWS 目录价,实际如有出入请以 AWS 官网为准。
  • Apache Kafka 是在公有云上使用GP3 EBS 三副本建设,不考虑运维人员的人力投入成本计算。
  • MSK 是以分层存储版本计算,实际是否满足以产品限制为准。
  • 上述对比场景均考虑三可用区部署,会存在跨可用区传输流量费用。
Talk to us, Get pricing
Unit Prices
Cloud Provider:
Deployment Type:
SaaS instances are deployed on the AutoMQ Cloud service side and expose services to the customer's VPC via VPC Peering, PrivateLink, etc. Customers only pay for AutoMQ services without worrying about the cloud resources consumed by the cluster.
BYOC instances have both the control plane and data plane fully deployed in the customer's VPC. Using BYOC instances requires no network interconnection, keeps data within the customer's VPC, and allows the reuse of customer cloud account discounts. Customers need to pay AutoMQ for software services (excluding cloud resource costs) and pay the cloud provider for underlying cloud resources.
AKU(AutoMQ Kafka Unit):
Pay for AutoMQ software services. Billing based on the peak throughput by each instance. Each 1AKU supports the following capabilities.
✓ Bytes In/Out
20 MiB/s
✓ Requests QPS
800 count/s
✓ Partitions
1125
Price:
0.147 - 0.620  CNY/AKU/Hour
[1    -   25)
0.620 CNY/AKU/Hour
[25  -   50)
0.465 CNY/AKU/Hour
[50  -  100)
0.349 CNY/AKU/Hour
[100 - 250)
0.262 CNY/AKU/Hour
[250 - 500)
0.196 CNY/AKU/Hour
[500 -    ~ )
0.147 CNY/AKU/Hour
Storage:
AutoMQ Cloud charges for the total data stored on a given AutoMQ instance.
Price:
0.25 CNY/GB/Hour
Data Ingress:
AutoMQ Cloud handles the cost of client data writes, including expenses incurred from cloud provider network transfer and storage operations.
Price:
Traffic:0.00083 CNY/GB
AKU(AutoMQ Kafka Unit):
Pay for AutoMQ software services. Billing based on the peak throughput by each instance. Each 1AKU supports the following capabilities.
✓ Bytes In/Out  
20 MiB/s
✓ Requests QPS
800 count/s
✓ Partitions
1125
Price:
0.7 CNY/AKU/Hour, the actual settlement price per AKU may vary based on the quantity of AKUs. Please refer to the conclusions of business communications for the final terms.
Cost Details:
The expenses for cloud resources required to run AutoMQ BYOC clusters, such as machines and object storage, are paid directly to the cloud provider.
Instance: refer to the pricing information provided by the cloud provider.
OSS price: refer to the pricing information provided by the cloud provider.
AKU(AutoMQ Kafka Unit):
Pay for AutoMQ software services. Billing based on the peak throughput by each instance. Each 1AKU supports the following capabilities.
✓ Bytes In/Out  
20 MiB/s
✓ Requests QPS
800 count/s
✓ Partitions
1125
Price:
0.2 USD/AKU/Hour, the actual settlement price per AKU may vary based on the quantity of AKUs. Please refer to the conclusions of business communications for the final terms.
Cost Details:
The expenses for cloud resources required to run AutoMQ BYOC clusters, such as machines and object storage, are paid directly to the cloud provider.
Instance: refer to the pricing information provided by the cloud provider.
S3 price: refer to the pricing information provided by the cloud provider.
联系我们,获取专属报价

Feature Comparison

Capability Item
Apache Kafka
AutoMQ Cloud
Fully-Managed service for enterprise
Cloud-Native Architecture
Second-level Partition Reassignment
Minute-level Smooth Scaling
100% Compatible with Apache Kafka
Self-balancing of Data
Traffic Throughput Based Scheduling
Request Call Pressure Based Scheduling
Automatic Identification of Cold Data Reads
Automatic Detection of Slow Nodes
Disaster Recovery
Server Auto-Healing on Crash
Active Self-Healing on Node Hang
Multi-AZ Resilience
Object Storage Resilience
Block Storage Resilience
Multi-Cloud Resilience
Elasticity & Cost Optimization
Storage Elasticity
Traffic-Driven Elastic Scaling
Support for Multiple EBS & Multiple WAL
Support for Multi-Cluster Multi-Bucket Read/Write
Multi-Metric Elasticity
Scheduled Elastic Scaling
Large-Scale Spot Instances
GUI-Based Management
Cluster Reassignment Tool
Web Console
Observability
JMX Metrics
Prometheus
OTLP Integration
Grafana Dashboard
Monitoring Alerts
Audit Logs
Integration
Kafka Connect
MirrorMaker2
SSO/LDAP/AD Integration
DevOps Automation
Kafka Admin API/CLI
Kubernetes
Terraform
REST APIs
Supported Cloud Providers
AWS
Azure
Google Cloud Platform
Supported Storage Technology Stack
MinIO
Ceph
CubeFS
HDFS
Software Artifact
Binary
Docker
Cloud Machine Image
Expert Services
Support Channels
Help from community
Enterprise work order
Dedicated Support
Read More

FAQ