A Seamless Apache Kafka Alternative,
Saving 50%+ Cloud Bills
Auto-Scaling, Single-digit ms latency, 100% Compatible
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
TCO, contains IaaS costs and service
6000
CNY/Month
50
%
Savings
Apache Kafka
IaaS Cost Only, excluding operational costs
12000
CNY/Month
50
%
Savings
Alibaba Cloud Kafka 2.0
Data from Alibaba Cloud.
以目录价文档为准,参考链接
12000
CNY/Month
Breakdown
Apache Kafka
Alibaba Cloud kafka 2.0
AutoMQ SaaS
VMs:
¥ 100
Instance:
¥ 1400
AKU:
¥ 1400
Storage:
¥ 1,400
Storage:
¥ 1,400
Storage:
¥ 1,400
Tips
  • 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.
  • Monthly costs are calculated based on 730 hours.
  • 上述对比以美东地域为例,费用参考 AWS 目录价,实际如有出入请以 AWS 官网为准。
  • Apache Kafka 是在公有云上使用GP3 EBS 三副本建设,不考虑运维人员的人力投入成本计算。
  • MSK 是以分层存储版本计算,实际是否满足以产品限制为准。
  • 上述对比场景均考虑三可用区部署,会存在跨可用区传输流量费用。
Talk to us, Get pricing
Unit Prices
Cloud Provider
Region
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.
AKU(AutoMQ Kafka Unit):
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
20 MiB/s
✓ Requests
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
费用介绍:
AKU 费用代表消息收发处理的能力规格费用,向 AutoMQ 支付。按实例的收发消息峰值吞吐规模进行计费。每 1 AKU 支持如下能力。
消息读写吞吐:
20 MiB/s
请求 QPS:
800 count/s
分区数:
1125
单价:
0.166 - 0.7  元/AKU/时
[1 - 25)
0.7 USD/AKU/时
[25 - 50)
0.525 USD/AKU/时
[50 - 100)
0.394 USD/AKU/时
[100- 250)
0.295 USD/AKU/时
[250 - 500)
0.221 USD/AKU/时
[500 - )
0.166 USD/AKU/时
费用介绍:
AutoMQ Cloud 用于衡量每个 AutoMQ 实例中存储数据的成本。按照每小时实际的空间消耗计费。
单价:
0.2 USD/GB/时
费用介绍:
用户从客户端网络访问 AutoMQ 服务时因云厂商网络传输而产生的写入流量费用。
价格:
VPC Peering: 0.2 USD/GB
PrivateLink: 0.2 USD/GB
费用介绍:
用户从客户端网络访问 AutoMQ 服务时因云厂商网络传输而产生的读取流量费用。
价格:
VPC Peering: 0.2 USD/GB
PrivateLink: 0.2 USD/GB
联系我们,获取专属报价

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

Talk to us for details,
Request free PoC and demo