Pay-as-you-go allows you to use all the basic features of DataWorks at a low cost. After you activate DataWorks in pay-as-you-go mode, you can perform the following operations in DataWorks: develop nodes, run nodes on a scheduled basis, schedule sync nodes, monitor a large number of workflows, monitor data quality, call API operations that are compiled in DataService Studio, and debug code in App Studio.

Notice
  • New users must activate DataWorks in pay-as-you-go mode first.
  • During peak hours, nodes that are run on shared resource groups for scheduling and shared resource groups for Data Integration share resources. Nodes may keep waiting for resources and fail to generate instances. Sync nodes may not be allocated a sufficient number of threads for data transmission. If you want to guarantee the concurrent running of nodes, purchase DataWorks exclusive resources.

Billing items

When DataWorks is activated in pay-as-you-go mode, the following billing items apply:
  • Shared resource groups for scheduling
  • Shared resource groups for Data Integration
  • Baseline instances generated by Intelligent Monitor
  • Data Quality checks
  • Calls and execution time of APIs compiled in DataService Studio
  • App Studio workspaces for development environments
  • Internet traffic generated by Data Integration
Note
  • You are billed only when you use these resources.
  • After you activate these billing items, the system automatically activates DataWorks Basic Edition for free.
  • If you run a smoke test in the development environment, instances are generated and billed.

For more information, see DataWorks billing details in pay-as-you-go mode.

Shared resource groups for scheduling

  • Billing range
    Except for the instances generated by zero load nodes, all instances generated by nodes that are committed to the scheduling system are included in the billing range. The instances include auto triggered node instances, manually triggered node instances, test instances, and retroactive instances.
    Note Nodes that are run on exclusive resource groups for scheduling are not counted in the number of nodes that are run on shared resource groups for scheduling. For more information, see Exclusive resources for scheduling.
  • Billing standards
    This billing item is billed daily according to a tiered pricing schedule based on the total number of instances that are run per day. The following table lists the billing standards.
    Region Minimum number of instances Maximum number of instances Billing cycle Price (USD/day)
    China (Hangzhou)

    China (Shanghai)

    China (Beijing)

    China (Shenzhen)

    China (Hong Kong)

    1 10 Daily 0
    11 500 Daily 0.15
    501 5,000 Daily 9.29
    5,001 20,000 Daily 23.22
    20,001 50,000 Daily 41.79
    50,001 120,000 Daily 92.87
    Singapore

    Australia (Sydney)

    Malaysia (Kuala Lumpur)

    Indonesia (Jakarta)

    Japan (Tokyo)

    US (Silicon Valley)

    US (Virginia)

    Germany (Frankfurt)

    UK (London)

    UAE (Dubai)

    1 10 Daily 0
    11 500 Daily 0.23
    501 5,000 Daily 13.93
    5,001 20,000 Daily 34.82
    20,001 50,000 Daily 62.68
    50,001 120,000 Daily 139.30
    Note
    • Only instances that have been run in Operation Center are billed. Instances that have been generated but not run, instances that are frozen, and dry-run instances are not billed.
    • If the number of instances per day exceeds 120,000, the excess instances cannot be scheduled. If your actual business volume exceeds this threshold, submit a ticket to seek technical help from Alibaba Cloud.
  • Deduction method

    At 00:00 every day, the billing system starts to settle the number of instances that were run on the previous calendar day and deducts a fee based on only one of the pricing tiers specified in the preceding billing standards. No additional fees are generated.

    Assume that you deploy a DataWorks workspace in the China (Shanghai) region and run 502 instances on April 30, 2019. The billing system deducts a fee of USD 9.26 from your account balance after 00:00 on May 1, 2019.

  • Overdue payments

    If your account has an overdue payment, you are given a 360-hour grace period. The billing system sends a notification at the 192nd, 288th, and 336th hours and reminds you to add funds to your account as soon as possible.

    • If your bill is overdue for more than 360 hours, the service will be suspended. At this time, instances that have not run cannot be started, but instances that have already started can run until they are finished.
    • If you add funds to your account within 360 hours after your bill becomes overdue, the service will not be suspended.
    • If the service payment becomes overdue again after settlement, you are given another 360-hour grace period before the service is suspended.

