The billing system of DataWorks consists of billing on features and billing on resources. DataWorks supports the subscription and pay-as-you-go billing methods for all billable items in the billing system. This topic describes the billable items of DataWorks and the billing details of features provided by different modules in DataWorks.

Precautions

  • The billing details of the DataWorks service vary based on the cloud environment, such as the Alibaba Cloud public cloud or Alibaba Finance Cloud, and the specifications. The fees that are generated when you use the service prevail.
  • Only an Alibaba Cloud account or a RAM user to which the AliyunBSSOrderAccess and AliyunDataWorksFullAccess policies are attached can be used to purchase resources.
  • Exclusive resources provided by DataWorks are classified into exclusive resource groups for Data Integration and exclusive resource groups for scheduling. When you purchase a resource group, make sure that you select the correct resource group type and region.

Billable items

The following figure shows the billable items of DataWorks. You can purchase features and resources based on your business requirements. You can also refer to the purchase guide that is provided by DataWorks for different users. For more information, see Purchase guide. bill
Category Billable item Description for fees Billing detail
Billing on features Editions DataWorks has the following editions: Basic Edition, Standard Edition, Professional Edition, Enterprise Edition, and Ultimate Edition. Standard Edition, Professional Edition, Enterprise Edition, and Ultimate Edition are advanced editions. After you activate the DataWorks service, DataWorks Basic Edition is activated by default. The DataWorks advanced editions provide more features than DataWorks Basic Edition. You can select an edition based on your business requirements. Billing on features: editions
Billing on resources Data Integration Data Integration supports data synchronization between various heterogeneous data sources. Resources are required to run nodes in Data Integration. You are charged for the resources that you use. Billing on resources: Data Integration
Node scheduling Scheduling resources are required for data development and scheduling of auto triggered nodes. You are charged for the resources based on the number of node instances that are successfully run. The related fees are included in your DataWorks bills. You can use an exclusive resource group for scheduling or the shared resource group for scheduling to schedule your node. You are charged for an exclusive resource group for scheduling based on the subscription billing method and the shared resource group for scheduling based on the pay-as-you-go billing method. Billing on resources: node scheduling
Alarm
  • Baselines provided by the Alarm system are used to monitor nodes. A baseline in the Enabled state generates baseline instances. You are charged for baselines based on the number of baseline instances that are generated. The related fees are included in your DataWorks bills.
  • The Alarm system provides the monitoring and alerting features for tables, nodes, and resources. You are charged for using the features based on the number of text messages and phone calls that are used to send alert notifications. The related fees are included in your DataWorks bills.
Billing on resources: Alarm
DataService Studio DataService Studio supports API encapsulation based on data sources. Data Service Studio also allows you to add existing APIs to DataService Studio to provide services. You are charged for DataService Studio API call based on the number of calls that you make and the execution time of calls. The related fees are included in your DataWorks bills. You can use the shared resource group for DataService Studio to call DataService Studio APIs. Billing on resources: calls to DataService Studio APIs
Data Quality Data Quality monitors the quality of table data generated by nodes. You are charged for the quality check based on the number of monitoring rules that are used in the check. The related fees are included in your DataWorks bills. Billing on resources: Data Quality
OpenAPI DataWorks provides the OpenAPI module. You can customize business development modes by using this module. You are charged for API call based on the number of calls that you make. The related fees are included in your DataWorks bills. Billing on resources: calls to DataWorks API operations in the OpenAPI module
Note

Billing methods

DataWorks supports the subscription and pay-as-you-go billing methods. The following table describes the details of the billing methods.
Billing method Description Billing cycle and billing formula Precautions
Subscription The subscription billing method allows you to purchase resources for a specified period of time before you can use them.
  • Billing cycle

    Year or month.

  • Billing formulas

    If the subscription duration is month, fees are calculated based on the following formula: Unit price per month × Number of months. If the subscription duration is year, fees are calculated by using the following formula: Unit price per year × Number of years.

If you no longer require a subscription resource, you can disable auto-renewal for the resource or unsubscribe from the resource. For more information, see Disable auto-renewal for subscription resources.
Pay-as-you-go The pay-as-you-go billing method allows you to pay for resources after you use them.
  • Billing cycle
    The pay-as-you-go billing method supports the following billing cycles for billable items:
    • Hourly billing

      The billing system calculates the actual resource usage over the previous hour every hour and deducts the actual fees from your account balance.

      For example, you are charged at 09:30 for the fees that are generated from 08:00 to 09:00.

    • Daily billing

      The billing system calculates the actual resource usage over the previous calendar day at 00:00:00 every calendar day and deducts the actual fees from your account balance.

      For example, you are charged at 00:00:00 on May 6, 2022 for the fees that are generated from 00:00:00 to 23:59:59 on May 5, 2022.

  • Billing formula

    Fees are calculated by using the following formula: Amount of resources used in a specific period of time × Unit price.

