Platform Introduction
Applies to: Organization (top-level user), Subuser, Developer Updated: 2026-07-02
CloudRouter is a one-stop AI model aggregation and routing service platform that provides enterprises with unified multi-model access, intelligent routing, usage management, and organized collaboration. This article helps you quickly understand the platform's positioning, core capabilities, and the new console's approach to organization management.
1. Platform Positioning
CloudRouter is an AI model aggregation and routing service platform for enterprise users. The platform does not develop or train models itself; instead, it acts as an intermediary service layer, providing enterprises with a unified access point to multiple models, intelligent routing and dispatch, usage management, and cost control.
- Platform URL: cloudrouter.online
- Console: console.cloudrouter.online
Building on its existing capabilities, the new console introduces a "Platform - Organization - User" three-tier account hierarchy, upgrading the former "tenant management" into a clearer organization management model. If you are a legacy user, your account and balance carry over smoothly and no re-registration is needed. See Migration & Transition Notes.
2. Core Capabilities
2.1 Unified Multi-Model Access
One API set to access the world's mainstream AI models, covering Anthropic, OpenAI, Google, and major domestic model vendors — no need to integrate each vendor's API separately. The platform continuously expands its model ecosystem, and new models become callable from the same entry point as soon as they go live.
The Model Market (cloudrouter.online/model-plaza) is the entry point for viewing all available models and prices. In the Model Market you can:
- Browse all models the platform supports, filtered by provider
- View each model's capability description and pricing
- Compare price differences across groups/channels
The Model Market is on the official website and can be accessed without logging in. After logging into the console, the "Call Guide" page shows the models and call names currently available to your organization, and the "Purchase" page lets you top up and subscribe to plans.
The model name for calls is always obtained from the console "Call Guide" page, which supports both bare model names and fingerprinted call names. See Developer Guide · Call Guide & Dual Routing.
2.2 Multi-Channel Service System and Groups
CloudRouter offers multiple service channels that differ in stability, response speed, and price. Enterprises can flexibly choose based on business scenario and budget:
- What a channel is: A channel is a different service tier the platform provides for model calls; different channels correspond to different service quality and price tiers
- Choose on demand: For everyday development you can pick a cost-effective channel to lower costs; for critical business you can pick a high-quality channel to ensure stability
- Dynamic adjustment: The channel list and prices are continuously optimized; refer to the platform's actual display
What a "group" is: The group is the concept you'll deal with most when using CloudRouter. In simple terms, a group = a service-plan label — the same model (such as claude-sonnet-4-6) can be offered through different groups, and different groups may correspond to different channels, prices, and discounts. When creating an API Key, you need to choose a group for it, and calls will then route through that group's corresponding channel.
- Groups are maintained centrally by the platform. On the console "Call Guide" page you can see the currently available groups and the models under them
- On the "Available Channels / Channel Status" page you can view the channels available to your organization and their health status
- Specific group prices and discounts are as displayed on the "Model Market" or the console "Purchase" page
2.3 Billing & Deduction (Dual Pricing for Domestic and Overseas)
The platform uses balance as its unified funding unit (denominated in RMB, ¥1 = 1 balance unit) to simplify the billing complexity of multiple models and channels. Top-ups go into the organization balance pool, and calls are charged based on the actual number of Tokens consumed and the price of the chosen channel.
- Instant top-up: ¥1 top-up = 1 balance unit, RMB at 1:1
- Metered by Token: Calls are charged based on the actual number of Tokens consumed and the chosen channel's price
- Multiple top-up methods: Supports online payment top-up, redemption codes, promo-code campaigns, and more
- Transparent bills: The Token consumption details of each call, usage statistics, and top-up/spending records are all viewable in the console
Because overseas and domestic models are priced in different currencies, the platform uses two sets of pricing logic:
- Overseas models (Claude / GPT / Gemini, etc.): The platform offers competitive RMB pricing, usually more economical than buying directly from the model provider. Specific prices are as displayed on the "Model Market" or the console "Purchase" page
- Domestic models (Kimi / DeepSeek / Qwen / GLM, etc.): Fully identical to the official list price (¥1 = 1 balance unit); users get a unified access point and management capability at the same price as official
In simple terms: overseas models are cheaper via CloudRouter than buying directly, while domestic models are priced the same as official but come with the convenience of the platform's unified management. The specific pricing of each model is as displayed on the "Model Market" or the console "Purchase" page.
2.4 Enterprise-Grade Organization Management (Three-Tier Account Hierarchy)
The new console provides teams and enterprises with complete organized management capabilities. Accounts are organized into three tiers, with capabilities narrowing at each level:
| Tier | Role | Scope | Who fills it |
|---|---|---|---|
| Tier 1 | Platform | All organizations platform-wide | CloudRouter official operations |
| Tier 2 | Organization (top-level user) | The organization's balance, subusers, and usage | Enterprise account holder |
| Tier 3 | User / Subuser | Only their own Key calls and usage | Developers / callers under the organization |
An organization's core capabilities include:
- Organization balance pool: The organization shares a unified balance, with unified top-up and unified deduction
- Subuser management: Create / edit / deactivate subusers, set their business identity (account name, email, notes) and quota limits. See Subuser Management
- Key management: Create API Keys and bind a routing group to each Key. See API Keys & Routing Groups
- Usage monitoring: Organization-level and subuser-level Token usage statistics, bill queries, and trend analysis
The new version replaces the legacy "tenant" term with "Organization," "member" corresponds to "Subuser," and "model group" is uniformly called "group." For a full comparison of terminology and capabilities, see Migration & Transition Notes and Roles & Permissions Matrix.
3. Applicable Enterprise Types
| Enterprise type | Applicable range | Typical scenarios |
|---|---|---|
| One-person company (OPC) | Team of no more than 5 | Independent developers, freelancer studios |
| Small enterprise | 6–50 people | Startups, small technical teams |
| Medium enterprise | 51–500 people | Growth-stage tech companies, regional ISVs |
| Large enterprise | Over 500 people | Public companies, corporate groups |
4. Start Here
| I want to… | Where to look |
|---|---|
| Understand which tier I'm on and what I can do | Admin Handbook Overview, Three-Tier Account Hierarchy |
| Register and activate an organization account | Organization Registration & Activation |
| Manage team members | Subuser Management |
| Create Keys and integrate into code | API Keys & Routing Groups |
| What changes after a legacy account is migrated | Migration & Transition Notes |
Contact Us
- Email: support_cloudrouter@clouditera.com
- QQ community: 712273971
- Platform URL: cloudrouter.online