All Products
Search
Document Center

Platform For AI:Elastic Algorithm Service (EAS) billing

Last Updated:Sep 09, 2026

Before you deploy model services with EAS, understand the billing rules for different resource types to manage costs effectively. EAS supports pay-as-you-go, subscription, and Serverless billing for the EAS billable items and billing methods.

Billing overview

Deploying services with EAS may incur charges for compute resources, system disks, and dedicated gateways:

  • Compute resources: public resources, EAS dedicated resources, General Computing Resources 2.0, and Lingjun AI Computing resources.

    General Computing Resources 1.0 is available only in DSW and DLC. General Computing Resources 2.0 is available in DSW, DLC, and EAS.
  • System disk (optional): A free quota is provided (30 GiB for public resources, 200 GiB for EAS dedicated resources and General Computing Resources 2.0). Usage beyond the free quota is billed separately.

  • Fully managed dedicated gateway(optional): Services use a shared gateway by default (free of charge). You can also purchase a fully managed dedicated gateway (manual setup required).

EAS supports two billing methods:

  • Pay-as-you-go: Billed based on resource usage duration, not service invocations. Suitable for workloads with unpredictable or fluctuating demand.

    Note

    For SDWebUI, EAS offers a Serverless version. Service deployment is free of charge. You're billed only for the actual processing time when the service handles requests.

  • Subscription: Pay upfront at a discounted rate. Suitable for long-term, stable workloads.

image
Important

If you use other Alibaba Cloud services such as Elastic IP Address (EIP), OSS, or NAS, the charges for those services are billed separately.

Billing period

Pay-as-you-go

For pay-as-you-go resources, note when billing starts and stops to avoid unexpected charges. Stop or delete model services that are no longer in use.

Resource type

Billing start time

Billing end time

Public resources

When the service instance provisions resources (billing applies even without service invocations).

When the model service is stopped (resources are released).

Important

You must stop or delete the service instance.

EAS dedicated resources /

General Computing Resources 2.0

When the machine is created and enters the Running state (billing applies even without deployed services).

  • When the machine resource is deleted.

  • When the machine resource enters the Stopped state.

Important

The Stopped state is triggered only by overdue payments. There is currently no way to manually stop a machine. Delete the pay-as-you-go machine resource to stop billing.

System disk

When the system disk is purchased.

  • When the EAS dedicated resource or General Computing Resources 2.0 machine is deleted.

  • When the service deployed on public resources is deleted.

Dedicated gateway

When the dedicated gateway is created.

When the dedicated gateway is deleted.

Warning

Common misconceptions about stopping pay-as-you-go billing for public resources:

  1. Billing continues during failed service startup: Billing is based on the duration of underlying Pod resource usage. Regardless of whether the service starts successfully, resources are billed for the entire occupation period. You can check whether billing is in progress by checking whether the service instance is marked as Billing in progress on the service overview page.

  2. Service anomaly auto-retry may incur charges: When a deployment anomaly occurs (such as waiting or failure due to insufficient resources), the system continues to automatically retry for up to 48 hours. Monitor the service status and stop or delete abnormal services promptly to avoid continuous billing after a retry succeeds with no one maintaining the service.

  3. Instances in the Stopped state: Services stopped by the system due to overdue payments don't automatically restart after you top up your account. Services that you manually stop are not restarted by scaling policies. To resume the service and billing, manually start the instance in the console or through an API call.

Scaling behavior

  • Scale-out: New resources are billed from the time the scale-out succeeds.

  • Scale-in: Released resources stop billing from the time the release succeeds. Remaining resources continue to be billed.

Subscription

Resource type

Billing start time

Billing end time

EAS dedicated resources /

General Computing Resources 2.0

00:00:00 the day after purchase.

Expiration time.

AI computing resources (Lingjun AI Computing resources)

00:00:00 the day after purchase.

Expiration time.

System disk

When the system disk is purchased.

Expiration time.

Dedicated gateway

When the gateway is purchased.

Expiration time.

Serverless services

Serverless service deployment is free of charge. You're billed only for the actual runtime while the service processes requests.

  • Example: If you submit an image generation request in the WebUI and it takes 10 seconds to generate the image, the billing duration is 10 seconds.

  • Limitations: Currently, only SDWebUI supports Serverless deployment. Check the deployment page for pricing details.

Billable items

The following table describes the billing methods for different resources. Note:

  • Except for Serverless services, pay-as-you-go billing is measured in minutes.

  • For pay-as-you-go public resources, stop unused model services to avoid unnecessary charges.

  • Some instance types may be temporarily unavailable in certain regions.

Billable item

Billing method

Billing formula

Unit price

Public resources

Pay-as-you-go

(specified machine resources)