By default, the pay-as-you-go billing method is used in DataWorks Basic Edition. You can use all basic core features only after DataWorks Basic Edition is activated. For more information about the pay-as-you-go billing method, see Pay-as-you-go.

Billing on features: editions

The following table describes the billing details of each edition.
Billable item Billing method Description for fees
Basic Edition Free of charge After you activate DataWorks, you can use the features and resources that are supported by DataWorks Basic Edition. You are charged no additional fees for Basic Edition. DataWorks Basic Edition is suitable for beginners and individual developers. If you are an enterprise user, we recommend that you activate DataWorks of an advanced edition.
Advanced editions
  • Standard Edition
  • Professional Edition
  • Enterprise Edition
  • Ultimate Edition
Subscription Advanced editions provide more features than Basic Edition. Features supported by different editions vary. You can activate a DataWorks edition based on your business requirements.
Note
  • After you activate DataWorks of an advanced edition in a region, you can use the features provided by the edition in the existing workspaces in the region or workspaces that are newly created in the region.
  • For more information about the features that are supported by each edition, see Differences among DataWorks editions.
  • For more information about edition upgrade, pricing for each edition, and service suspension and downgrade, see Billing of DataWorks advanced editions.

Billing on resources: Data Integration

When you run data synchronization nodes in Data Integration to synchronize data, the data synchronization nodes occupy resources. You are charged for the resources. The related fees are included in your DataWorks bills. The following table describes the billing details.

Billable item Billing method Billable item description Use scenario Usage note
Exclusive resource group for Data Integration Subscription This type of resource group is managed by Alibaba Cloud and is used only to run data synchronization nodes in Data Integration. After you purchase an exclusive resource group for Data Integration, you can exclusively use resources in the resource group.
  • Large number of data synchronization nodes that must be run in parallel

    If a large number of data synchronization nodes in Data Integration must be run in parallel, you can use exclusive resource groups for Data Integration to ensure that data is transmitted in a fast and reliable manner.

  • Access to the Internet
    Exclusive resource groups for Data Integration can be used to access the Internet. If your data source is deployed on the Internet, you can use an exclusive resource group for Data Integration to access the data source for data synchronization.
    Note Data in some data sources cannot be synchronized over the Internet due to the characteristics of the data sources. For more information, see Supported data source types, readers, and writers.
  • Access to a data source deployed in a complex network environment

    You can use an exclusive resource group for Data Integration to access a data source that is deployed in a complex network environment. For more information about network connectivity solutions that can be used, see Select a network connectivity solution.

  • Real-time data synchronization

    You can use an exclusive resource group for Data Integration to synchronize data in real time.

  • Scheduling fees
    • The scheduling system issues batch data synchronization nodes in Data Integration to the related exclusive resource groups for scheduling and use the resource groups to schedule the nodes. During this process, scheduling fees are generated.
      Note
    • For real-time synchronization nodes, you are not charged fees for scheduling instances generated for batch synchronization nodes.
    • Fees for scheduling instances are charged based on the batch synchronization node that is generated by a data synchronization solution. If no batch synchronization node is generated by the solution, no fees are charged. You must check whether the batch synchronization node is generated after a data synchronization solution is configured and run.
  • Other fees
    Fees and bills for the fees may be generated for nodes that are generated by a data synchronization solution. You are charged the fees for specific configurations of the nodes.
    Note For example, fees for using data sources, computing and storage features of the related compute engine instance, and network services such as Express Connect, Elastic IP Address (EIP), and EIP Bandwidth Plan in a data synchronization node may be generated. All these fees are not included in your DataWorks bills.
  • Number of data synchronization nodes that can be run in parallel

    The number of data synchronization nodes that can be run in parallel on exclusive resource groups for Data Integration with different specifications vary. For more information, see Billing of exclusive resource groups for Data Integration (subscription).

Internet traffic Pay-as-you-go If you use an exclusive resource group for Data Integration or the shared resource group for Data Integration to run a data synchronization node in Data Integration, Internet traffic may be generated during data transmission. You are charged for the generated Internet traffic based on the pay-as-you-go billing method. For more information about the Internet traffic generated during data synchronization and billing details of the generated Internet traffic, see Billing of Internet traffic. N/A
If a data source with a public IP address configured is used for a data synchronization node in Data Integration, fees for Internet traffic are generated regardless of which type of resource group is used to run the node.
Note
  • Fees for Internet traffic generated when you use an exclusive resource group for Data Integration to run a data synchronization node are included in your DataWorks bills. For more information, see Billing of Internet traffic.
  • For more information about the supported data sources, see Supported data source types, readers, and writers.
  • For more information about how to view the nodes that generate Internet traffic during running, see the View the statistics on batch synchronization nodes on the Data Integration tab section in the View the statistics on the Overview page topic.
  • For more information about how to view the generated Internet traffic, see the View the statistics on batch synchronization nodes on the Data Integration tab section in the View the statistics on the Overview page topic.
  • If you run a data synchronization node on a custom resource group and Internet traffic is generated, you are not charged for the generated Internet traffic. Internet traffic may be generated by other cloud services during data transmission. Whether you are charged for the generated Internet traffic is determined based on the pricing policies of the cloud services.

