CloudBase Platform Integration Solution Overview
The CloudBase Platform Integration solution is designed for platforms such as AI Coding, Vibe Coding, and Agent, allowing any platform to configure and manage backends on behalf of users. Your users can get a usable application backend without understanding underlying concepts such as databases and cloud functions.
The relationship between users, your platform, and CloudBase is as follows:
Users only need to describe their requirements to the Agent; the platform backend creates environments and delivers credentials; with the API Key, the Agent connects directly to the environment and can create databases, deploy cloud functions, and more, without going through the platform backend again.
This document is intended for platform providers / enterprise integrators, with the "environment" as the core management unit, explaining how to integrate CloudBase into your product through Tencent Cloud APIs.
Use Cases
- AI Coding / Vibe Coding platforms: such as Lovable, Bolt.new, Vercel v0, Tencent Tusi, providing isolated backend capabilities for each customer/tenant, managed through APIs rather than only the console
- SaaS and multi-tenant systems: providing independent databases, cloud functions, static hosting and other resources for each tenant
- Enterprise internal business platforms: allocating isolated AI development environments to employees
Core Concepts
The CloudBase Platform Integration solution revolves around three layers: Tencent Cloud account → CloudBase environment → resources within the environment.
| Concept | Description |
|---|---|
| Tencent Cloud account | The management entity in the unified account model. With one Tencent Cloud account (main account or sub-user with CloudBase permissions), you can create multiple environments. All resources and billing of all environments belong to this account, facilitating unified management and unified billing |
| CloudBase environment | A complete set of backend resources for one tenant, typically one environment per tenant. Resources and data are isolated between environments |
| Resources within the environment | The databases, cloud functions, static hosting and other resources contained in the environment, which can be enabled and configured on demand |
The hierarchy of accounts, environments, and resources:
Integration Package
Integration Package is an exclusive package for platform-type customers, designed for enterprise-level applications. When creating an environment, use the package ID baas_integration. It has the following characteristics:
- Lower subscription unit price: compared with the Basic package, the Integration package is more affordable
- Unified credit-based metering: all CloudBase resources are uniformly converted into "credits" for metering and deduction, making usage more transparent
- Overrun pay-as-you-go guarantee: after enabling overrun pay-as-you-go, when the package quota is exhausted, billing automatically switches to pay-as-you-go without interrupting business
- Flexible billing management: supports operations such as renewal and plan changes (upgrade / downgrade package)
The Integration package environment is currently in whitelist release. If you need to use it, please contact us, or submit a Tencent Cloud ticket to activate it.
In addition to the Integration package, CloudBase provides a variety of package specifications to meet the needs of everyone from individual developers to large enterprises. For the conversion between various CloudBase resources (databases, cloud functions, storage, etc.) and credits, see the credits price documentation.
Integration Steps
The first three chapters are the main flow of platform integration. After completing them in order, users can directly operate CloudBase environments through their Agent:
| Chapter | Content | What problem it solves |
|---|---|---|
| Enable and create your first environment | Enable the CloudBase service and create the first environment through APIs | Get through the first step "from nothing to something" |
| Get environment API Key | Issue an API Key for each user environment | Give every user an isolated access credential |
| Connect environments with API Key | Connect client Agents and cloud Agents | Let Agents directly operate cloud resources |
After the API Key is delivered to users, users' Agents can create databases, deploy cloud functions, configure domains, and more. The following chapters are for platform-side environment management scenarios (such as hosting all resources on behalf of users and controlling costs), and are optional advanced content:
| Chapter | Content | What problem it solves |
|---|---|---|
| Manage environment resources | Deploy cloud functions, configure domains, manage databases, monitor logs | Daily operations and maintenance of environments |
| Manage resource quotas | Package, quota and billing management | Control costs, guarantee resources |
In addition to the above chapters, the appendix also collects supplementary content for on-demand reference:
| Chapter | Content | What problem it solves |
|---|---|---|
| Connect environments with other credentials | Two credential methods: custom auth code / temporary key | Suitable for scenarios requiring own-domain login or server-side control of credential lifecycle |
Recommended Implementation Order
If the platform manages resources on its own, it is recommended to implement in the following order:
- Environment creation and billing: complete single-tenant environment creation and billing activation, and support usage queries.
- Deploy backend: deploy HTTP cloud functions to provide external API or WebSocket capabilities.
- HTTP access service and domains: configure routes and custom domains to achieve external exposure and access control.
- Database and permissions: enable databases and create tables for tenants, and configure permissions and security rules.
- Monitoring and logging: troubleshoot and analyze usage through monitoring curves and CLS logs.