Bill amount per model service = Number of instances × (CPU cores × (unit price / 60) + Memory × (unit price / 60)) × Duration (minutes)

For pricing details, see Table 1. Specified machine resources.

The prices shown here are hourly for readability. Actual billing is per minute. Divide the hourly price by 60 to get the per-minute price.

Pay-as-you-go (specified instance type)

Bill amount per model service = Number of instances × (Instance type unit price / 60) × Duration (minutes)

Pricing varies by region and instance type. Refer to the console for actual prices.

For the list of supported instance types, see Appendix: Public resource group instance types.

EAS dedicated resources /

General Computing Resources 2.0

Pay-as-you-go

Bill amount per resource group = Number of machine specifications × (Price / 60) × Duration (minutes)

For pricing details, visit the EAS dedicated machine pay-as-you-go purchase page.

Subscription

Bill amount per resource group = Number of machine specifications × Price × Duration (months)

For pricing details, visit the EAS dedicated machine subscription purchase page.

AI computing resources (Lingjun AI Computing resources)

Subscription / Pay-as-you-go

Purchase Lingjun AI Computing resources and use the corresponding resource quota to deploy EAS services.

For AI computing resource billing details, see Billing of AI computing resources.

System disk

Pay-as-you-go

Bill amount = Number of instances (machine specifications) × System disk capacity (GiB) × (Unit price / 60) × Duration (minutes)

For pricing details, visit the Block Storage (PL1 ESSD) page.

Subscription

Bill amount = Number of machine specifications × System disk capacity (GiB) × Unit price × Duration (months)

For pricing details, visit the Block Storage (PL1 ESSD) page.

Dedicated gateway

Pay-as-you-go

Bill amount = (Gateway unit price / 60) × Number of gateway nodes × Duration (minutes)

For pricing details, visit the EAS dedicated gateway pay-as-you-go page.

Subscription

Bill amount = Gateway unit price × Number of gateway nodes × Duration (months)

For subscription pricing details, visit the EAS dedicated gateway subscription page.

Service inference (Serverless)

Billed by actual runtime while the service processes requests

Bill amount = Service inference duration (seconds) × Unit price (per second)

Currently, only SDWebUI supports Serverless deployment. Check the deployment page for pricing details.

Table 1. Specified machine resources

Important

The following pricing information is for reference only. Actual prices are shown on the purchase page.

Resource type

Price

CPU

0.03 (USD/core/hour)

Memory

0.004 (USD/GB/hour)

Usage notes

All prices in this topic are for reference only. Actual prices are shown on your invoice.

Billing examples

Important

The following billing examples are for reference only. Actual prices are shown on the purchase page.

Public resource group billing examples

Pay-as-you-go example

  • Scenario: Deploy a model service in the public resource group using specified machine resources in the China (Hangzhou) region.

    • 09:00:00 — The service enters the Running state with 2 CPU cores + 8 GB memory.

    • 10:00:00 — Scale-in completes. Resources are reduced to 1 CPU core + 4 GB memory.

    • 11:00:00 — Scale-out completes. Resources increase to 4 CPU cores + 16 GB memory.

    • 12:00:00 — The service is stopped.

  • Cost calculation:

    Bill amount = (2 × 0.03 + 8 × 0.004) + (1 × 0.03 + 4 × 0.004) + (4 × 0.03 + 16 × 0.004) = 0.322 USD

EAS dedicated resource billing examples

Subscription example

  • Scenario:

    Purchase 2 machines, each with 4 CPU cores + 15 GB GPU T4, in the China (Hangzhou) region with a 3-month subscription at 570 USD/month (actual price may vary).

  • Cost calculation:

  • Total = 2 × 570 × 3 = 3420 USD

Pay-as-you-go example

  • Scenario:

    Purchase 2 ecs.g6.6xlarge machines (24 CPU cores + 96 GB) in the China (Hangzhou) region using pay-as-you-go billing for 45 minutes at 1.02 USD/hour (actual price may vary).

  • Cost calculation:

  • Bill amount = 2 × (1.02 / 60) × 45 = 1.53 USD

System disk billing examples

Subscription example

  • Scenario: Purchase 2 machine resources with EAS dedicated resources on subscription, each with a 300 GiB system disk, in the China (Hangzhou) region for 3 months.

  • Cost calculation:

  • Bill amount = 2 × (300 - 200) × 0.153 × 3 = 91.8 USD

