Instance Billing

This page describes accounts, top-ups, bills, and the pricing, renewal, configuration changes, cancellation, and overdraft rules for Serverless and standard instances on the MatrixOne instance management platform.

This ledger is separate from Credit and model-usage billing in AI Studio / Genesis. See Costs and Billing.

The prices below are common list-price examples. Purchases and bills are governed by the console and your contract.

Account overview

Entry point: Instance management platform → Billing → Account overview.

Account funds

Component

Description

Cash

Funds added through top-ups

Vouchers

Activated with a code and deducted before cash

Deduction order: Vouchers are used first. When several are valid, the one expiring soonest is used first, followed by the one with the smaller balance. The platform calculates the preceding hour’s usage and deducts charges approximately hourly.

Top-ups

Entry point: Top up at the top of the page, or another billing entry shown in the console.

Common methods:

  • Alipay and WeChat, subject to per-transaction limits shown on the page

  • Corporate bank transfer

Notes:

  • If the account has an outstanding balance, a top-up first pays unpaid bills.

  • A top-up itself generally cannot be invoiced. Request an invoice against consumption after charges are generated.

  • Online withdrawal availability and procedures depend on the console and customer support.

Vouchers

Entry point: Billing → Account overview → Voucher management.

  • Select + Add voucher and enter an activation code. An activated voucher is deducted according to its rules and cannot be returned or exchanged.

  • A voucher is usable only during its validity period; the remaining value becomes unavailable after expiration.

  • Available balance = face value − used − expired − invalidated − not-yet-effective value.

Status

Meaning

Not effective

Activated but before its effective date

Available

Within the validity period with remaining value

Used up / expired / invalidated

Cannot be deducted

Usage records can be filtered by voucher ID and time to inspect successful or failed deductions. The ID generally requires an exact match.

Bill details and transactions

Bill details

Bill details show usage and cost at the minimum billing interval and support multidimensional filters.

Field

Description

List amount

Original price

Rounding adjustment

Amount removed from fractional values according to the rules; aggregated views show the total

Amount payable

List amount − discount − rounding adjustment

Status

Unsettled / unpaid / paid

You can export details as CSV. Complete any security verification requested by the console before downloading.

Transactions

The platform bills and deducts the preceding hour’s consumption approximately hourly. Filter by exact transaction number or transaction time.

Type

Description

Top-up

Adds funds to the account

Consumption

Instance charges

Withdrawal

Returns a balance to the original payment account, subject to availability and console rules

Refund

Returns funds to the platform account balance

Serverless pricing for production instances

CU (Compute Unit)

CU is the basic unit of Serverless compute consumption and reflects CPU, memory, object-storage I/O, public-network traffic, and other resources used by SQL. As an intuitive order-of-magnitude reference, reading about 32 KB of data can correspond to 1 CU. Refer to product billing documentation or the console for exact CPU, memory, and network conversion.

Resource

List-price reference

CU

Approximately ¥1 / 100,000 CU

Storage

Approximately ¥0.15 / GiB-month

Public outbound traffic contributes to compute consumption; private-network access generally does not add public-traffic CU charges. Use the console’s bill breakdown as the final authority.

Free instances have separate free CU and storage quotas and may be restricted when they are exhausted. See Database Instances.

Production instances can also configure spending limits and keep service, choosing whether to stop or continue at low speed after quota exhaustion. See the instance-creation options.

Standard instance pricing

Item

Description

List-price reference

Compute node (CN)

Subscription or pay-as-you-go; common specifications include 8 cores/32 GiB and 16 cores/64 GiB

Pay-as-you-go approximately ¥4.8/hour and ¥9.6/hour; see the purchase page for monthly/annual prices

Data storage

Usage-based

Approximately ¥0.15 / GB-month

Data requests

Object-storage requests made while executing SQL, settled hourly

Approximately ¥0.01 / 10,000 requests

Public traffic

Private access is not billed; public traffic is settled hourly

Approximately ¥0.8 / GB

Monthly or annual subscriptions suit production. Pay-as-you-go is generally more expensive and suits short-term evaluation. The purchase-page discount determines the final price.

Renewal of subscription standard instances

Service pauses after the contract expires. Renewal extends validity and generally cannot be canceled after payment. Use configuration change or cancellation if the configuration must change.

Renew by:

  1. Enabling automatic renewal during instance creation.

  2. Using Renew / Automatic renewal on the instance card and selecting duration and payment method.

You can disable automatic renewal at any time. When enabled, the platform attempts to charge the next period approximately nine days before expiration. Keep sufficient balance.

Configuration changes for standard instances

Entry point: Change configuration on the instance page. The instance enters Changing configuration and usually finishes within minutes. A new bill is generated. Cash settles pre-change bills first, and used vouchers are not refunded.

Pay-as-you-go: No prepaid adjustment. The new configuration is billed from its effective time.

Subscription: Upgrade charges or downgrade refunds are summarized below.

Scenario

Billing rule

Increase node specification, count, or both

Additional amount ≈ (new monthly list price − old monthly list price) ÷ 30 ÷ 24 × remaining subscription time

Decrease specification, count, or both

If cash paid exceeds consumed amount, part of the cash can be refunded in proportion to the configuration difference. If cash paid does not exceed consumption, commonly because vouchers covered much of the order, the refund can be 0. Difference ratio = (old list price − new list price) ÷ old list price.

Increase specification while reducing nodes, or decrease specification while adding nodes

Calculate upgrade charge and downgrade refund separately, then combine them.

The console shows the amount payable or refundable before submission. Use the confirmation-page amount.

Cancellation of subscription standard instances

  • Pay-as-you-go: No cancellation operation; terminate the instance to stop future billing.

  • Subscription: You can request cancellation. Data is generally retained for about seven days and can be restored under platform rules before deletion. Used vouchers are neither refunded nor converted to cash.

Condition

Result

Cash paid > consumed amount

Refund ≈ cash paid − consumed amount

Cash paid ≤ consumed amount, including voucher deductions

Refund = 0

The consumed amount is estimated from used years, months, and days, the corresponding duration discount, and an adjustment factor:

  • Less than 30 days used: factor = 1.5

  • At least 30 days used: factor = 1

  • Partial days count as full days

The daily unit price can be understood as current monthly list price ÷ 30. Use the final amount on the cancellation confirmation page.

Cash overdraft

If cash overdraft is enabled, services can continue within a preset limit when the account balance is insufficient.

  • This capability generally requires an application through an account manager and is not enabled for every account by default.

  • After activation, the overdraft limit appears in Account overview.