Shared resource groups for Data Integration

  • Billing range

    The billing system bills you for the concurrent threads that are used to run data integration node instances when they are generated and run as auto triggered node instances, retroactive instances, manually triggered node instances, node instances in DataStudio workflows, or smoke test instances.

    Note
    • Data integration node instances consume both shared resource groups for Data Integration (pay-as-you-go) and shared resource groups for scheduling (pay-as-you-go).
    • Nodes that are run on exclusive resource groups for Data Integration are not counted in the number of nodes that are run on shared resource groups for Data Integration. For more information, see Exclusive resources for Data Integration.
  • Billing standards

    This billing item is billed daily according to a tiered pricing schedule based on the total number of threads generated when data integration nodes are scheduled per day. The following table lists the billing standards.

    Region Minimum number of threads Maximum number of threads Billing cycle Price (USD/day)
    China (Hangzhou)

    China (Shanghai)

    China (Beijing)

    China (Shenzhen)

    China (Hong Kong)

    1 10 Daily 0
    11 500 Daily 0.15
    501 5,000 Daily 0.93
    5,001 20,000 Daily 3.10
    20,001 50,000 Daily 7.74
    50,001 120,000 Daily 15.48
    Singapore

    Australia (Sydney)

    Malaysia (Kuala Lumpur)

    Indonesia (Jakarta)

    Japan (Tokyo)

    US (Silicon Valley)

    US (Virginia)

    Germany (Frankfurt)

    UK (London)

    UAE (Dubai)

    1 10 Daily 0
    11 500 Daily 0.23
    501 5,000 Daily 1.39
    5,001 20,000 Daily 4.64
    20,001 50,000 Daily 11.61
    50,001 120,000 Daily 23.22
    Note If the number of threads per day exceeds 120,000, the excess threads cannot be scheduled. If your actual business volume exceeds this threshold, submit a ticket to seek technical help from Alibaba Cloud.
  • Deduction method

    At 00:00 every day, the billing system starts to settle the number of instances that were run on the previous calendar day and deducts a fee based on only one of the pricing tiers specified in the preceding billing standards. No additional fees are generated.

    Assume that you configure two sync nodes (Node A and Node B) in your DataWorks workspace in the China (Shanghai) region and use shared resources to run these nodes. If you set the concurrency of Node A to 2 and schedule it on a daily basis, the system generates one instance every day. If you set the concurrency of Node B to 5 and schedule it on an hourly basis, the system generates 24 instances every day.

    If all node instances are run, you are billed as follows:
    1. Total concurrent threads settled each day: 2 × 1 + 5 × 24 = 122.
    2. The number of daily concurrent threads is 122, which is in the 11 to 500 tier. According to the price for this tier, you are charged a daily fee of USD 0.15.
  • Overdue payments
    If your account has an overdue payment, you are given a 360-hour grace period. The billing system sends a notification at the 192nd, 288th, and 336th hours and reminds you to add funds to your account as soon as possible.
    • If your bill is overdue for more than 360 hours, the service will be suspended. At this time, instances that have not run cannot be started, but instances that have already started can run until they are finished.
    • If you add funds to your account within 360 hours after your bill becomes overdue, the service will not be suspended.
    • If the service payment becomes overdue again after settlement, you are given another 360-hour grace period before the service is suspended.

Internet traffic generated by Data Integration

  • Billing range

    When data integration nodes are run on shared resource groups or exclusive resource groups, the Internet traffic they generate is billed on a pay-as-you-go basis. The unit price is USD 0.12/GB.

    Note When Internet traffic is generated, DataWorks does not charge for the Internet traffic generated by nodes that are run on custom resource groups. You may be billed for the Internet traffic generated by other cloud services during data transmission, depending on the pricing policies of the corresponding services.
  • Deduction method

    The billing system calculates your fee for the previous hour and generates a bill at the start of each hour. Then, the actual fee is deducted from the balance of your Alibaba Cloud account.

    For example, the billing system bills you at 09:30 for the charges incurred from 08:00 to 09:00.

    Note If your usage is less than 1 GB in an hour, the system bills you for 1 GB. For example, if your usage in an hour is 345 MB, the billing system sends you a bill of CNY 0.8 for 1 GB at the start of the next hour. If your usage in each hour within one day is less than 1 GB, the billing system bills you daily CNY 19.2 for 24 GB at most.
  • Overdue payments

    If your account has an overdue payment, you are given a 360-hour grace period. The billing system sends a notification at the 192nd, 288th, and 336th hours and reminds you to add funds to your account as soon as possible.

    • If your bill is overdue for more than 360 hours, the service will be suspended. At this time, instances that have not run cannot be started, but instances that have already started can run until they are finished.
    • If you add funds to your account within 360 hours after your bill becomes overdue, the service will not be suspended.
    • If the service payment becomes overdue again after settlement, you are given another 360-hour grace period before the service is suspended.