Pay-as-you-go example

  • EAS dedicated resources

    • Scenario: Purchase 2 machine resources with EAS dedicated resources on pay-as-you-go, each with a 300 GiB system disk, in the China (Hangzhou) region for 5 hours.

    • Cost calculation:

    • Bill amount = 2 × (300 - 200) × 0.000319 × 5 = 0.319 USD
  • Public resource group

    • Scenario: Purchase 2 instance nodes in the public resource group on pay-as-you-go, each with a 300 GiB system disk, in the China (Hangzhou) region for 5 hours.

    • Cost calculation:

    • Bill amount = 2 × (300 - 30) × 0.000319 × 5 = 0.8613 USD

FAQ

Q: How do I view deduction details?

On the Billing Details page, filter by PAI to view the detailed bill. For details, see View PAI billing details.

Q: How do I view pay-as-you-go billing details and the corresponding resource ID for EAS public resources?

  1. Get the resource instance ID:

    The resource instance ID in EAS public resource pay-as-you-go bills uses the format <service instance ID>;<service ID>. To find it:

    1. Log on to the PAI console and go to the Elastic Algorithm Service (EAS) page. On the Inference Service tab, find the service deployed on public resources and get the service ID.

    2. Click the service name to go to the details page. At the bottom of the Overview tab, get the service instance ID from the Service Instance section.

      If the service is stopped, the instance ID isn't available here.
  2. View billing details: Go to the Bill Details page. Filter by product name EAS Service Pay-As-You-Go and resource instance ID <service instance ID>;<service ID>.

Note

If you receive an overdue payment notification but can't find the corresponding instance in the console, check the service lists in all regions (especially China (Shanghai) and China (Hangzhou)) for any undeleted residual instances.

Q: Why did PAI-EAS generate a 0 CNY order after activation when no instances were created?

Activating EAS pay-as-you-go billing is free. The 0 CNY order simply confirms that the service module has been activated. Billing occurs only when EAS instances (Pods) are actually created. If no running EAS instances are found in the console, no charges are incurred.

Q: How is the SLA compensation calculated for PAI-EAS service issues?

EAS SLA compensation is calculated per individual service (task), based on the downtime of the affected service and all resources used by that service, not on the total resources across your account.

Q: Why am I still being charged after stopping an EAS service?

  • Bill delay: For DSW/EAS pay-as-you-go billing, there's a delay in bill generation and deduction. The charge notification you received may reflect actual usage before you stopped the instance, not charges incurred after stopping.

  • EAS service running in the background: A service that you don't use is still running. As long as the service isn't manually stopped or deleted, it continues to incur charges for resource usage. Before deleting, make sure all necessary data is backed up.

Q: Why am I still being charged when using EAS trial resources?

  • Cause: When deploying stable-diffusion-webui or comfyui in EAS, if the selected image version includes the -api or -cluster suffix, an async queue resource is provisioned during deployment. This resource is billed and can't be offset by EAS trial resources.

  • Solution: When deploying stable-diffusion-webui or comfyui, select the standard version — an image version with -standard or no suffix.

Q: Do I need to manually release the PAI savings plan after it expires?

No. The PAI savings plan is a pre-paid product that expires automatically. No manual release or deletion is needed, and no additional charges are incurred. After receiving the expiration notification, you don't need to take any action if you no longer need the service. If you have running EAS service instances in the PAI console that you no longer use, stop or delete them to avoid pay-as-you-go charges.

Q: How do I check whether my savings plan or free trial credits are exhausted?

Log on to the Billing and Cost Management console, go to the My Subscriptions page to check the remaining balance and validity period of the savings plan. If the credits are exhausted or expired, continued use of EAS public resource group services is billed at standard pay-as-you-go rates.

Appendix: Public resource group instance types

The following lists some public resource instance types supported by EAS. For a complete list, go to the custom deployment configuration page and check the Resource Information section. For details, see Custom deployment. Available instance types vary by region. Refer to the console for the actual list.

CPU types

Instance type

vCPU

Memory (GB)

ecs.c7.large

2

4

ecs.c7.xlarge

4

8

ecs.c7.2xlarge

8

16

ecs.c7.4xlarge

16

32

ecs.c7.6xlarge

24

48

ecs.c7.8xlarge

32

64

ecs.c7.16xlarge

64

128

ecs.r7.4xlarge

16

128

ecs.r7.large

2

16

ecs.r7.xlarge

4

32

ecs.r7.2xlarge

8

64

ecs.r7.6xlarge

24

192

ecs.r7.8xlarge

32

256

ecs.r7.16xlarge

64

512

ecs.g7.large

2

8

ecs.g7.xlarge

4

16

ecs.g7.2xlarge

8

32

ecs.g7.4xlarge

16

64

ecs.g7.6xlarge

24

96

ecs.g7.8xlarge

32

128

ecs.g7.16xlarge

64

256

ecs.g6.large

2

8

ecs.g6.xlarge

4

16

ecs.g6.2xlarge

