Platform Integration with CloudBase#
CloudBase for Platform is a solution for AI Coding; Vibe Coding; Agent platforms; allowing any platform to configure and manage backends on behalf of users. Users don't need to understand underlying concepts like databases; cloud functions; etc; and can get a usable application backend.
All CloudBase management APIs are available in the CloudBase API Overview, with multi-language SDK support including Python, Java, Go, Node.js, PHP, .NET, C++, and Ruby.
Quick Navigation#
- Employees log in with Tencent Cloud sub-accounts → Sub-account Mode
- No direct Tencent Cloud login required → White-label Mode
Mode Comparison#
| Sub-account Mode | White-label Mode | |
|---|---|---|
| Core Idea | Create a Tencent Cloud sub-account for each employee; implement environment isolation through permission policies | Enterprise's own authentication system as authorization middleware; no Tencent Cloud sub-accounts needed |
| User Account | Tencent Cloud sub-account | Enterprise's own account (SSO / LDAP / platform account) |
| Environment Isolation | CAM permission policy precise to environment level | Temporary credentials + environment ID binding |
| Brand Perception | Users can perceive the Tencent Cloud brand | Users only interact with enterprise/platform domain; no perception of Tencent Cloud |
| Login Entry | Tencent Cloud standard authorization page | Enterprise custom authorization page |
| SSO Integration | Not supported | Supports enterprise LDAP / SSO / unified login |
| Manual Cloud Resource Management | Supported; employees can log in to Tencent Cloud Console via sub-account | Not supported; users have no Tencent Cloud account |
| MCP Credentials | Auth code login or sub-account key | Custom auth code or temporary credentials |
Selection Advice#
The two modes are not mutually exclusive. You can start with Sub-account Mode for a quick launch; and upgrade to White-label Mode after validating the results.
What is CloudBase for Platform?
A solution for AI Coding; Vibe Coding; Agent and other platforms (e.g.; OpenClaw; Lovable; Bolt.new; Vercel v0; Figma Make); allowing any platform / Agent to configure and manage backends on behalf of its users. Platforms want to provide users with a seamless flow and out-of-the-box backend capabilities; without exposing the complexity of underlying resources like databases; cloud functions; object storage, etc. — users don't need to understand these concepts; they can get a usable application with one sentence or simple operations.
What you get: Using CloudBase; provide each of your tenants with an independent environment. Each environment contains databases; cloud functions; HTTP access entry; and static hosting. Tenants are isolated from each other. You can complete automated management of creation; billing; deployment; database; and monitoring through Tencent Cloud APIs.
Applicable scenarios: SaaS; internal business platforms; multi-tenant systems; or AI Coding / Vibe Coding platforms — hoping to provide isolated backend capabilities for each customer/tenant and manage them through APIs rather than just the console.
Management unit: In units of environments. One environment = a complete set of resources for one tenant (database; cloud function; HTTP access service; static hosting; etc.). Usually one tenant per environment. All capabilities are managed programmatically via Tencent Cloud Development API.
Relationship between Tencent Cloud account and environments: Adopt the unified account model — you use one Tencent Cloud account (main account or sub-user with CloudBase permissions); and can create multiple environments under that account. Each tenant corresponds to one environment. Resources and billing for all environments belong to this account; making it convenient for you to manage uniformly and have a unified bill. The number of environments is limited by the account quota. Before creating; you can query the environment count limit; if you need to adjust the limit; you can contact us.
The account; environment; and resource hierarchy is as follows:
Recommended Implementation Order#
- Environment creation and billing: Complete single-tenant environment creation and billing activation; and support usage queries.
- Deploy backend: Deploy HTTP cloud functions; provide external API or WebSocket capabilities.
- HTTP access service and domain: Configure routing and custom domain to implement external exposure and access control.
- Database and permissions: Open the database for tenants; create tables; configure permissions and security rules.
- Monitoring and logs: Troubleshoot and analyze usage through monitoring curves and CLS logs.
If your platform needs to create CloudBase environments rapidly at scale (e.g., SaaS multi-tenant, C-end platforms with large user bases) and has high throughput or response-time requirements for environment provisioning, we offer an Environment Pool API. It supports pre-creating a pool of environments and allocating them on demand, enabling fast provisioning of massive numbers of CloudBase environments.
This capability requires allowlisting — please apply via the CloudBase Help Center or contact your account manager.
Terminology#
| Term | Description |
|---|---|
| Environment | A complete set of resources for one tenant (database; cloud function; HTTP access service; static hosting; etc.). Usually one tenant per environment. |
| HTTP Cloud Function | On-demand executed cloud function; provides URL externally through HTTP access service; suitable for REST APIs; lightweight logic. |
| HTTP Access Service | Unified HTTP entry that forwards requests to HTTP cloud functions according to routing (this term is used in Tencent Cloud documentation). |