Skip to main content

Platform Edition vs. Integration Package

This document is intended for customers already using the Integration package. It introduces the differences between Platform Edition and the Integration package to help you understand how to continue using CloudBase after discontinuation. If you are a new customer, just read the Platform Edition Overview — this document is not needed.

Integration package discontinued

The Integration package will be discontinued on September 30, 2026. After discontinuation, new Integration package environments will no longer be supported, while existing Integration package environments can continue to be used. To create new environments, purchase a Platform Edition package and create environments under it. The platform does not provide data migration, billing changes, or other such features.

Audience​

  • Existing Integration package customers: currently using the Integration package, who want to understand the differences between Platform Edition and the Integration package, and how to continue using CloudBase after discontinuation
  • New customers: please read the Platform Edition documentation directly. Platform Edition meets all your needs

Core Differences​

ItemPlatform EditionIntegration Package
Billing dimensionAccount level (one package covers all environments)Environment level (one package per environment)
Environment creationOn-demand / pre-creation (API)Regular creation, waits 1-3 minutes
Environment scale100k+ environments per accountUp to 1,000 environments per account
Environment status managementManual suspend / start supported (environment level)Not supported; only expiry isolation and overrun service suspension
Expiry logicEnvironment expiry consistent with account packageEach environment expires separately

Key Difference Details​

Billing dimension​

  • Platform Edition: billed at the account (UIN) level. Purchase one Platform Edition package and it covers all environments under the account; environment creation and resource usage are metered and deducted from the package credits. Revenue is tied to package subscriptions, costs are predictable, and billing is not affected by the number of environments customers create.
  • Integration package: billed at the environment level. Each environment purchases a package and is billed separately; the number of environments directly affects costs.

Environment creation​

  • Platform Edition: supports both on-demand creation and pre-creation, suitable for large-scale, high-concurrency environment creation scenarios.
  • Integration package: uses the regular creation flow, which takes 1-3 minutes per environment.

Environment scale​

  • Platform Edition: supports 100k+ environments per account, designed for massive environment scenarios.
  • Integration package: supports up to 1,000 environments per account.

Environment status management​

  • Platform Edition: supports manual suspend / start of environments, allowing you to control the usage status of a single environment according to business strategy.
  • Integration package: does not support manual suspend / start; environments can only enter a suspended state through expiry isolation, overrun service suspension, and similar mechanisms.

How to Choose​

  • Need large-scale environments + account-level unified billing: choose Platform Edition.
  • Currently small scale with a limited number of environments: you can use CloudBase Personal or Standard packages.
  • Existing Integration package customers: existing Integration package environments can continue to be used, but new Integration package environments are not supported after discontinuation. To create new environments, purchase a Platform Edition package and create environments under it. The platform does not provide data migration, billing changes, or other such features.

Next Steps​