Skip to Main Content

Licensing and Enterprise Features

Users can follow the deployment methods listed below to install and use AutoMQ:

  • Install the Open Source Version: Deploy and operate the AutoMQ open-source version within your private network environment or data center.

  • AutoMQ Cloud Service (Recommended): Simplify the process by directly enabling the AutoMQ Cloud service in a public cloud environment, thereby avoiding installation and maintenance hassles. AutoMQ Cloud is a fully managed, maintenance-free cloud service provided by the AutoMQ team. For more details, please refer to the reference documentation.

AutoMQ Cloud provides developers with a two-week free trial credit worth $1,400, without the need for credit card registration or payment information.

Open Source Version​

The open-source version of AutoMQ is covered under the Apache License 2.0, and the source code for all related functionalities is available for review in the GitHub project. The AutoMQ open-source edition is fully production-ready and widely deployed across numerous industry-leading enterprises; however, significant challenges remain with self-hosting distributed storage software. For best practices in the open-source community regarding deployment, operations, monitoring, and performance tuning, please reach out to Community Support.

Product Comparison​

Below is a comparison between the AutoMQ Open Source edition and AutoMQ Cloud:

Product Name


AutoMQ Open-source Edition


AutoMQ Cloud

Service Models


Open Source Software (Apache License 2.0)


SaaS Fully Managed Service [1]


BYOC Fully Managed Service [2]


Deployment Environment


Supported cloud providers:


  • AWS
  • Other cloud providers (compatible with the S3 API)

Private data center, requires the provision of the following storage software


  • MinIO
  • Ceph
  • CubeFS
  • Other software compatible with the S3 protocol

Supported mainstream cloud providers:


  • AWS
  • Azure
  • GCP
  • Alicloud
  • Tencent Cloud
  • Baidu Cloud
  • Tianyuan Cloud
WAL Storage Engine

Standard Object Storage WAL


  • Produce RT: P99 600+ milliseconds

Low Latency Storage WAL (EBS, FSx)


  • Produce RT: P99 < 10 milliseconds
Continuous Data Rebalancing

Basic scheduling strategy that focuses solely on balancing network throughput


Multi-metric comprehensive scheduling strategy to balance the following metrics:


  • Network throughput
  • Requests QPS (Queries Per Second)
  • Data cold read backlog
  • Slow Node Isolation
Cluster Reassignment

Open-source MirrorMaker2 presents the following issues:


  • Inconsistent message replication offsets
  • Cluster switchover requires downtime

KafkaLinking Zero Downtime Migration Tool supports:


  • Offset-consistent ByteToByte message synchronization
  • Zero-downtime rolling cluster switching
Enterprise Product Features

None


  • Ready-to-use UI for managing Clusters, Topics, and Group resources
  • Metrics integration: Prometheus, CloudWatch, etc.
  • Operational audit
  • RBAC & SSO
  • Terraform
Disaster Recovery
  • Automatic server fault recovery
  • Automatic Server Healing
  • Redundant Object Storage
  • Multi-Cloud Redundancy

Resource Ownership


IaaS resources are owned by the user.


IaaS resources are owned by the AutoMQ company's cloud account.


IaaS resources are owned by the user's cloud account.


Data Sovereignty


100% Private: Data remains within the user's private network


100% Secure: Managed by a trusted AutoMQ company cloud account


100% Private: Data does not exit the user's VPC


Operations Method

Self-deployment and operations


Effortlessly access our services through channels like the cloud marketplace and our official website, offering fully managed services that address the following scenarios:


  • Deployment
  • Version upgrades (new features and bug fixes)
  • Parameter tuning
  • System Alerts[3]
  • Online Fault Handling[4]

Cost Structure


    • Machine resource costs (self-provided)

    • Operations and development manpower investment

  • Paid Commercial Technical Consultation (Optional)

Subscription fee (pricing includes cloud resources)


  • Subscription fee (pricing excludes cloud resources)
  • Cloud resource costs (paid directly to cloud providers)
Technical Support
  • None
  • Community-based technical support
  • Expert technical support
  • Online emergency response support

  • [1] involves deploying both the control plane and the data plane of AutoMQ Cloud within a dedicated VPC under AutoMQ company's primary account and connecting to the customer's VPC through VPC PrivateLink or VPC Peering.

  • [2] involves deploying both the control plane and the data plane of AutoMQ Cloud under the customer's primary account VPC.

  • [3] During the operation of the AutoMQ Server, all generated logs, metrics, and diagnostic data will be stored in a separate object storage bucket. Customers need to grant cross-account permissions for this bucket to the AutoMQ team's main account. The AutoMQ operations platform will analyze the logs and metrics of customer clusters in real-time to ensure stable cluster operation, supported by AutoMQ's professional R&D team.

  • [4] AutoMQ Server is outfitted with automatic fault recovery capabilities, offering real-time monitoring of various cluster performance metrics and automatically isolating any nodes that show anomalies. This ensures fault recovery occurs before any failure impacts the application, usually completing this process within minutes. Following this, engineers from the AutoMQ team carry out a backend analysis to determine the fault's causes.

If you're interested in evaluating our cloud services or need paid technical support, please fill out the form, and our product experts will get in touch with you promptly.