Difference with AutoMQ Enterprise Edition

The use cases for AutoMQ are categorized according to the deployment model as follows:

• Self-hosted Open Source Version: You can independently deploy and maintain the open-source version of AutoMQ in a private cloud environment.

• Purchase Commercial Version: By utilizing the commercial version and services provided by the AutoMQ team, you can receive technical support and maintenance services from the AutoMQ team. The commercial version is available in two forms:

  • AutoMQ Cloud The fully managed cloud service version provided by the AutoMQ team, which is particularly suitable for public cloud environments.

  • AutoMQ Enterprise The commercial version software provided by the AutoMQ team for private clouds, known as AutoMQ Enterprise.

Open Source Version

AutoMQ's open source version operates under the Apache License 2.0, with all related feature source code accessible in the GitHub repository. Despite being production-ready and extensively adopted by industry leaders, managing distributed storage software independently can present significant challenges. For best practices in deployment, operation, monitoring, and performance optimization, please reach out to community support.

Commercial Version

The commercial version of AutoMQ is tailored for enterprise-level needs, offering fully managed operations along with an SLA commitment. It provides significant optimizations and enhancements in crucial areas such as fault recovery, disaster recovery, elasticity, and observability compared to the open source version. A detailed comparison is as follows:

	AutoMQ Open Source Version	AutoMQ Commercial Edition
Product Name	AutoMQ	AutoMQ Cloud		AutoMQ Enterprise
Service Form	Free Software	SaaS Fully Managed Service [1]	BYOC Fully Managed Service [2]	Commercial Software [3]
Deployment Environment	Public Cloud or Private Cloud: AWS Alibaba Cloud Tencent Cloud Huawei Cloud Baidu Cloud CTyun MinIO Ceph CubeFS	Mainstream public cloud providers supported: AWS Azure GCP Alibaba Cloud Tencent Cloud Huawei Cloud Baidu Cloud China Telecom Cloud		For private cloud, the following storage technology stack is supported: MinIO Ceph CubeFS HDFS
Resource Ownership	IaaS resources owned by the user	IaaS resources owned by AutoMQ's cloud account	IaaS resources owned by the user's cloud account	IaaS Resource Ownership by Users
Data Sovereignty	100% Private, data remains within the user's private network	100% Secure, managed by the trusted AutoMQ company cloud account management	100% Private, data remains within the user's VPC	100% private; data remains within the user's private network
Operations Method	Self-deployment and operation	One-click activation via cloud marketplace, official website, etc., offering fully managed services covering the following scenarios: Deployment Version upgrades (new features and bug fixes) Parameter tuning System alerts[4] Online issue troubleshooting[5]		All operational tasks are carried out by the customer, with remote technical support provided by the AutoMQ team.
Payment Methods	[Optional] Subscribe to Technical Consultation	Pay-as-you-go: Pay per usage on an hourly basis Monthly/Annual Package: Prepay for specified configurations and benefits		Annual Subscription: Pay annually for specified configurations and benefits Perpetual License: A one-time purchase for software usage rights
Cost Structure	Machine Resource Costs (self-provided) Operations and Development Manpower Investment Commercial Paid Technical Consultation (Optional)	Software service fee (pricing includes cloud resources)	Software service fee (pricing excludes cloud resources) Cloud resource fees (paid to cloud providers)	Software service fee (pricing excludes machine resources) Machine resource fees (self-provided)
Technical Support	None Community Technical Support	Professional Technical Support Online Emergency Response Support		Expert Technical Support Online Emergency Response Support
Applicable Scenarios	Initial PoC Testing Recommended for production applications only if the client has a substantial in-house development team	Public Cloud Customer Default Options	Some public cloud customers prefer to utilize IaaS discounts, maintain data within the VPC, and agree to operational authorization.	This is relevant for customers in finance, government, and enterprises that require data sovereignty and complete environmental isolation.

• [1] involves deploying both the control and data planes of AutoMQ Cloud into a separate VPC under AutoMQ company's main account, which connects to the customer's VPC through VPC PrivateLink or VPC Peering.

• [2] involves deploying both the control and data planes of AutoMQ Cloud into the customer's main account VPC.

• [3] refers to deploying both the control and data planes of AutoMQ Enterprise into the customer's private cloud. The customer is responsible for operations and maintenance, while AutoMQ provides technical support and version upgrades.

• [4] During the operation of the AutoMQ Server, logs, metrics, and diagnostic data generated will be stored in a separate object storage Bucket. Customers need to grant cross-account access to this Bucket to AutoMQ's main account. The AutoMQ SaaS platform will analyze the customer's cluster logs and metrics in real-time to ensure stable operation through monitoring by AutoMQ's professional R&D team.