Billing on resources: node scheduling

When you develop nodes in DataStudio and schedule auto triggered nodes, scheduling resources are used and fees for the scheduling resources are generated. You can use the shared resource group for scheduling or an exclusive resource group for scheduling to schedule your auto triggered node. You are charged for an exclusive resource group for scheduling based on the subscription billing method and the shared resource group for scheduling based on the pay-as-you-go billing method. The following table describes the billing details of the two types of resource groups.

Billable item Billing method Billable item description Use scenario Usage note
Exclusive resource group for scheduling Subscription This type of resource group is managed by Alibaba Cloud. After you purchase an exclusive resource group for scheduling, you can exclusively use resources in the resource group. You can plan the scheduling of your nodes based on the specifications of and the number of Elastic Compute Service (ECS) instances in your exclusive resource group for scheduling. For more information, see Overview.
  • Large number of data synchronization nodes that must be run in parallel

    If you want to schedule a large number of nodes on a daily basis, you can use an exclusive resource group for scheduling.

  • High requirement for timeliness

    Resources in the shared resource group for scheduling are shared by all DataWorks tenants. If you have a high requirement for the timeliness of your node, we recommend that you use an exclusive resource group for scheduling.

  • Access to a network environment other than the Internet

    If a data source resides in a network environment other than the Internet and is configured with a whitelist, the shared resource group for scheduling cannot be used to access the data source. If you want to access such a data source, we recommend that you use an exclusive resource group for scheduling.

  • Parallel scheduling of nodes

    The number of nodes that can be scheduled in parallel on an exclusive resource group for scheduling is affected by the specifications of and the number of ECS instances in the resource group. If the number of nodes that are scheduled in parallel on an exclusive resource group for scheduling exceeds the maximum number of nodes that can be scheduled in parallel on the resource group, the nodes that need to be run may wait to be scheduled or wait for resources. In this case, you must appropriately plan the scheduling time of the nodes and configure different scheduling time for the nodes. You can also purchase an exclusive resource group for scheduling with higher specifications or scale out the exclusive resource group for scheduling that you use.

  • Number of nodes that can be scheduled in parallel

    The maximum number of nodes that can be scheduled in parallel on exclusive resource groups for scheduling with different specifications vary. For more information, see Billing of exclusive resource groups for scheduling (subscription).

Note
  • After a node is issued to a compute engine instance, the fees for using the compute engine instance may be generated in the related Alibaba Cloud service. The fees are not included in your DataWorks bills.
  • After you purchase an exclusive resource group for scheduling, you are no longer charged for the scheduling instances. You must make sure that the resource group used to schedule all your nodes is changed to the exclusive resource group for scheduling that is newly purchased. For more information, see Network connectivity and operations on resource groups.
  • You can go to the Workbench Overview tab of Operation Center to view the resource usage of the shared resource group for scheduling. For more information, see View the statistics on the Overview page.
Shared resource group for scheduling Pay-as-you-go
  • Resources in the shared resource group for scheduling are shared by all DataWorks tenants. Tenants may compete for resources during peak hours. As a result, nodes may not be scheduled in time. For more information, see Shared resource group for scheduling.
    Note After you activate DataWorks of a specific edition, the shared resource group for scheduling is provided by default, and you can directly use the resource group.
  • When you use the shared resource group for scheduling to schedule batch nodes, scheduling instances are generated. You are charged for the batch nodes based on the number of scheduling instances.
    Note If you schedule a node by hour or minute, multiple instances are generated for the node by hour or minute every day. You are charged for the scheduling of the node based on the number of instances that are generated and successfully run.

Billing on resources: Alarm

Fees are generated when the Alarm system of DataWorks monitors nodes. The following table describes the billing details.
Billable item Billing method Billable item description
Number of baseline instances Pay-as-you-go All baselines in the Enabled state generate baseline instances. You are charged based on the number of baseline instances that are generated before 23:59 every day.
Note

Billing on resources: Data Quality

