DAS billing editions pricing pay-as-you-go subscription-Database Autonomy Service(DAS)-阿里云帮助中心

Learn about the billing methods, billable items, and supported databases for each Database Autonomy Service (DAS) edition.

Editions

DAS offers three editions: Basic Edition, Economy Edition, and Enterprise Edition (formerly Professional Edition).

Basic Edition: Enabled by default and free of charge. Provides unified management of multiple database engines, database issue diagnosis, and performance optimization for daily O&M needs.
Economy Edition: Paid, subscription-based. Builds on the Basic Edition with lightweight autonomy services. It introduces automatic fragment reclamation and Performance Insight, and enhances instance sessions and lock analysis.
Enterprise Edition (formerly Professional Edition): Paid. Builds on the Economy Edition and adds SQL Explorer and Audit.

Important
The Enterprise Edition is continuously updated and has multiple minor versions. When you enable it for a database instance, only the latest supported minor version is available. Each update brings more flexible and cost-effective billing.

The following table lists the billing method and billable items for each DAS edition.

Note

To check which edition a database instance uses, go to the Version Management page in the DAS console.

Edition	Minor version	Billing method	Billable items
Basic Edition	None	Free	None
Economy Edition	None	Subscription	Basic Package Standard Package Premium Package
Enterprise Edition	V3	Pay-as-you-go	Important Enterprise Edition V3 charges for log traffic and cold storage by default. Other features are billed based on usage. Default billing: Log traffic Cold storage Usage-based billable items: Log indexing SQL Explorer Security audit Hot storage Cold query Download (Free)
	V2 (formerly the new Professional Edition)	Pay-as-you-go	Hot data storage Cold data storage Data query
	V1 (formerly the old Professional Edition)	Subscription + Pay-as-you-go	Enterprise Edition V1 quota (Subscription) Note The maximum number of database instances that can use Enterprise Edition V1. Storage fees for SQL Explorer (Pay-as-you-go)
	V0 (formerly the old Professional Edition, uses the old ingest endpoint)	Pay-as-you-go	Storage fees for SQL Explorer

Database	Region
ApsaraDB RDS for MySQL PolarDB for MySQL	China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Japan (Tokyo), Malaysia (Kuala Lumpur), Indonesia (Jakarta), UK (London), US (Silicon Valley), Philippines, US (Virginia), and Germany (Frankfurt)
ApsaraDB RDS for PostgreSQL	China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Indonesia (Jakarta), Japan (Tokyo), US (Virginia), Germany (Frankfurt), and UK (London)
ApsaraDB RDS for SQL Server	China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Guangzhou), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Japan (Tokyo), Indonesia (Jakarta), US (Silicon Valley), US (Virginia), and Germany (Frankfurt)

Database	Region
RDS MySQL PolarDB for MySQL	China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Guangzhou), China (Heyuan), China (Zhangjiakou), China (Ulanqab), China (Hong Kong), and Singapore

Database	Region
RDS MySQL ApsaraDB RDS for SQL Server PolarDB for MySQL Note The high-availability series of ApsaraDB RDS for SQL Server 2008 R2 is not supported.	China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Heyuan), China (Ulanqab), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)
ApsaraDB RDS for PostgreSQL	China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Zhangjiakou), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)
PolarDB-X 2.0	China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and Singapore

Database	Region
ApsaraDB RDS for MySQL ApsaraDB RDS for SQL Server PolarDB for MySQL Note RDS SQL Server 2008 R2 High-availability Edition is not supported.	China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Heyuan), China (Ulanqab), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), US (Virginia), US (Silicon Valley), Germany (Frankfurt), and UK (London)
RDS PostgreSQL	China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Zhangjiakou), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)
PolarDB-X 2.0	China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), and Singapore

Database	Region
ApsaraDB RDS for MySQL PolarDB for MySQL	China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Chengdu), and China (Hong Kong)

Database	Region
ApsaraDB RDS for MySQL, PolarDB for MySQL, MyBase for MySQL, and self-managed MySQL RDS PostgreSQL, PolarDB for MySQL, and self-managed PostgreSQL ApsaraDB RDS for SQL Server and MyBase for SQL Server PolarDB for PostgreSQL (Compatible with Oracle) PolarDB-X 2.0 Tair (Redis OSS-compatible), MyBase for Redis, and self-managed Redis ApsaraDB for MongoDB and self-managed MongoDB	No region restrictions