Plans & Pricing

The Enterprise plans are designed for businesses and teams, providing centralized management, collaboration, and security capabilities, including:

• Centralized billing: Organization billing is managed and paid centrally by admins, with support for limiting resource usage quotas.
• Admin console: Manage member access permissions, model usage restrictions, data privacy modes, and more.
• Domain control: Restrict access to specific email domains.
• Single Sign-On (SSO): Support for enterprise-grade authentication.
• Analytics & Insights: Data metrics and analysis.
• Capability management and distribution: Plugin/Skill management and sharing.
• Knowledge engine: Maximize team knowledge value.

​

Plan Comparison

​

Subscription Pricing & Seat Quotas

The Enterprise plans are priced per seat, with support for purchasing Shared Add-on Credits for organization-wide consumption.

​

Seat Management

When a user in the organization is assigned a billable role, they occupy a seat. Once occupied, the seat is billed for the current billing cycle. If the user is later removed from the organization, any seat charges already incurred are non-refundable. For details about adding and removing members, see Members and Roles.

• Enterprise: After a member is removed from the organization, their seat is automatically released and returned to the unassigned pool. It can be reassigned to another member within the current billing cycle at no additional charge.
• Teams: Seats include Credits. Once any Credits from a seat have been used, the seat is bound to that member's account and cannot be reassigned to another user during the current billing cycle.

Enterprise plan subscriptions support adjusting seat counts at any time, with bills calculated immediately:

​

Shared Add-on Credits

Administrators can purchase Shared Add-on Credits to supplement model compute capacity. These credits form a shared pool available to all organization members. For complete details, see the Shared Add-on Credits guide.

​

Billing & Payment Management

Enterprise plans support centralized billing. For organizations that purchased on the official website:

• Order management: Navigate to Organization Settings > Subscription & Billing > Orders to review past orders, pay outstanding invoices, or cancel pending orders.
• Payment methods: Manage credit cards, set a default payment method, and update billing addresses under Organization Settings > Subscription & Billing > Manage Payment Information. Note: Updates apply to future transactions only.

For organizations that purchased through the cloud marketplace:

• Billing and payment methods are managed within the Alibaba Cloud marketplace account. Please go to Alibaba Cloud Marketplace to manage.

​

Billing Cycle

The following billing cycle rules apply to all plans except the Cloud Marketplace Teams Edition. For the Cloud Marketplace Teams Edition, see the special note below.

​

New Purchase Scenarios

Subscriptions are billed monthly or annually. A monthly subscription cycle is calculated as follows:

1. Add one calendar month to the purchase time.
2. If the target month does not have the corresponding day, use the same time on the last day of that month.
3. Move the resulting time forward to the next midnight (00:00). This is the subscription cycle end time.

Auto-renewal charges are deducted 9 days before the cycle expires. If the auto-renewal payment fails, the subscription for the next cycle will be unavailable. Monthly billing cycle examples: Annual billing cycle examples:

• Regular subscription: If you subscribe on August 16, 2025, the current billing cycle ends at midnight on August 17, 2026.
• Month-end subscription: If you subscribe on January 31, 2025, the current billing cycle ends at midnight on February 1, 2026.

​

Renewal Scenarios

Renewals do not apply the new-purchase rule of moving the calculated time forward to midnight. Instead, each renewal cycle advances by one calendar month from the previous cycle's end time. For a monthly subscription, the renewal cycle is calculated as follows:

1. The start time is the end time of the previous cycle.
2. The end time is midnight on the same date one calendar month after the start time. If the next month does not have the corresponding date, use midnight on the last day of that month.

Monthly renewal cycle examples: Transition from new purchase to renewal: If you purchase a monthly subscription on September 30 at 05:00, the first cycle ends on October 31 at 00:00. After renewal, the next cycle runs from October 31 at 00:00 to November 30 at 00:00, not December 1 at 00:00. Continuous renewal example: Because each renewal is calculated from the previous cycle's end date, the expiration date moves earlier after a shorter month and does not automatically return to the original date. For example, if the previous cycle ends on July 31 at 00:00, subsequent cycles end at 00:00 on August 31, September 30, October 30, November 30, December 30, and January 30 of the following year. If the following year is not a leap year, the next cycle ends on February 28 at 00:00, and subsequent cycles use the 28th as their reference date. If it is a leap year, the next cycle ends on February 29 at 00:00, and subsequent cycles use the 29th until a non-leap-year February shifts the reference date to the 28th; all later cycles then use the 28th.

​

Special Note: Cloud Marketplace Teams Edition Billing Cycle Rules

The Cloud Marketplace Teams Edition uses a redemption-code balance top-up model. The expiration time is not normalized to midnight; instead, it falls on the exact order time on the corresponding date of the next month. Teams subscriptions activated via cloud marketplace redemption codes follow these rules: Upon first redemption and activation, the subscription cycle is calculated as one calendar month from the activation time; if the next month does not have the same date, the expiration falls on the last day of that month.

• Example: First activation on August 5 at 10:00 — the current cycle runs until September 5 at 10:00; if first activation is on January 31 at 10:00 — since February has no 31st, the expiration is February 28 at 10:00, and subsequent cycles continue on the 31st, 30th, etc., of each month.