You are charged for using Data Quality based on the number of monitoring rules that are triggered by node instances such as auto triggered node instances and data backfill instances. The following table describes the billing details.
Billable item Billing method Billable item description Remarks
Number of monitoring rules that are triggered Pay-as-you-go
You are charged based on the number of monitoring rules that are triggered by node instances. For more information, see Billing of Data Quality.
Note If you use the features provided by Data Quality and your node instances trigger monitoring rules, you are charged fees for checking the quality of data generated by your node instances.

For example, you configure two partition filter expressions for a table of an auto triggered node and two monitoring rules for each of the partition filter expressions. After you associate the auto triggered node with the four monitoring rules, the monitoring rules are triggered when the auto triggered node is run. If the auto triggered node is successfully run, fees for running the four monitoring rules are generated each time the auto triggered node is run.

  • If you use the Data Profiling feature provided by DataMap to detect data in a table, you are charged for the data profiling task in Data Quality.
  • When you run monitoring rules to check data quality, SQL statements for the check are generated and issued to the related compute engine instances. When the SQL statements are executed on the compute engine instances, fees are generated. The fees are included in the bills for the Alibaba Cloud services to which the compute engine instances belong.

Billing on resources: calls to DataService Studio APIs

You can use the shared resource group for DataService Studio whose billing method is pay-as-you-go to call DataService Studio APIs. Resources in the shared resource group for DataService Studio are shared by all DataWorks tenants. DataWorks provides a monthly free quota for API calls for each tenant. After the free quota is used up, fees are generated when you call DataService Studio APIs. You are charged the fees based on the number of API calls that you make and the execution time of API calls. For more information, see DataService Studio.
Note You can go to the Statistics Dashboard page of DataService Studio to view the information about DataService Studio API calls that are made during the last 30 days. For more information, see View the summary information about API statistics.

Billing on resources: calls to DataWorks API operations in the OpenAPI module

You can customize business development modes in the DataWorks OpenAPI module. After you activate DataWorks Enterprise Edition or DataWorks Ultimate Edition, you can call DataWorks API operations to use DataWorks features. You are charged based on the number of API calls that you make. For more information, see Billing of DataWorks API operations.
Note
  • For more information about how to view the number of API calls in the OpenAPI module, see OpenAPI.
  • DataWorks provides a monthly free quota of API calls for each Alibaba Cloud account in each region. After the free quota is used up, you are charged based on the billing rules for API calls in each region. For more information, see Billing standards.

Description for scenarios in which fees generated by using services associated with DataWorks are not included in the bills for DataWorks

Nodes in DataWorks are issued by using services associated with DataWorks to the related compute engine instances for running. During this process, the following types of fees that are charged for using the services but are not included in the bills for DataWorks may be generated:
  • Fees for using network services that are required for running nodes, such as fees for using Express Connect, EIP Bandwidth Plan, and EIP
  • Fees for using data sources in data synchronization
  • Storage and computing fees of compute engine instances
Note For more information about the node issuing mechanism of DataWorks, see Mechanism for issuing nodes.
The following table describes the sample scenarios in which fees are generated by using services associated with DataWorks but are not included in the bills for DataWorks.
No. Sample scenario
1 When you schedule nodes that use compute engines such as AnalyticDB for MySQL, AnalyticDB for PostgreSQL, Hologres, MaxCompute, and E-MapReduce (EMR) in DataWorks, you are charged only fees for node scheduling. The fees are included in your DataWorks bills. Fees for running the nodes are included in the bills for the compute engines. For more information about the billing rule of each compute engine, see the related topic in the documentation for each compute engine.
2 When you run data synchronization nodes in Data Integration, fees for configurations of the nodes may be generated. For example, when you run a data synchronization node in Data Integration, fees for using data sources, computing and storage features of the related compute engine instance, and network services such as Express Connect, EIP Bandwidth Plan, and EIP in the node may be generated. All these fees are not included in your DataWorks bills but are included in the bills for the related Alibaba Cloud services. For more information about the billing rule of the related Alibaba Cloud service, see the related topic in the documentation for the service.
3 When you run data analysis tasks in DataAnalysis, the tasks are issued to the related compute engine instances, and computing and storage fees may be generated in the Alibaba Cloud services to which the compute engine instances belong. The fees are not included in your DataWorks bills but are included in the bills for the Alibaba Cloud services to which the compute engine instances belong. For more information about the billing rule of the related Alibaba Cloud service, see the related topic in the documentation for the service.
4 When you run monitoring rules to check data quality, SQL statements for the check are generated and issued to the related compute engine instances. When the SQL statements are executed on the compute engine instances, computing fees are generated. The computing fees are not included in your DataWorks bills but are included in the bills for the Alibaba Cloud services to which the compute engine instances belong. For more information about the billing rule of the related Alibaba Cloud service, see the related topic in the documentation for the service.