Professional traders and small desks using Gate Institutional subaccounts when they need parallel strategies, member roles, or external team access without giving up fund-control authority at the main-account level. The sections below cover the main-account relationship, permission and isolation design, reporting and API access, and when subaccounts beat a single VIP main account.
A Gate subaccount is an investment account created under a primary Gate account (main account). The main account owns creation, funding, and permission governance; subaccounts execute strategies or serve assigned team members and external trading teams.
Per Gate subaccount creation guide, each main account can create multiple subaccounts. The cap scales with main-account VIP level:
| VIP level | Maximum subaccounts |
|---|---|
| VIP 0 – VIP 4 | Up to 10 |
| VIP 5 – VIP 9 | Up to 30 |
| VIP 10 – VIP 11 | Up to 100 |
| VIP 12 – VIP 16 | Up to 200 |
Contact official support if more subaccounts are needed. Subaccounts cannot be deleted after creation, so naming and purpose should be planned for long-term use.
| Type | Role | Typical use |
|---|---|---|
| Standard Subaccount | Directly managed by the main account | Internal quant desks, strategy testing, product-line fund separation |
| Managed Subaccount | Can connect to an external trading team | Delegated management, outsourced strategies, partner trading with permission boundaries |
During creation, users choose account type, set username, configure trading permissions (spot/margin, perpetual futures, delivery futures, etc.), and add remarks. Managed subaccounts require trading teams to apply through customer support; after approval, team managers operate via subaccount API keys (see managed subaccount workflow).
The main account is the root of funds and permissions. Subaccounts bind to it in several ways:
| Dimension | Main account | Sub-account |
|---|---|---|
| Fund transfers | Can move funds to/from subaccounts | Cannot initiate transfers to main or other subaccounts |
| VIP tier | Sets subaccount creation cap | Inherits main-account VIP tier and fee discounts |
| VIP evaluation | Aggregates subaccount volume | Volume counts toward main-account 30-day trading volume |
| Withdrawals and P2P | Full feature set | No P2P; withdrawals restricted and whitelist-based |
| Security | Primary control | Can use separate login/2FA or follow main-account settings |
This structure keeps asset safety centralized. Even if an external operator holds a subaccount API key, they cannot move funds off-platform without main-account authorization (unless a whitelist was pre-configured). Professional teams can delegate execution while treasury or operations retains funding control.
Professional teams usually need separated capital, positions, and API access per strategy so books stay clean and risk limits do not cross-contaminate. Gate subaccounts support isolation through:
Quant teams running arbitrage, trend, or market-making lines in parallel often assign one subaccount plus one API stack per strategy. The main account rebalances capital daily or by risk rules. Underperforming strategies can be frozen without stopping others.
Team operations need auditable records and automation—not just order entry. Gate subaccounts provide on Web and App:
| Feature | Purpose |
|---|---|
| Transfer history | Track main-to-sub fund movements |
| Account records | Sub-account-level trades and balance changes |
| Sub-account API | Independent API key management per subaccount |
| Remarks and pinning | Identify strategy purpose when many subaccounts exist |
Institutional-style teams planning cross-venue execution should align subaccount key design with institutional API access: least-privilege permissions, IP allowlists, and separate keys per person or strategy—not one shared full-access key.
For reporting, main-account operators can aggregate subaccount performance and reconcile against internal PnL systems. Sub-account volume automatically counts toward main-account VIP evaluation, so team-wide fee reduction still depends on main-account VIP tier—subaccounts do not carry separate VIP levels but contribute volume that helps maintain or raise tier.
Not every professional trader needs subaccounts. Use this decision frame:
| Scenario | Suggested structure | Why |
|---|---|---|
| Solo high-frequency trader, one strategy | Single VIP main account | Simplest path; VIP thresholds apply directly |
| 2–5 parallel strategies needing isolated PnL | Multiple subaccounts + VIP main account | Clear strategy boundaries with shared VIP fees |
| External trading team manages capital | Managed subaccount | Defined permission boundary; main account keeps funding control |
| Cross-product shared margin, less fragmentation | Unified Account (can combine with subaccounts) | Unified Account improves margin efficiency; subaccounts improve strategy boundaries |
| Enterprise approvals, OTC, custody | Institutional modules + subaccounts/Unified Account | Subaccounts handle execution roles; Institutional handles enterprise workflows |
A single VIP main account fits one operator, one strategy, and fee optimization as the top goal. Subaccounts become worth evaluating when signals appear: multiple traders need separate logins or APIs; strategies have materially different risk parameters; test and production capital must stay apart; or an external manager needs execution access while the firm keeps fund sovereignty.
Subaccounts and Gate Unified Account solve different problems: subaccounts slice vertically by strategy and people; Unified Account connects horizontally across product margin pools. Advanced teams often combine both—see combining Unified Account and subaccounts.
Before designing architecture, note platform constraints:
These limits push large fiat on/off-ramps and institutional settlement toward the main account or Institutional OTC workflows, while subaccounts focus on execution.
Gate subaccounts give professional traders and teams strategy isolation, role-based permissions, and independent API management under one main account. Subaccounts inherit VIP fee tiers and feed main-account VIP volume evaluation while funding control stays at the main-account level. Standard subaccounts suit internal multi-strategy desks; Managed subaccounts suit vetted external trading teams. A single VIP main account is enough when one strategy and one operator dominate; subaccounts matter when parallel strategies, staff separation, or delegated execution appear. Combined with Unified Account and institutional API, subaccounts help teams balance margin efficiency and operational boundaries—the next module in this path compares Unified Account and subaccount usage in detail.
A Gate subaccount is an investment account created under the main account for role separation and asset isolation. The main account creates subaccounts, moves funds, and sets permissions. Subaccounts inherit main-account VIP tier and fee discounts, but only the main account can initiate fund transfers.
Yes. Sub-account volume counts toward the main account’s 30-day VIP trading volume, and subaccounts inherit the main account’s current VIP tier and fee discounts. VIP progress displays from the main-account view.
Standard subaccounts fit strategies or members managed directly by the main account. Managed subaccounts fit approved external trading teams: the main account keeps funding control while the team trades via subaccount API keys. The choice depends on whether outsourced execution and permission boundaries are required.
No. Subaccounts separate strategies and users under one main account. Unified Account shares margin and centralizes risk views across products at the account-structure level. Teams can use both, but each solves a different problem.
Not necessarily. If trading stays on one strategy with no staff separation or capital isolation needs, a single VIP main account is usually simpler. Evaluate subaccounts when parallel strategies, separate API access, external team delegation, or test/production isolation becomes necessary.
* The information is not intended to be and does not constitute financial advice or any other recommendation of any sort offered or endorsed by Gate.
* This article may not be reproduced, transmitted or copied without referencing Gate. Contravention is an infringement of Copyright Act and may be subject to legal action.





