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 Model
Open-source software (Apache License 2)
Fully managed service, providing SaaS version [1] and BYOC version [2]
Deployment Environment
Supported cloud providers:
  • AWS
  • Other cloud providers (compatible with S3 API)

Private data centers require the following storage software:
  • MinIO
  • Ceph
  • CubeFS
  • Other software compatible with S3 protocol
Supported mainstream cloud providers:
  • AWS
  • Azure
  • GCP
  • OCI
  • Other cloud providers supporting object storage
WAL Storage Engine
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, balancing network throughput only
Comprehensive multi-metric scheduling strategy, balancing the following metrics:
  • Network throughput
  • Request QPS
  • Data cold read accumulation
  • Slow node isolation
Cluster Reassignment
Open-source MirrorMaker2 has the following issues:
  • Message replication offset inconsistency
  • Cluster switching requires downtime
KafkaLinking, a non-downtime reassignment tool, supports:
  • Offset-consistent ByteToByte message synchronization
  • Non-downtime rolling cluster switch
Enterprise Product Features
None
  • Out-of-the-box UI for managing cluster, Topic, and Group resources
  • Metrics integration: Prometheus, CloudWatch, etc.
  • Operation audit
  • RBAC & SSO
  • Terraform
Disaster Recovery
  • Self-healing server failures
  • Self-healing server failures
  • Object storage redundancy
  • Multi-cloud redundancy
Resource Ownership
IaaS resources owned by users
Under SaaS model, IaaS resources belong to AutoMQ’s cloud account; Under BYOC model, IaaS resources belong to the customer
Data Sovereignty
100% private, data stays within the user’s private network
Under BYOC model, data remains within user’s private network VPC
Operation Method
Self-deployment and operation
One-click activation through cloud marketplace, official website, etc., fully managed services covering 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
  • Commercial paid technical consultation (optional)
  • Subscription fees
  • Cloud resource costs (only in BYOC mode), direct payment to cloud providers
Technical Support
  • None
  • Community 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.