8

32

ecs.g6.4xlarge

16

64

ecs.g6.6xlarge

24

96

ecs.g6.8xlarge

32

128

ecs.c6.large

2

4

ecs.c6.xlarge

4

8

ecs.c6.2xlarge

8

16

ecs.c6.4xlarge

16

32

ecs.c6.6xlarge

24

48

ecs.c6.8xlarge

32

64

ecs.r6.large

2

16

ecs.r6.xlarge

4

32

ecs.r6.2xlarge

8

64

ecs.r6.4xlarge

16

128

ecs.r6.6xlarge

24

192

ecs.r6.8xlarge

32

256

ecs.g5.6xlarge

24

96

ecs.c5.6xlarge

24

48

ecs.g8y.large

2

8

ecs.g8y.xlarge

4

16

ecs.g8y.2xlarge

8

32

ecs.g8y.4xlarge

16

64

ecs.g8y.8xlarge

32

128

ecs.g8y.16xlarge

64

256

ecs.c7a.large

2

4

ecs.c7a.xlarge

4

8

ecs.c7a.2xlarge

8

16

ecs.c7a.4xlarge

16

32

ecs.c7a.8xlarge

32

64

ecs.c7a.16xlarge

64

128

ecs.g7a.large

2

8

ecs.g7a.xlarge

4

16

ecs.g7a.2xlarge

8

32

ecs.g7a.4xlarge

16

64

ecs.g7a.8xlarge

32

128

ecs.g7a.16xlarge

64

256

GPU types

Instance type

vCPU

Memory (GB)

GPU memory

ml.gu7i.c8m30.1-gu30

8

30

1 * 24 GB

ml.gu7i.c16m60.1-gu30

16

60

1 * 24 GB

ml.gu7i.c32m188.1-gu30

32

188

1 * 24 GB

ml.gu7i.c64m376.2-gu30

64

376

2 * 24 GB

ml.gu7i.c128m752.4-gu30

80

256

4 * 24 GB

ecs.gn5i-c4g1.xlarge

4

16

1 * 8 GB

ecs.gn5i-c8g1.2xlarge

8

32

1 * 8 GB

ecs.gn5-c4g1.xlarge

4

30

1 * 16 GB

ecs.gn5-c8g1.2xlarge

8

60

1 * 16 GB

ecs.gn5-c8g1.4xlarge

16

120

2 * 16 GB

ecs.gn5-c28g1.7xlarge

28

112

1 * 16 GB

ecs.vgn6i-m4-vws.xlarge

4

23

1 * 4 GB

ecs.vgn6i-m8-vws.2xlarge

10

46

1 * 8 GB

ecs.gn6i-c4g1.xlarge

4

15

1 * 16 GB

ecs.gn6i-c8g1.2xlarge

8

31

1 * 16 GB

ecs.gn6i-c16g1.4xlarge

16

62

1 * 16 GB

ecs.gn6i-c24g1.6xlarge

24

93

1 * 16 GB

ecs.gn6i-c24g1.12xlarge

48

186

2 * 16 GB

ecs.gn6i-c24g1.24xlarge

96

372

4 * 16 GB

ecs.gn7i-c8g1.2xlarge

8

30

1 * 24 GB

ecs.gn7i-c16g1.4xlarge

16

60

1 * 24 GB

ecs.gn7i-c32g1.8xlarge

32

188

1 * 24 GB

ecs.gn7i-c32g1.16xlarge

64

376

2 * 24 GB

ecs.gn7i-c32g1.32xlarge

128

752

4 * 24 GB

ecs.gn6v-c8g1.2xlarge

8

32

1 * 16 GB

ecs.gn6v-c8g1.4xlarge

16

64

2 * 16 GB

ecs.gn6v-c8g1.8xlarge

32

128

4 * 16 GB

ecs.gn6e-c12g1.3xlarge

12

92

1 * 32 GB

ecs.gn6e-c12g1.12xlarge

48

368

4 * 32 GB

ecs.gn6e-c12g1.24xlarge

96

736

8 * 32 GB

ecs.gn7-c12g1.3xlarge

12

94

1 * 40 GB

ecs.gn7-c13g1.13xlarge

52

378

4 * 40 GB

ecs.gn7-c13g1.26xlarge

104

756

8 * 40 GB

ecs.gn7-c13g1.6xlarge

26

189

2 * 40 GB

ecs.gn7e-c16g1.4xlarge

16

125

1 * 80 GB

ecs.gn7e-c16g1.8xlarge

32

250

2 * 80 GB

ecs.gn7e-c16g1.16xlarge

64

500

4 * 80 GB

ecs.gn7e-c16g1.32xlarge

128

1000

8 * 80 GB