Calls and execution time of APIs compiled in DataService Studio

  • Billing range
    The billing system bills you for the calls and execution time of APIs that are compiled in DataService Studio. All users receive a free quota each month. The billing system bills you only for valid calls to APIs compiled in DataService Studio, including online test calls.
    • Valid calls are API requests that receive a response with an error code of 0.
    • Invalid calls are API requests that receive a response with an error code other than 0.
  • Billing standards
    Billing item Unit Unit price Remarks
    Number of API calls Million calls USD 0.21/million calls None
    Execution time Memory × seconds (GB×s) USD 0.000017193/GB×s The minimum unit of time that the billing system bills you for is 100 ms. A time shorter than 100 ms is calculated as 100 ms.
    DataService Studio provides a free quota for each user every month. The Resource Access Management (RAM) users of an Alibaba Cloud account share the monthly free quota with the Alibaba Cloud account.
    • Number of API calls: The first 1 million API calls that a user makes per month are free.
    • Execution time: The first 400,000 GB×s of execution time for API calls that a user makes per month is free.
    Note The free quota is recalculated at the start of each month. Any remaining quota from the previous month does not roll over.
    For example, if you make 10 million API calls this month, and each call occupies 2 GB and takes 1,060 ms, you are billed as follows:
    • Monthly API calls and fee

      You receive a free quota of 1 million calls per month, so the number of API calls to be billed this month is: 10 million - 1 million = 9 million. The price of every 1 million calls is USD 0.21, so the total fee for the number of API calls this month is: 900/100 × 0.21 = USD 1.89.

    • Monthly execution time and fee

      The execution time of API calls is measured in memory (GB) × seconds, that is, GB×s. The minimum unit of time that the billing system bills you for is 100 ms. A time shorter than 100 ms is calculated as 100 ms.

      Your total execution time of API calls = Number of calls × Memory consumed per call (GB) × Running time per call (seconds) = 10,000,000 × 2 × 1.1 = 22,000,000 GB×s. You receive a free execution time quota of 400,000 GB×s each month, so the actual execution time to be billed is: 22,000,000 - 400,000 = 21,600,000 GB×s. The price per GB×s of execution time is USD 0.000017193, so the total fee of execution time this month is: 21,600,000 × 0.000017193 = USD 371.37.

    • Total monthly fee

      Total monthly fee = Monthly API call fee + Monthly execution time fee = 1.89 + 371.37 = USD 373.26.

  • Deduction method

    DataService Studio has an hourly billing cycle. The billing system calculates your fee for the previous hour and generates a bill at the start of each hour. Then, the actual fee is deducted from the balance of your Alibaba Cloud account.

  • Overdue payments

    If your account has an overdue payment, you are given a 360-hour grace period. The billing system sends a notification at the 192nd, 288th, and 336th hours and reminds you to add funds to your account as soon as possible.

    • If your bill is overdue for more than 360 hours, the service will be suspended and you will be unable to call the deployed APIs.
    • If you add funds to your account within 360 hours after your bill becomes overdue, the service will not be suspended.
    • If the service payment becomes overdue again after settlement, you are given another 360-hour grace period before the service is suspended.

