Licensing
AutoMQ's use cases vary based on the type of deployment:
Self-hosted Community Edition: This allows you to independently deploy and maintain the AutoMQ Community Edition within a Private Cloud setting.
Purchasing the Business Edition: By adopting the Business Edition and leveraging the services from the AutoMQ team, you gain access to their expert technical support and maintenance services. The Business Edition is available in two variants:
AutoMQ Cloud A fully managed cloud service known as AutoMQ Cloud, ideally suited for Public Cloud environments.
AutoMQ Enterprise A version of the Business Edition software designed for Private Clouds, called AutoMQ Enterprise.
Community Edition
The AutoMQ Community Edition is covered by the AutoMQ BSL license, with all its source code accessible on the GitHub project.
Note:
Anyone can freely access the source code and software artifacts of AutoMQ Community Edition. It's important to note that providing third-party messaging queue, stream storage, and other commercial services requires a commercial license from AutoMQ CO.
Each community version source code governed by the BSL automatically converts to Apache V2.0 License four years after its release.
The legal entity referred to as "AutoMQ Team" or "AutoMQ CO." is AutoMQ CO.,LTD.
Business Edition
AutoMQ Business Edition is specifically designed for enterprise-level needs, offering fully managed operations and maintenance with an SLA commitment. Compared to the Community Edition, it significantly enhances and optimizes key areas such as fault recovery, disaster recovery, elasticity, and observability. The detailed comparison is as follows:
| - | AutoMQ Community Edition | AutoMQ Business Edition | AutoMQ Business Edition | AutoMQ Business Edition |
|---|---|---|---|---|
| Product Name | AutoMQ | AutoMQ Cloud | AutoMQ Cloud | AutoMQ Enterprise |
| Service Model | Free Software | SaaS Fully Managed Service [1] | BYOC Fully Managed Service[2] | Paid Software[3] |
| Deployment Environment | Public or Private Cloud:
| Geared towards Public Cloud, supported mainstream cloud providers:
| Geared towards Public Cloud, supported mainstream cloud providers:
| Geared towards Private Cloud, supports the following storage technology stack:
|
| Resource Ownership | IaaS resources owned by the user | IaaS resources owned by AutoMQ company cloud account | IaaS resources owned by user's cloud account | IaaS resources owned by the user |
| Data Sovereignty | 100% private, data stays within the user's private network | 100% secure, trusted AutoMQ company cloud account management | 100% private, data stays within the user's VPC | 100% private, data stays within the user's private network |
| Operations Management | Self-deployed and managed | One-click activation via cloud marketplaces or official website, fully managed services, covering the following scenarios:
| One-click activation via cloud marketplaces or official website, fully managed services, covering the following scenarios:
| All operations are performed by the client, with remote technical support provided by the AutoMQ team |
| Payment Method | [Optional] Subscription to technical consulting |
|
|
|
| Cost Structure |
| Software service fee (pricing includes cloud resources) |
|
|
| Technical Support |
|
|
|
|
| Applicable Scenarios |
| Default option for public cloud customers | Suitable for some public cloud customers who wish to reuse IaaS discounts, data stays within VPC, accepts operational authorization | Suitable for financial, government and enterprise customers requiring data sovereignty and completely isolated environments |
[1] Involves deploying both the control plane and data panel of AutoMQ Cloud within the independent VPC of the main account under AutoMQ CO., while establishing connectivity to the customer's VMD via VPC PrivateLink or VPC Peering.
[2] Pertains to deploying both the control plane and data plane of AutoMQ Cloud directly within the VPC of the customer's main account.
[3] Entails deploying both the control plane and data plane of AutoMQ Enterprise within the customer’s Private Cloud, with the customer handling operations and maintenance, and AutoMQ CO. providing technical support and updates.
[4] During the operation of AutoMQ Server, all generated logs, metrics, and diagnostic data are stored in a dedicated Object storage Bucket, requiring cross-account authorization from the customer to the AutoMQ team’s main account. The AutoMQ SaaS platform conducts real-time analysis of the customer’s cluster logs and metrics, with the professional R&D team at AutoMQ ensuring the stable operation of the customer’s cluster from the backend.
[5] AutoMQ Server features robust automatic failure recovery capabilities, constantly monitoring the performance metrics of the cluster, automatically isolating any nodes showing abnormalities, thus ensuring rapid failure recovery before any impact reaches the application, usually completed within minutes. Following this, engineers from the AutoMQ team will analyze the root causes of the failure.
If you're interested in evaluating or learning more about the Business Edition, please fill out the form, and our product specialists will contact you shortly.
Appendix: Product Capability Comparison List
| Capability Group | Capability Item | Community Edition | Business Edition |
|---|---|---|---|
| Cloud Native Architecture Design | Sub-second Partition Reassignment | ✅ | ✅ |
| Cloud Native Architecture Design | Minute-level Smooth Scaling | ✅ | ✅ |
| Cloud Native Architecture Design | 100% Compatible with Apache Kafka | ✅ | ✅ |
| Continuous Data Self-balancing | Based on Traffic Throughput Scheduling | ✅ | ✅ |
| Continuous Data Self-balancing | Based on Request Invocation Pressure Scheduling | ❌ | ✅ |
| Continuous Data Self-balancing | Automatic Identification of Cold Data Reads | ❌ | ✅ |
| Continuous Data Self-balancing | Automatic Identification of Slow Nodes | ❌ | ✅ |
| Disaster Recovery | Server Crash Self-recovery | ✅ | ✅ |
| Disaster Recovery | Node Hang Self-Healing | ❌ | ✅ |
| Disaster Recovery | Multi-AZ Resilience | ❌ | ✅Implemented cross-AZ scheduling recovery based on Regional EBS |
| Disaster Recovery | Object Storage Resilience | ❌ | ✅Supports cross-region write disaster recovery to S3, with automatic switching |
| Disaster Recovery | Block Storage Resilience | ❌ | ✅Supports rapid persistence of hot data to disaster recovery EBS |
| Disaster Recovery | Multi-Cloud Resilience | ❌ | ✅Supports cross-cluster routing for disaster recovery, including message offset and consumption state reassignment |
| Elasticity & Cost Optimization | Storage Elasticity | ✅ Natively supports on-demand use of S3 | ✅ Natively supports on-demand use of S3 |
| Elasticity & Cost Optimization | Traffic-based Scalable Elasticity | ❌ | ✅ |
| Elasticity & Cost Optimization | Supports Multiple EBS and Multiple WAL | ❌ | ✅ |
| Elasticity & Cost Optimization | Support for Multi-Bucket Read/Write in a Single Cluster | ❌ | ✅ |
| Elasticity & Cost Optimization | Multi-Metric Elasticity | ❌ | ✅Supports CPU, memory, network throughput, and other metrics, offering stronger adaptability to complex pressure scenarios |
| Elasticity & Cost Optimization | Scheduled Elastic Scaling | ❌ | ✅Ready out of the box |
| Elasticity & Cost Optimization | Large-Scale Spot Instances | ❌ | Requires addressing forced reclamation risk of Spot instances |
| GUI-Based Management | Cluster Reassignment Tool | ❌ | ✅Provides a managed smooth reassignment tool |
| GUI-Based Management | Web Console | ❌ | ✅Provides a ready-to-use console |
| Observability | JMX Metrics | ✅ | ✅ |
| Observability | Prometheus | ❌ | ✅Offers customized Metrics store dumping feature |
| Observability | OTLP Integration | ❌ | ✅ |
| Observability | Grafana Dashboard | ❌ | ✅ Provides out-of-the-box visualization dashboards |
| Observability | Monitoring and Alerts | ❌ | ✅ Provides out-of-the-box monitoring alert templates, simplifying configuration
|
| Observability | Audit Logs | ❌ | ✅ Provides out-of-the-box event auditing capabilities (based on Ops S3 bucket)
|
| Integration | Kafka Connect | ✅ | ✅ |
| Integration | MirrorMaker2 | ✅ | ✅ |
| Integration | SSO/LDAP/AD Integration | ❌ | ✅ |
| DevOps Automation | Kafka Admin API/CLI | ✅ | ✅ |
| DevOps Automation | Kubernetes | ❌ | ✅ |
| DevOps Automation | Terraform | ❌ | ✅ |
| DevOps Automation | Cluster Management REST APIs | ❌ | ✅ |
| Supported Cloud Providers | AWS | ✅ | ✅ |
| Supported Cloud Providers | Azure | ❌ | ✅ |
| Supported Cloud Providers | Google Cloud Platform | ❌ | ✅ |
| Supported Cloud Platforms | Alibaba Cloud | ✅ | ✅ |
| Supported Cloud Platforms | Tencent Cloud | ✅ | ✅ |
| Supported Cloud Providers | Huawei Cloud | ✅ | ✅ |
| Supported Cloud Providers | Baidu Cloud | ✅ | ✅ |
| Supported Cloud Providers | Chinatelecom Cloud | ✅ | ✅ |
| Supported Cloud Providers | China Mobile Cloud | ✅ | ✅ |
| Supported Storage Technology Stack | MinIO | ✅ | ✅ |
| Supported Storage Technology Stack | Ceph | ✅ | ✅ |
| Supported Storage Technology Stack | CubeFS | ✅ | ✅ |
| Supported Storage Technology Stack | HDFS | ❌ | ✅ |
| Software Product | Binary | ✅ | ✅ |
| Software Product | Docker | ✅ | ✅ |
| Software Product | Cloud Machine Image | ❌ | ✅ |
| Expert Services | Support Channels | Community-based Help | Enterprise Ticket Services |
| Expert Services | Dedicated Expert Support | ❌ |
|