White Label Platform Overview: A Brand Operating Studio and API Platform

White label sites allow you to use your own name, logo, domain, directory, and customer service on a shared platform to operate an AI Studio or API developer portal. It does not replicate a set of code or establish an independent ledger, but rather resolves the access domain to the corresponding site configuration.

This series uses "Zhishuyun" as a continuous case study:

studio.zhishuyun.com    AI Studio for creators and general users
platform.zhishuyun.com  Service, pricing, and documentation portal for developers
xapi.zhishuyun.com      API request entry for developers

¶ What You Will Get After Completing This Series

• A Studio using your own brand, capability directory, channel pricing, and customer service information;
• A developer portal showcasing selected API services, pricing, documentation, and navigation;
• Two page domain names and one API domain name, all accessible via HTTPS;
• A set of registration, login, purchase, API Key, usage records, and customer attribution acceptance processes;
• A repeatable inspection and troubleshooting checklist after going live.

¶ How to Choose Between Studio and API Platform

Comparison	White Label Studio	White Label API Platform
Main Customers	General users, creators, business teams	Developers, enterprise tech teams
How Customers Use	Chat, generate images, create videos, and compose music on the web	Read documentation, create API Keys, call interfaces
Page Domain Example	studio.zhishuyun.com	platform.zhishuyun.com
Is API Domain Required	No	Yes, bind xapi.zhishuyun.com when needed
Main Configuration	Brand, capabilities, login, pricing, banners, statistics	Brand, services, documentation, menu, domain, legal

You can launch either one or both simultaneously. If operating dual sites, first unify the brand name, logo, customer service, legal entity, and pricing principles, then configure them separately to avoid conflicting information for customers on both ends.

¶ Preparation Before Starting

1. A main account that can log into Ace Data Cloud;
2. Brand name, company/entity name, and a one-sentence introduction;
3. Horizontal logo, square favicon, preferably transparent PNG;
4. A self-owned domain that can modify DNS;
5. At least one real customer service method that is maintained;
6. Terms of service and privacy policy;
7. A test user who has never registered, for final verification of initial attribution.

The Zhishuyun case uses a 10% markup as an example for the API Platform. The real-time configuration in the screenshot is just a case status, not a suggested value, and should not be directly copied.

¶ Recommended Launch Order

1. First, create the Studio sub-site to verify brand, login, capabilities, pricing, and page domain;
2. Then create the API Platform, configuring services, documentation, page domain, and API domain;
3. Use a brand new test user to verify registration, redirection, customer attribution, and channel pricing;
4. Use low-cost requests to verify API documentation, Base URL, usage records, and billing;
5. After going live, conduct inspections daily, weekly, and monthly.

¶ Clarify Revenue and Pricing

The site can set a markup for the entire site or individual services. The normal purchasing process initiated from this white label site will display and record channel pricing; orders that meet distribution rules will be settled according to the current distribution relationship and level.

• Markup is not "100% of the difference returned to the site owner";
• Refunds, order status, risk control, and existing invitation relationships will affect final revenue;
• Accounts, balances, and packages belong to a shared system; site markup is not a mandatory tenant price that cannot be bypassed at all entry points.

¶ Must Understand Shared Boundaries

• Studio and API Platform use a shared identity system, and login may go through a unified authentication domain;
• Hiding recharge, services, documentation, or menus is display control, not interface authorization;
• Custom API domain names are brand entry points, not independent gateways or token tenant isolation;
• Generated results may still use the platform's public CDN;
• The crawler's first screen for the Platform and the ordinary browser SPA shell should be accepted separately;
• The brand of the Studio and shared authentication page mainly loads after the page runs, and the original HTML may still be a unified product shell.

¶ Success Indicators

You have decided to launch the Studio, API Platform, or both, and are ready with brand materials, candidate domain names, customer service, legal content, and test accounts; the team is also clear about the shared boundaries of the white label site.

¶ Next Article

Start building the first sub-site from Studio White Label from 0 to 1.