• [5] AutoMQ Server is equipped with automatic fault recovery capabilities, monitoring various cluster performance metrics in real time, and isolating any nodes that exhibit anomalies. This facilitates fault recovery before the application is impacted, a process that typically completes within minutes. Subsequently, engineers from the AutoMQ team will perform backend fault cause analysis.

If you need to evaluate or learn more about the commercial edition, please fill out the form and our product experts will contact you shortly.

Product Capability Comparison List

Capability Group	Capability Item	Open Source Version	Commercial Version
Cloud-Native Architecture Design	Second-level partition reassignment	✅	✅
	Minute-level smooth scaling	✅	✅
	100% compatible with Apache Kafka	✅	✅
Continuous data rebalancing	Traffic throughput-based scheduling	✅	✅
	Load balancing based on request call pressure	❌	✅
	Automatic identification of cold data reads	❌	✅
	Automatic identification of slow nodes	❌	✅
Disaster recovery	Automatic self-healing for server downtime	✅	✅
	Node Hang Self-Healing	❌	✅ Supports proactive scheduling, isolation, and recovery capabilities for the following fault scenarios: Network jitter isolation and recovery Server hang isolation and recovery FullGC isolation and recovery Slow Request Isolation Recovery
	Multi-AZ Disaster Recovery	❌	✅ Implement cross-AZ recovery based on Regional EBS
	Object Storage Disaster Recovery	❌	✅ Support cross-region write disaster recovery for S3, with automatic failover
	Block Storage Disaster Recovery	❌	✅ Supports quick persistence of hot data to backup EBS
	Multi-Cloud Disaster Recovery	❌	✅ Supports cross-cluster route disaster recovery, including message offset and consumption state reassignment
Elasticity & Cost Optimization	Storage Elasticity	✅ Kernel natively supports on-demand usage of S3	✅ Kernel natively supports on-demand usage of S3
	Traffic supports elastic scaling	❌	✅
	Support for multiple EBS and multiple WALs	❌	✅
	Support for Single Cluster Multi-Bucket Read/Write	❌	✅
	Multi-Metric Linked Elasticity	❌	✅ Supports multi-metric linked elasticity, including CPU, memory, and network throughput, offering enhanced adaptability to complex stress scenarios
	Scheduled Elastic Scaling	❌	✅Out-of-the-box functionality
	Large-scale Spot Instances	❌ Spot termination risks need to be addressed	✅Out-of-the-box, customize Spot instance ratio and scale based on business requirements
Visual management	Cluster Reassignment Tools	❌	✅ Provides seamless, managed reassignment tools
	Web Console	❌	✅ Comes with a ready-to-use console One-click cluster scaling and configuration adjustments Version management, including upgrades and rollbacks CRUDL management for topics, groups, and clusters Status queries for backlog, traffic hotspots distribution, etc.
Observability	JMX Metrics	✅	✅
	Prometheus	❌	✅ Provides custom metrics store dump functionality
	Integration with OTLP	❌	✅
	Grafana Dashboard	❌	✅ Provides ready-to-use visualization dashboards
	Monitoring Alerts	❌	✅ Offers ready-to-use monitoring alert templates to simplify configuration Operational anomaly alerts Stack alerts, etc.
	Audit Logs	❌	✅Comes with built-in event auditing capabilities (using operational S3 buckets) Operational action events Automatic rebalancing events Exception Events
Integration	Kafka Connect	✅	✅
	MirrorMaker2	✅	✅
	SSO/LDAP/AD Integration	❌	✅
DevOps Automation	Kafka Admin API/CLI	✅	✅
	Kubernetes	❌	✅
	Terraform	❌	✅
	Cluster Management REST APIs	❌	✅
Supported Cloud Providers	AWS	✅	✅
	Azure	❌	✅
	Google Cloud Platform	❌	✅
	Alibaba Cloud	✅	✅
	Tencent Cloud	✅	✅
	Huawei Cloud	✅	✅
	Baidu Cloud	✅	✅
	Tianyi Cloud	✅	✅
	Mobile Cloud	✅	✅
Supported Storage Technology Stack	MinIO	✅	✅
	Ceph	✅	✅
	CubeFS	✅	✅
	HDFS	❌	✅
Software Artifacts	Binary	✅	✅
	Docker	✅	✅
	Cloud Machine Image	❌	✅
Expert Services	Support Channels	Community Support	Enterprise Ticketing Service
	Expert Dedicated Support	❌	Product Integration Consultation Business Architecture Consulting Cluster Risk System Review Key Business Window Safeguarding

Related Content

Software Artifact▸