Data Quality checks

  • Billing range

    The billing system bills you for the Data Quality checks that are generated by Data Quality within each calendar day. Such Data Quality checks are generated when Data Quality rules are triggered by auto triggered node instances, retroactive instances, or rule tests.

  • Billing standards
    Data Quality checks per day Price (USD/day)
    1 to 10 0
    11 to 200 3.10
    201 to 1,000 7.74
    1,001 to 5,000 30.96
    5,000 to 10,000 46.43
  • Deduction method

    At 00:00 every day, the billing system starts to settle the number of Data Quality checks that were run on the previous calendar day and deducts a fee based on only one of the pricing tiers specified in the preceding billing standards. No additional fees are generated.

    • A Data Quality check is run and billed when the corresponding Data Quality rules are triggered and alerts are reported or workflows are blocked due to data quality problems.
    • The upper limit for Data Quality checks in pay-as-you-go mode is 5,000 per day. After this threshold is reached, Data Quality checks stop running. If you need more Data Quality checks per day, submit a ticket to seek technical help from Alibaba Cloud.
  • Overdue payments

    If your account has an overdue payment, you are given a 24-hour grace period. The billing system sends a notification at the 12th and 23rd hours and reminds you to add funds to your account as soon as possible.

    • If your bill is overdue for more than 24 hours, the service will be suspended. In this case, you cannot start new Data Quality checks, but Data Quality checks that have already started are not affected.
    • If you add funds to your account within 24 hours after your bill becomes overdue, the service will not be suspended.
    • If the service payment becomes overdue again after settlement, you are given another 24-hour grace period before the service is suspended.

Baseline instances generated by Intelligent Monitor

  • Billing range

    All enabled baselines generate baseline instances and you are billed based on the number of baseline instances generated before 23:59 each day.

  • Billing standards
    Baseline instances per day Price (USD/day)
    1 to 2 0
    3 to 10 0.77
    11 to 100 3.10
  • Deduction method

    At 00:00 every day, the billing system starts to settle the number of baseline instances that were run on the previous business day and deducts a fee based on only one of the pricing tiers specified in the preceding billing standards. No additional fees are generated.

    • The billing system calculates one baseline instance for an hourly baseline of an hourly node.
    • The upper limit of baseline instances for enabled baselines in pay-as-you-go mode is 100 per day. After this threshold is reached, no more baseline instances can be generated. If you need more baseline instances per day, submit a ticket to seek technical help from Alibaba Cloud.
  • Overdue payments

    If your account has an overdue payment, you are given a 24-hour grace period. The billing system sends a notification at the 12th and 23rd hours and reminds you to add funds to your account as soon as possible.

    • If your bill is overdue for more than 24 hours, the service will be suspended. In this case, no more baseline instances can be generated, but baseline instances that have already started are not affected.
    • If you add funds to your account within 24 hours after your bill becomes overdue, the service will not be suspended. If the service payment becomes overdue again after settlement, you are given another 24-hour grace period before the service is suspended.

App Studio workspaces for development environments

  • Billing standards
    This billing item charges for code debugging in App Studio workspaces for development environments on an hourly basis. The following table lists the billing standards.
    App Studio workspace for development environments Code debugging price (USD/hour) Region
    1c2g 0.12 China (Shanghai)

    China (Hangzhou)

    China (Shenzhen)

    China (Beijing)

    2c4g 0.25
    4c8g 0.50
    8c16g 0.99
    Note The first 2 billable hours of each month are free. The following table lists the conversion between the actual debugging time and consumed billable hours.
    App Studio workspace for development environments Actual debugging time (hours) Consumed billable hours
    1c2g 1 1
    2c4g 1 2
    4c8g 1 4
    8c16g 1 8
  • Deduction method

    Billing starts when you start to debug code and ends when you stop debugging code.

    If you modify the instance specifications in the debugging configuration, the debugging fee is billed based on the modified configuration.

  • Overdue payments

    If your account has an overdue payment, you are given a 24-hour grace period. The billing system sends a notification at the 12th and 23rd hours and reminds you to add funds to your account as soon as possible.

    • If your bill is overdue for more than 24 hours, the service will be suspended. If you are debugging code at this time, the current process will not be interrupted. However, if you stop debugging code, the debugging cannot be resumed.
    • If you add funds to your account within 24 hours after your bill becomes overdue, the service will not be suspended.
    • If the service payment becomes overdue again after settlement, you are given another 24-hour grace period before the service is suspended.