Overview of White Label Platform: Operating Studio and API Platform with Your Own Brand

White label operation is the second path of revenue generation for the affiliate alliance. Unlike "promoting YuJun," you no longer just share our entry point, but use your own brand, domain, product catalog, and pricing to serve customers.

The white label platform has two product forms:

• White Label Studio: Targeted at general users and content creators;
• White Label API Platform: Targeted at developers and enterprises.

They share the same white label foundation for the site. You can operate one or both under the same brand.

¶ White Label is Not a Redeployment of a System

The white label site will load your configuration based on the access domain name:

Your Studio page domain ──► Studio + Your brand, capabilities, and pricing
Your Platform page domain ─► API Platform + Your services and documentation
Your API request domain ─────► API Gateway + Unified authentication and billing

The underlying services, payments, ledgers, upgrades, and maintenance are still handled by the platform; you are responsible for brand positioning, product selection, pricing, customer acquisition, and customer service.

¶ What Can White Label Studio Do

White Label Studio is aimed at customers who do not need to write code and can currently configure:

• Site name, Logo, Favicon, theme color;
• Enable or hide AI capabilities;
• Display names and icons for capabilities;
• Unified markup for the entire site or per service;
• Custom domain names for pages and automatic HTTPS;
• Login methods, SMS sending, customer service, and legal information;
• Multilingual support, SEO, and platform branding.

Each account can currently create 5 sub-sites under one main site.

👉 White Label Studio: From Creation to Launch

¶ What Can White Label API Platform Do

White Label API Platform is aimed at developers and enterprise customers and can currently configure:

• Platform site name, Logo, Favicon, and brand information;
• Whether API services are displayed, display names, summaries, and sorting;
• Unified markup for the entire site or per service;
• Whether development documentation is displayed, titles, summaries, and sorting;
• Homepage Banner, customer service, and legal links;
• Custom domain names for Platform pages;
• Custom domain names for API requests;
• API Host and code examples displayed to customers.

Custom API domain names are a "nameplate change": customers can initiate requests through your domain, but the underlying system still uses a unified authentication and billing system. It will not automatically form an independent token tenant isolation.

👉 White Label API Platform: From Site to API Domain Name

¶ What Do the Two Products Share

Capability	White Label Studio	White Label API Platform
Own brand	✅	✅
Custom domain names	✅	✅
Service catalog and per service markup	✅	✅
Customer attribution and distribution revenue	✅	✅
Visual AI applications for general users	✅	—
Development documentation and API examples	—	✅
Custom API domain names	—	✅

It is best to plan brand, pricing, and customer attribution uniformly first, and then configure the two front ends separately to avoid using different names, prices, or customer service information for the same brand on Studio and API Platform.

¶ How White Label Revenue is Calculated

The revenue from the white label site still follows the platform's unified distribution system:

1. You set a markup for the entire site or a specific service;
2. Customers see and pay the amount after the markup;
3. The customer transaction amount enters the distribution statistics;
4. You earn revenue according to the current distribution level.

Therefore, the markup determines the base of the transaction amount, and the distribution level determines the proportion you earn from the transaction amount. The markup does not mean "the entire difference directly enters the site owner's balance."

¶ Recommended Launch Sequence

1. Create a site, determine the brand name and target customers;
2. Choose to launch White Label Studio, White Label API Platform, or both simultaneously;
3. Configure brand, customer service, and legal information;
4. Select services and set prices;
5. Bind page domain names;
6. If operating API Platform, bind API request domain names;
7. Complete registration, purchase, and call acceptance with new users;
8. Use content marketing and Connector to continuously acquire customers.

¶ Boundaries That Still Need to Be Clearly Stated

• Processes like social login may still go through a unified authentication domain, but will try to display the brand according to the site;
• Custom API domain names are brand entry points, which do not mean tokens can only be used on that domain or that site;
• Generated assets may still use the platform's public CDN domain;
• Specific visible configurations are subject to the projects currently provided by the two consoles.

You can read separately:

• White Label Studio Practical Guide
• White Label API Platform Practical Guide
• Customer Attribution and White Label Revenue